EM

EMC2

Einsteinium

Unresolved

An inactive aggregator label conflicts with a much newer code commit and a responding official website.

Checked-channel clock

1,115complete dayson the checked code repository · through 11 Jul 2026This is not a project-wide silence date.
AssessmentUnresolved

Evidence conflicts or is incomplete

Clock interval1,115 days

Native timestamp precision

Overall confidencelow

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

An inactive aggregator label conflicts with a much newer code commit and a responding official website.

“Ghosted” is editorial shorthand only. The formal assessment is unresolved, scoped to the channels and dates shown below.

01

Strongest supporting evidence

2 cited facts

02

Strongest counterevidence

Leading hypothesis attacked
C1

The foundation's linked website responds, and the 2023 commit is newer than an abandonment inference based only on an inactive listing would suggest.

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
Codeemc2foundation/einsteinium default branchsilent21 Jun 20231,115 complete daysOpen source ↗Newer than the other pilot candidates, but still only one checked code surface.
Websiteemc2.foundationreachable unverified freshnessUnresolvedunknownOpen source ↗A responding site is countercontext, not a reliable update timestamp.
X@einsteiniumcoinnot exhaustively checkedUnresolvedunknownOpen source ↗Complete historical access was not established.

04

Alternative explanations

  • A1Low-frequency maintenance may be appropriate for mature protocol software.
  • A2Trading inactivity and team inactivity may be unrelated.

05

Unresolved unknowns

  • U1No complete release, issue, X or community chronology has been reviewed.
  • U2The website's most recent meaningful first-party update is unresolved.

Highest-value next checks

What would most reduce uncertainty?

  1. Review releases, all branches, signed commits, issues and organization repositories after June 2023.
  2. Establish the official X account ID and retrieve its complete accessible history.