<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Dead Tokens research updates</title><link>https://deadtokens.com</link><description>Evidence-first crypto project activity assessments.</description><item><title>Feathercoin — active counterexample</title><link>https://deadtokens.com/projects/feathercoin</link><guid>https://deadtokens.com/projects/feathercoin#2026-07-11.1</guid><description>CoinPaprika says inactive, yet the official repository shows substantive activity in June 2026.</description></item><item><title>Nebulas — unresolved</title><link>https://deadtokens.com/projects/nebulas</link><guid>https://deadtokens.com/projects/nebulas#2026-07-11.1</guid><description>Late-2024 code is real, static sites remain online, and backend failures may be temporary; a dead-project verdict would be premature.</description></item><item><title>Waltonchain — possibly silent</title><link>https://deadtokens.com/projects/waltonchain</link><guid>https://deadtokens.com/projects/waltonchain#2026-07-11.1</guid><description>Its last verified official post described an airdrop, not a shutdown; the linked code vanished and the main domain became unreachable or blocked.</description></item><item><title>Geist Finance — explicitly ceased</title><link>https://deadtokens.com/projects/geist-finance</link><guid>https://deadtokens.com/projects/geist-finance#2026-07-11.1</guid><description>Geist publicly said it would not reopen after the Multichain loss; a generic page at the old domain does not reverse that closure.</description></item><item><title>Einsteinium — unresolved</title><link>https://deadtokens.com/projects/einsteinium</link><guid>https://deadtokens.com/projects/einsteinium#2026-07-11.1</guid><description>An inactive aggregator label conflicts with a much newer code commit and a responding official website.</description></item><item><title>Babylon Finance — explicitly ceased</title><link>https://deadtokens.com/projects/babylon-finance</link><guid>https://deadtokens.com/projects/babylon-finance#2026-07-11.1</guid><description>The founder explained the wind-down, published reimbursement work and set a closure date; this is an orderly shutdown, not a disappearance.</description></item><item><title>Cover Protocol — explicitly ceased</title><link>https://deadtokens.com/projects/cover-protocol</link><guid>https://deadtokens.com/projects/cover-protocol#2026-07-11.1</guid><description>The team announced shutdown and treasury distribution in September 2021; this is transparent closure, not ghosting.</description></item><item><title>ShipChain — explicitly ceased</title><link>https://deadtokens.com/projects/shipchain</link><guid>https://deadtokens.com/projects/shipchain#2026-07-11.1</guid><description>Token operations were ordered to cease; the last verified default-branch code activity predates the order.</description></item><item><title>Po.et — possibly silent</title><link>https://deadtokens.com/projects/poet</link><guid>https://deadtokens.com/projects/poet#2026-07-11.1</guid><description>Its final official update promised a roadmap the following week; no later publication appeared, code had already stopped, and the domain is gone.</description></item><item><title>Substratum — possibly silent</title><link>https://deadtokens.com/projects/substratum</link><guid>https://deadtokens.com/projects/substratum#2026-07-11.1</guid><description>The last verified official post announced production in 2019; the original team then disappeared while a successor fork continued the codebase.</description></item><item><title>Bounty0x — possibly silent</title><link>https://deadtokens.com/projects/bounty0x</link><guid>https://deadtokens.com/projects/bounty0x#2026-07-11.1</guid><description>Old code and an inactive listing are strong leads, but public communication histories remain incomplete.</description></item><item><title>BitConnect — explicitly ceased</title><link>https://deadtokens.com/projects/bitconnect</link><guid>https://deadtokens.com/projects/bitconnect#2026-07-11.1</guid><description>The original platform shut down in January 2018; later community code does not prove the original operator returned.</description></item></channel></rss>