Fork confusion map
When a chain forks, the fight moves off the code and onto one question — which one is the real one — and that question drags a dozen others behind it. Here they are as one network, colored by how well each is evidenced.
Fork confusion map, anonymized
- Load-bearing: which one is real?
- Verified: are my old coins safe?
- Verified: inherited the old scandal
- Verified: same name, new token
- Contested: did the devs move?
- Contested: is it a cash-grab?
- Verified: exchange listed the wrong one
- Latent: docs point to old repo
- Latent: which chat is official?
How to read it
Each node is a question the public actually asks. A link means one misreading pulls the next along with it. Node size is downstream pull — how many other questions it feeds.
- Verified — documented in the public record
- Contested — the evidence points both ways
- Latent — asked quietly, not yet loud
- The load-bearing question
Anonymized pattern from real audits; questions collected from public surfaces. Color = evidence state, not vibe. Hand-tuned layout, static render.
Why it matters
A contested fork doesn't spread through its whitepaper. It spreads the way a rumor does — one confused person at a time, each question dragging the next. Draw the network and one node usually carries the rest. Answer that one first.
Read the note