DEAD TOKENS
Directory/ShipChain
SH

SHIP

ShipChain

Explicitly ceased

Token operations were ordered to cease; the last verified default-branch code activity predates the order.

Cessation clock

2,027–2,028complete dayssince the SEC cessation order · through 11 Jul 2026
AssessmentExplicitly ceased

Cessation supported by a primary source

Clock interval2,027–2,028 days

Source gives a date, so a range is preserved

Overall confidencemedium

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

Token operations were ordered to cease; the last verified default-branch code activity predates the order.

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

01

Strongest supporting evidence

3 cited facts
01

On 21 December 2020, the SEC ordered ShipChain to transfer its SHIP tokens so they could be permanently disabled and to request removal from trading platforms.

U.S. SEC order ↗live

02

Strongest counterevidence

Leading hypothesis attacked
C1

The SEC Fair Fund case page contains administrative updates through 2025. Those are regulator/distribution activity, not evidence that the ShipChain team resumed work.

U.S. SEC Fair Fund ↗live · redirected
C2

The old domain responds, but a responding domain alone cannot establish current project ownership or a recent substantive update.

Live domain ↗live · redirected

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
CodeShipChain/transmission default branchsilent22 Oct 20202,087 complete daysOpen source ↗Latest default-branch commit found. Other branches and transferred repositories remain a coverage risk.
Websiteshipchain.ioidentity uncertainUnresolvedunknownOpen source ↗A live domain is not evidence of project activity; current ownership and content continuity need archival verification.
X@shipchainnot exhaustively checkedUnresolvedunknownOpen source ↗Historical completeness was not established, so no project-wide last-post date is claimed.

04

Alternative explanations

  • A1Some work could have moved to private repositories before the regulatory order.
  • A2A community continuation could exist without representing the original issuer.

05

Unresolved unknowns

  • U1The final meaningful first-party post across X, Medium and Telegram has not been established with complete native histories.
  • U2Current ownership of shipchain.io has not been cryptographically or archivally tied to the original team.

Highest-value next checks

What would most reduce uncertainty?

  1. Obtain the complete X account timeline by stable account ID and compare it with archived Medium and Telegram history.
  2. Resolve every repository in the historical ShipChain organization, including non-default branches and transfers.