BitNames
Naming & identityA decentralized naming and identity sidechain. Register human-readable names, domains, and identities on Bitcoin — a Namecoin-style system with no separate token.
Eleven drivechains active on the eCash alphanet — seven from Layer Two Labs, plus four newly proposed by independent teams. Each is a purpose-built chain secured by proof-of-work through blind merge mining.
A decentralized naming and identity sidechain. Register human-readable names, domains, and identities on Bitcoin — a Namecoin-style system with no separate token.
A low-fee, Turing-complete UTXO sidechain for builders, built on RISC-V. Uses Avalanche-style pre-consensus for instant finality, serving high-throughput applications while staying BTC-pegged.
An asset-issuance sidechain. Create and trade user-defined assets — tokens, stablecoins, and synthetic instruments — collateralized and settled on Bitcoin.
A high-throughput payments sidechain. Optimized for fast, low-fee transactions at large scale, keeping everyday spending off scarce mainchain block space.
A decentralized oracle and prediction-market sidechain — Paul Sztorc's Hivemind design. Settles real-world outcomes and runs peer-to-peer betting markets without a trusted third party.
The Elements codebase behind Liquid, rebuilt as a native drivechain. Brings Confidential Transactions, issued assets, and Simplicity smart contracts — secured by BIP 301 blind merge mining instead of a federation.
A Snowball-consensus Avalanche subnet for eCash — a high-throughput EVM chain where ECX is the native gas token. Its bridge is a custodial MVP today, with full BIP 300/301 enforcer integration planned.
A privacy sidechain derived from Zcash. Brings shielded, zero-knowledge transactions to Bitcoin, so BTC can move confidentially — no separate coin and no trusted mixer.
A sidechain focused on quantum resistance — hardening Bitcoin-secured value against future quantum attacks on today’s signature schemes.
Credit creation on a drivechain, in the tradition of Scottish free banking. Discount houses issue redeemable credit notes and bills of exchange backed by reserves — be your own bank.
A sidechain node with a trustless L2 ↔ L1 swap system, moving value between the sidechain and Bitcoin mainchain without a custodian.
BIP 300 makes sidechains permissionless to build and miner-approved to activate. Anyone can create one; Bitcoin's miners decide whether it earns a slot. Here's the path from idea to live chain.
Fork a template — such as Layer Two Labs' plain sidechain — or use the drivechain library to implement your chain's rules, its deposit and withdrawal logic, and BIP 301 blind merge mining so Bitcoin miners can commit to your blocks. No permission is needed to write it; the software itself is the proposal.
Assemble the metadata that uniquely names the chain: a slot number (BIP 300 provides 256 sidechain slots), a version, a human-readable title and description, and hashes committing to the exact software release — so every node and miner can verify they're running identical rules.
Publish an M1 "Propose Sidechain" message in the coinbase of a Bitcoin block, claiming an empty slot. This registers the candidate directly on the mainchain and opens its activation vote — no altcoin, no separate token sale.
Over a fixed activation window, miners signal approval by including M2 "ACK Sidechain" messages in their coinbase outputs, block after block. The proposal must clear a high approval threshold within the window: enough hashrate agreement and the slot activates; too little and it expires, freeing the slot for someone else.
Once a slot is active, users peg BTC in by depositing to the sidechain's escrow output, transact on the chain, and peg out through the slow, publicly-audited withdrawal-bundle process (M3 / M4). Miners keep securing it with blind merge mining — one proof-of-work, your chain included — and it stays denominated in BTC with no new token.
Note: BIP 300/301 is a proposed Bitcoin soft fork and is not yet activated on mainnet, so today these steps run on a drivechain signet. Activating BIP 300 itself is a one-time soft fork; after that, every new sidechain is adopted through the miner-vote process above — no further protocol change required.