Timeline
Roadmap
The project's milestones, from the foundation phase to full decentralisation. Source: the Bitcoin Hyper whitepaper — latest version: 4 January 2026
bitcoinhyper.com
A note on method: dates marked ✓ have been verified. Dates marked ○ are estimates based on official announcements. According to the whitepaper, mainnet was originally expected in Q4 2025 – Q1 2026; as at 28 April 2026 it was not live.
Foundation phase
Launch of the official site, brand development, whitepaper v1, formation of the core team, community building on X, Telegram and Discord
Presale and staking
The $HYPER token in a multi-stage public presale. Staking active, with an APY for early participants. The first smart contract audit is under way. Advisory work and developer partnerships.
DevNet live
SVM programs run natively, the block explorer is live, and DeFi, SPL and multi-signature testing is under way with selected developers
Security audit
The first audit of the smart contract and the bridge is under way. According to the project, the results will be published on the official site before the TGE.
A stable canonical bridge
The BTC↔Hyper bridge is being tested on DevNet and forced exit is in development. The plan is for a decentralised, non-custodial bridge.
Public testnet
Launch of a testnet for developers and the wider community. Ahead of mainnet.
Mainnet launch
Deployment of the Bitcoin Hyper Layer 2 network. Activation of the canonical BTC bridge. The SVM fully operational. The first dApps and smart contracts on the Layer 2.
Listings and ecosystem growth
Listing of $HYPER on DEXs (Uniswap) and CEXs. A developer toolkit (SDK + API). Onboarding of DeFi, gaming and NFT projects. Listing price: $0.013681.
DAO and decentralisation
Launch of the Bitcoin Hyper DAO for community governance. Incentives for node operators and developers. Decentralisation of the sequencer is estimated at two to four years after mainnet.
Critical dependencies: mainnet depends on (1) completing and publishing the audits, (2) stabilising the canonical bridge, forced exit included, (3) settling the data availability solution and (4) completing the tokenomics schedule. A delay in any one of these pushes mainnet back.