Breakcoin: a Bitcoin fork split across one million recovery phrases

Breakcoin. Fork of Bitcoin. The logo looks cracked on purpose. So does the custody story.

I will be publishing spec drafts on GitHub: https://github.com/justindrake. This is my only GitHub. If it is not on that account, it is not from me.

In this post:

• Why I forked Bitcoin instead of inventing another L1 from scratch
• The million-phrase registry and combinatorial custody
• What “bunkermode” means in crypto—and why Breakcoin breaks it
• What breaks if you treat Breakcoin like a normal memecoin
• Plus 3 links and 2 notes

---

A Bitcoin fork with a different recovery story - 2026-10-17

Breakcoin is a consensus fork of Bitcoin: same UTXO intuition, same block cadence, same “verify, don’t trust” spine. Where it diverges is custody. Bitcoin taught the world to write down twelve words, stash them offline, and call that security. I call the mindset bunkermode: hoard one seed string in a safe, a steel plate, or an air-gapped laptop, then treat the problem as solved.

Bunkermode fails in predictable ways. One burglary. One coercion scene where you read the words aloud. One bulk leak from a password manager or a cloud photo roll labeled “do not open.” One phishing flow that asks you to “confirm your recovery phrase.” The chain does not care that you felt clever hiding paper in a freezer.

Breakcoin refuses the single-string bunker. At launch the fork commits a fixed catalog of exactly 1,048,576 recovery phrases (2²⁰ entries, indexed 0…1048575). Each line is BIP39-shaped, but none of them alone is your wallet. Your wallet is a break draw: twenty-four phrase IDs chosen deterministically from block hash entropy when you create the account, plus an optional user passphrase.

The private key is not any one phrase. It is derived only when you supply the full tuple:

BREAK_SEED = SHA-256( phrase[id_1] || phrase[id_2] || ... || phrase[id_24] || passphrase )
k            = BIP32_master(BREAK_SEED)
address      = Hash160(k * G)

The million phrases are public. They ship in the break genesis block as a Merkle root. Anyone can mirror the list. What they cannot guess is which twenty-four slots belong to you unless they know your draw—or brute-force a space that is intentionally obnoxious. You cannot bunker one pretty sentence and call it safe; the vocabulary is shared, and the secret is the combination.

Why publish a million phrases if they are public anyway? - 2026-10-17

Because bunkermode optimizes for hiding one blob. Breakcoin optimizes for splitting recovery across a public phrase registry and a private draw. Malware that dumps seed.txt finds index files and partial checkpoints, not a single labeled line. An attacker with your laptop must identify which twenty-four of a million published lines you used, in order, then grind the KDF. A phishing page cannot succeed with one paste—it would need your entire index vector, which honest UIs never show as one blob.

Artifact	What it is
Registry root	On-chain at break genesis. 1,048,576 phrases committed once. Same for everyone.
Draw vector	Twenty-four integers in [0, 1048575]. This is what you backup (encoded, not plaintext phrases).
Passphrase	Optional second factor. Hashed into BREAK_SEED before BIP32.
Private key k	Ephemeral. Wallets derive, sign, zero. Never written to disk.

Recovery is ritual, not poetry. You open a Break wallet, re-enter the draw (or scan an encoded backup QR), pull the twenty-four public phrases by ID, mix them, and only then see a balance. Lose the draw vector and the million phrases are a library with no card catalog.

What Breakcoin actually is on-chain - 2026-10-17

Breakcoin inherits Bitcoin’s monetary surface: capped supply on the fork, boring blocks, fees are fees. The novelty is custody metadata on Breakcoin-native addresses: spends must prove you completed the phrase combination without revealing which IDs were used. (Pedersen commitments over the index vector plus a SNARK that the derived pubkey matches—this post is not the spec.)

Logo above. Meme surface area: high. Under the meme is the point: combinatorial custody so you cannot retreat into bunkermode with one seed and pretend you are done.

What this will not save you from - 2026-10-17

If you photograph your draw vector and post it, Breakcoin cannot help you. If someone holds a gun and you read all twenty-four indices aloud, same story. The million phrases are not magic; they are a different shape of lock. Combinatorial custody raises the cost of bulk leaks, lazy phishing, and “I have one seed in a bunker” complacency. It does not repeal social engineering.

Also: 1,048,576 phrases at genesis is a large but finite download. Light clients fetch proofs, not the whole book. Do not interpret “million recovery phrases” as “store a million backups.” You store one vector. The chain stores the library once.

Why I would ship this fork - 2026-10-17

Because Bitcoin won the narrative war on sound money and still lost the custody war to single-string bunkermode. Breakcoin separates public vocabulary from private selection. The vocabulary is the million lines. The selection is yours. The key is the ceremony that combines them—on a chain that still feels like Bitcoin if you squint at the block explorer.

If I were writing the wallet box copy, it would fit on a sticker:

1. Breakcoin is a Bitcoin fork.
2. One million recovery phrases ship with the chain. They are not secrets.
3. Your wallet is twenty-four IDs into that catalog, plus an optional passphrase.
4. Never backup the derived key. Backup the draw. Do not bunkermode one string.

---

Links

• Discuss on Hacker News
• Grok @bot agents and Stupid Moron Company
• BIP-39, for the phrase format the registry reuses

Notes

TIL: 2²⁰ = 1,048,576. I picked a power of two so index vectors pack cleanly into 20-bit fields.

Quote: “Bunkermode is one seed in a hole. Breakcoin is twenty-four shelf numbers in a million-line library.” — me, on a scrap of paper.