Inspiration
Every crypto cycle ends the same way: thousands of tokens die — rugged, abandoned, or simply faded away — and nobody remembers them. I have watched tokens I followed go to zero, and the graveyard of dead coins felt like a story worth telling with a little dark humor. Crypto Graveyard gives every dead token a tombstone.
What it does
Crypto Graveyard is a horror-themed dashboard for dead and rugged tokens. Each token gets a grave showing its name, cause of death (rug pull, abandoned, or faded -99%), peak price, how far it fell, and its full story. Live prices come from the free Dexscreener API wherever a trading pair still exists, and the header totals the estimated value lost across all graves with live data. You can search any token, filter by cause of death, open a token's detail view for its price sparkline and full story, and paste any contract address to look it up directly. Tokens whose trading pair is gone are marked "pair gone" and show an illustrative decline from peak to death instead of a live sparkline. Everything runs client-side — no backend, no API key, no login.
How I built it
I built it with Kiro CLI 3.4.0 using spec-driven development. I wrote a full spec first (.kiro/specs/crypto-graveyard/): requirements, design, and 15 tasks in order. Kiro implemented tasks 1–10 from the spec (Vite + React + TypeScript + Tailwind scaffold, curated token registry, Dexscreener client, graveyard computations, dark horror theme, tombstone cards, grid, stats header, search and filters). The stack is Vite, React, TypeScript, Tailwind CSS, and Vitest, deployed on GitHub Pages. After launch I fixed the live-price handling and added the cause filter (task 16): empty Dexscreener results are now treated as "no pair" instead of an error, five registry addresses were corrected against live data, and pair-less tokens are labelled honestly. All 69 Vitest tests pass and the production build is clean.
Challenges I ran into
No free API exposes "dead tokens", and Dexscreener has no historical OHLCV — so peak prices, death dates, and causes of death live in a curated registry inside the app, while Dexscreener only provides live prices and change buckets for the sparkline. Most dead tokens have no trading pair left at all: the first deployed version treated that as an error and showed $0 lost, so I reworked it to distinguish a genuinely missing pair from a failed request. Mid-build, my Kiro monthly usage limit ran out — so I finished tasks 11–15 manually, following the same spec (charts, token detail, data hooks, routing). The spec kept the build on track even after Kiro itself was unavailable.
What's next
More tokens in the registry, community-submitted tombstones, and a "cause of death" deep-dive view.
Built With
- dexscreenerapi
- githubpages
- kiro
- react
- tailwindcss
- typescript
- vite
- vitest