CO

COVER

Cover Protocol

Explicitly ceased

The team announced shutdown and treasury distribution in September 2021; this is transparent closure, not ghosting.

Cessation clock

1,769–1,770complete dayssince the official shutdown announcement · through 11 Jul 2026
AssessmentExplicitly ceased

Cessation supported by a primary source

Clock interval1,769–1,770 days

Source gives a date, so a range is preserved

Overall confidencehigh

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

The team announced shutdown and treasury distribution in September 2021; this is transparent closure, not ghosting.

“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

02

Strongest counterevidence

Leading hypothesis attacked
C1

Contracts and tokens can remain usable or tradable after team closure; this is ecosystem persistence, not renewed project operation.

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
CommunicationOfficial @CoverProtocol X accountceased5 Sept 20211,770 complete daysOpen source ↗The post explicitly announced shutdown and a treasury-distribution plan.
CodeCoverProtocol/cover-docssilent23 Jul 20211,814 complete daysOpen source ↗Last official default-branch commit found before shutdown.
WebsiteFormer project domainidentity uncertainUnresolvedunknownOpen source ↗The former domain redirects to unrelated content and must not reset the project clock.

04

Alternative explanations

  • A1Community users may continue interacting with immutable contracts after the team exits.

05

Unresolved unknowns

  • U1Whether every promised treasury distribution completed is outside this closure classification.

Highest-value next checks

What would most reduce uncertainty?

  1. Verify the final treasury distribution on-chain and preserve the official thread in an archive.