DEAD TOKENS
Directory/Feathercoin
FT

FTC

Feathercoin

Active counterexample

CoinPaprika says inactive, yet the official repository shows substantive activity in June 2026.

Latest checked activity

34complete dayssince the latest checked code activity · through 11 Jul 2026
AssessmentActive counterexample

Recent activity falsifies the dead-token shortcut

Clock interval34 days

Native timestamp precision

Overall confidencemedium

Minimum of identity, timestamp and coverage

Policy2026-07-11.1

Reviewed as of 11 Jul 2026

Concise conclusion

CoinPaprika says inactive, yet the official repository shows substantive activity in June 2026.

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

01

Strongest supporting evidence

2 cited facts

02

Strongest counterevidence

Leading hypothesis attacked
C1

The inactive listing is counterevidence only to market support, not to project activity; recent code directly contradicts a project-silence claim.

CoinPaprika API FAQ ↗live

03

Channel ledger

Separate clocks; separate failure modes
ChannelStatusLast verified activityEvidence
CodeFeatherCoin/Feathercoin default branchactive6 Jun 202634 complete daysOpen source ↗This recent first-party code activity falsifies the shortcut that an inactive aggregator listing means a dead project.
Websitefeathercoin.comreachableUnresolvedunknownOpen source ↗Reachability corroborates continuity but is not used as a publication timestamp.
X@Feathercoinnot exhaustively checkedUnresolvedunknownOpen source ↗Not needed to reject the dead-token hypothesis, but still incomplete.

04

Alternative explanations

  • A1The aggregator status may reflect trading availability rather than software maintenance.
  • A2The project could be active in code but quiet in investor-facing communication.

05

Unresolved unknowns

  • U1The latest meaningful communication-channel activity has not been exhaustively established.

Highest-value next checks

What would most reduce uncertainty?

  1. Check whether the June 2026 commit is a substantive maintainer change rather than an automated or mirrored update.
  2. Ask CoinPaprika what specific market condition caused the inactive status.