Timeline
Roadmap
The project milestones, from Foundation through to full decentralisation. Source: the Bitcoin Hyper whitepaper — Latest version: 4 January 2026
bitcoinhyper.com/it
Methodological note: Dates marked ✓ are verified. Dates marked ○ are estimates based on official statements. According to the whitepaper, the mainnet was originally expected in Q4 2025–Q1 2026; as of 28 April 2026 it was not yet live.
Foundation
Launch of the official site, branding, whitepaper v1, formation of the core team, community building on X/Telegram/Discord
Presale & Staking
The $HYPER token in a multi-stage public presale. Staking activated with APY for early participants. First smart-contract audit under way. Advisory work and developer partnerships.
Devnet operational
SVM programs running natively, explorer live, DeFi/SPL/multi-signature testing with selected developers
Security audit
First smart-contract and bridge audit under way. The project states that the results will be published on the official site before the TGE.
Stable canonical bridge
The BTC↔Hyper bridge is under testing on devnet, with forced exit in development. Intended to be a decentralised, non-custodial bridge.
Public testnet
Opening of the testnet to developers and the wider community. Pre-mainnet.
Mainnet launch
Deployment of the Bitcoin Hyper Layer 2 network. Activation of the BTC canonical bridge. SVM fully operational. First dApps and smart contracts on the Layer 2.
Listing & Ecosystem Expansion
Listing of $HYPER on DEXs (Uniswap) and CEXs. Developer toolkit (SDK + API). Onboarding of DeFi, gaming and NFT projects. Listing price: $0.013681.
DAO & decentralisation
Launch of the Bitcoin Hyper DAO for community governance. Incentives for node operators and developers. Sequencer decentralisation is projected at 2–4 years from mainnet.
Critical dependencies: The mainnet depends on: (1) completion and publication of the audits, (2) stabilisation of the canonical bridge with forced exit, (3) definition of the DA solution, and (4) completion of the tokenomics schedule. Any delay on any of these points would push back the mainnet.