All 10M participants enter the daily BTC draws. The first 1M get 3× tickets in every daily draw and exclusive entry to the 275 BTC founding draw. Once the millionth slot is filled, both advantages close by code.
The protocol is structurally simple but the documentation is comprehensive. Pick the door that matches what you want to know — each tile takes you straight to the section that answers it.
Three tickets in every daily BTC draw, for the full five-year cycle. Not one. Three.
A second, sealed draw — 275 winners receive 1 BTC each. Reserved exclusively for the founding million.
Same $100 entry, same capital terms, same pro-rata share of the Year 5 surplus pool as everyone else. The bonus is encoded at registration and resolved deterministically on-chain — no operator can modify the outcome. The protocol's total distribution is 2,100 BTC: one for every 10,000 of the 21 million that will ever exist.
The $100 entry is not consumed on use. It contributes to a treasury that holds ICP across the five-year cycle. At Year 5, the 80% participant pool is distributed pro rata to every participant — winners and non-winners alike. If the treasury performs, every participant receives a share.
See the Full Scenario Analysis · 1× to 100× ICP →Illustrative model. Subject to treasury performance. No specific financial outcome is promised.
The protocol is designed to settle deterministically on a single day at the end of the five-year cycle. There is no mid-cycle event, no rebalancing, and no managerial reaction to market movement. Bull runs, drawdowns, recoveries — whatever happens to ICP between launch and settlement does not affect the outcome. Only the ICP price on the settlement day determines what is in the pool to distribute.
This page is informational. Participation, if and when it opens, will be restricted by jurisdiction and subject to the outcome of the current legal engagement.
The first 1,000,000 participants form the founding cohort. They receive 3× tickets in every daily BTC draw for the full 5 years and exclusive entry to the 275 BTC sealed founding draw. Once the millionth slot is filled, both advantages close permanently. Daily 1 BTC draw eligibility extends across all 10,000,000 participant slots at the standard one-ticket rate.
Participation will not be offered to persons resident or located in the United States, Canada, or other jurisdictions where local law does not permit it. You are responsible for determining whether participation would be lawful in your location. Access may be technically restricted by geoblocking at launch.
A deterministic protocol built on the Internet Computer Protocol — which runs entirely on-chain, without off-chain servers or AWS dependencies. The description below reflects the protocol architecture currently under legal review. Specific mechanics may change as that review concludes.
A single fixed participation amount per person — indicatively $100 — up to a capped number of participants. No tiered pricing. No discretionary allocation. No preferential access. Every participant enters under the same rules. No payment is accepted on this page today.
Participant capital, at launch, is programmatically segregated on-chain into predefined pools under encoded allocation logic. The specific ratios and operational rules are set out in the technical protocol documentation. No human operator modifies the allocation after deployment.
All economic rules are encoded before launch and cannot be modified by any operator thereafter. The code is subject to independent audit. The protocol is designed to run to the end of its cycle under the rules committed at deployment. No discretionary override is possible.
At the end of the five-year cycle, the protocol reconciles according to its encoded rules. Whether any surplus is distributed, and on what basis, depends on the performance of the on-chain treasury and the final protocol design approved by counsel. No specific financial outcome is promised to any participant.
Everything above is a summary. The full canonical mechanics — every number, every rule, every guarantee — are set out in two standalone reference documents. They are the single source of truth for the protocol. Written in plain language.
The plain-language version of where things stand and what your registration does.
You give us your name and email. You receive protocol documentation as it is published. That is all. No payment is requested. No commitment is created. No slot is guaranteed. No financial outcome of any kind is promised or implied.
A structuring and authorisation engagement with specialist counsel is under way. The final form of the protocol — including specific mechanics, eligibility, and jurisdictional reach — depends on the outcome of that engagement and on obtaining the authorisations it identifies.
No participant capital will be accepted before a satisfactory legal opinion has been obtained and published. If the required authorisations cannot be obtained in a form that is consistent with the commercial proposition, the protocol will not launch, and pre-registered users will be informed. Independent code audit will be commissioned and the audit report will be published before any participant is invited to transact.
Registration is free and non-binding. It simply records your interest and your position in the queue for when the protocol launches — subject to authorisation. No funds are accepted today.
Register Your InterestBitcoin Storm is not a fund, a DAO governed by committee, or a protocol built by anonymous contributors. It was conceived by a single person with a clear thesis: that the fairest way to run an on-chain capital protocol is to remove all human discretion from the equation entirely.
The protocol architecture — the capital flows, the treasury structure, the 5-year cycle — all of it is being designed with one principle: the rules are set before a single dollar enters, and no one, including me, can change them after that. The final form is subject to the outcome of ongoing legal review.
We're building this on the Internet Computer Protocol because it's the only infrastructure that makes that promise technically unbreakable. The code is the contract. The canister is the vault. There is no back door. Authorisation before launch — no participant capital accepted before legal opinion is in place.
Bitcoin Storm is an active build — a deterministic, on-chain protocol being developed on the Internet Computer. At full launch scale the capital architecture is designed to accommodate a substantial treasury. The infrastructure does not forgive mistakes — and neither does the code that runs it. All economic mechanics are subject to legal review before any participant capital is accepted.
We're assembling a small, elite group: a Director of Operations who owns everything that isn't code, and a core engineering team who understands that the best on-chain infrastructure is invisible, immutable, and unstoppable. If you've shipped on ICP, led technical teams under pressure, or built something that made people say "how is that possible on-chain?" — this is your storm to shape.
Every role goes through the same rigorous assessment. No exceptions. No shortcuts. The team locks before launch. The protocol launches only after authorisations are in place.
Due diligence template required · Remote · Global
Bitcoin Storm is being designed to operate entirely on-chain. If and when participation opens, participants would swap approved tokens directly into the protocol at entry — no credit cards, no bank transfers. The indicative whitelist below is under review and will be finalised in light of counsel advice. Individual assets may be added or removed before launch. This page is not an offer and no swap is available today.
| Symbol | Name | Chain | Type | What It Is | Status |
|---|---|---|---|---|---|
| ICP | Internet Computer | ICP | Governance | Native token powering the Internet Computer network | ✓ Launch |
| ckBTC | Chain-Key Bitcoin | BTC · ICP | Chain-Key | 1:1 Bitcoin wrapped natively on ICP — no bridges | ✓ Launch |
| ckETH | Chain-Key Ethereum | ETH · ICP | Chain-Key | 1:1 Ethereum wrapped natively on ICP — no bridges | ✓ Launch |
| ckUSDC | Chain-Key USDC | ETH · ICP | Stablecoin | USDC brought on-chain to ICP via chain-key cryptography | ✓ Launch |
| ckSOL | Chain-Key Solana | SOL · ICP | Chain-Key | Solana brought natively on-chain to ICP | ~ Launch |
| CHAT | OpenChat | ICP | SNS DAO | Governance token of OpenChat — decentralised messaging on ICP | ✓ Launch |
| SNS1 | SNS-1 | ICP | SNS DAO | The first SNS DAO on ICP — community governed | ✓ Launch |
| ICX | ICPSwap Token | ICP | DEX | Governance token of ICPSwap — the leading ICP DEX | ✓ Launch |
| SONIC | Sonic DEX | ICP | DEX | Token of the Sonic decentralised exchange on ICP | ✓ Launch |
| NUA | Nuance | ICP | SNS DAO | Decentralised blogging platform built on ICP | ✓ Launch |
| KINIC | Kinic | ICP | SNS DAO | On-chain search engine for the ICP ecosystem | ✓ Launch |
| HOT | Hot or Not | ICP | SNS DAO | Decentralised short-video social platform on ICP | ✓ Launch |
| BOOM | BOOM DAO | ICP | SNS DAO | On-chain gaming infrastructure DAO on ICP | ✓ Launch |
| DKP | Dragginz | ICP | SNS DAO | On-chain metaverse and gaming world on ICP | ✓ Launch |
| GHOST | IC Ghost | ICP | Meme · SNS | The original ICP meme coin — first SNS meme on Internet Computer | ✓ Launch |
| DOGMI | Dogmi | ICP | Meme · SNS | First dog-themed meme coin on ICP — strong community | ✓ Launch |
| BOB | Bob | ICP | Meme | Community meme token on ICP with active following | ✓ Launch |
| PANDA | IC Panda | ICP | Meme | ICP ecosystem meme token with growing liquidity | ✓ Launch |
| BURN | Burn Token | ICP | Meme · Deflationary | Deflationary meme token with burn mechanics on ICP | ~ Launch |
| BTC | Bitcoin | Bitcoin | Layer 1 | Native Bitcoin via ICP chain-key integration | ~ Launch |
| ETH | Ethereum | Ethereum | Layer 1 | Native ETH via ICP chain-key integration | ~ Launch |
| SOL | Solana | Solana | Layer 1 | SOL via cross-chain swap integration | ~ Launch |
| DOGE | Dogecoin | Multi | Meme · OG | The original meme coin — deep liquidity across all exchanges | ~ Launch |
| SHIB | Shiba Inu | Ethereum | Meme | Top meme coin by market cap — massive global community | ~ Launch |
| PEPE | Pepe | Ethereum | Meme | Cultural meme coin phenomenon — top 20 by market cap | ~ Launch |
| WIF | dogwifhat | Solana | Meme | Leading Solana meme coin — top tier liquidity | ~ Launch |
| BONK | Bonk | Solana | Meme | OG Solana meme coin — strong community and exchange presence | ~ Launch |
| FLOKI | Floki | Multi | Meme · Utility | Multi-chain meme coin with real utility ecosystem | ~ Launch |
| LINK | Chainlink | Ethereum | Oracle | Leading decentralised oracle network — deep liquidity | ~ Launch |
| UNI | Uniswap | Ethereum | DEX | Governance token of the largest decentralised exchange | ~ Launch |
| AVAX | Avalanche | Multi | Layer 1 | High-speed L1 blockchain with strong DeFi ecosystem | ~ Launch |
Four documents that explain the technical and conceptual context of the Bitcoin Storm design. Informational only — not an offer and not legal or financial advice.
"How participant capital is designed to be segregated, allocated, and tracked under encoded protocol rules."
Read →"The greatest expansions in financial history did not announce themselves. March 2026 is the mud."
Read →"When the hardest money in history merges with the most capable compute layer ever built, the result is multiplicative."
Read →"Bitcoin's 21 million cap is absolute. This protocol creates no synthetic exposure."
Read →Reported by Krebs on Security · Aikido Security · Tom's Hardware
In March 2026 a cybercrime group deployed live malware using an ICP canister as command-and-control infrastructure. What happened next is the most important proof Bitcoin Storm has.
A cybercrime group — CanisterWorm — deployed malware using the Internet Computer Protocol as its command-and-control layer. The canister ran live, served active targets, and operated continuously on-chain.
The NNS consensus layer never flinched. The protocol was untouched. The canister ran exactly as coded — including the malicious code — because that is what immutability means. No human could intervene, including DFINITY itself.
Access was eventually restricted at the Boundary node layer under the ICP Code of Conduct. Two separate layers. One immutable. One governed. Both working exactly as designed.
Common questions about the protocol, the registration, and where things stand. If something isn't covered here, the full protocol documentation in the library goes deeper.
Compliance, editorial, and development documentation suite.
By accessing this page or submitting a registration of interest, you agree to be bound by these Terms. If you do not agree, please do not use this page or submit the registration form.
The Bitcoin Storm is a pre-launch deterministic on-chain protocol being developed on the Internet Computer Protocol (ICP). The final form of the protocol is subject to the outcome of an active legal structuring engagement with specialist Gibraltar counsel. Until that engagement has produced an acceptable position and any required authorisations are in place, the protocol is not available for participation and no participant capital is or will be accepted. These Terms relate solely to the current pre-registration page and do not constitute the participation terms that will apply if and when the protocol launches.
This page collects your name and email address for the sole purpose of registering your interest in receiving protocol documentation as it is published. Submitting your details does not create any contractual commitment, confer any entitlement to participate, reserve any “slot” or position, create any right to any financial outcome, or give rise to any obligation on our part beyond the provision of informational updates. No payment is requested, accepted, or processed on this page.
Nothing on this page is or should be construed as an offer, solicitation, inducement, or recommendation to purchase, subscribe for, or otherwise acquire any security, financial instrument, crypto-asset, fund interest, gambling product, or any other regulated or unregulated product or service. The page is informational only.
Nothing on this page constitutes financial, investment, legal, tax, or other professional advice. All content is informational only and reflects the protocol design as currently contemplated. Any future protocol mechanics, if they are deployed at all, may differ materially from the descriptions on this page. Cryptocurrencies and digital assets are volatile and speculative. You should seek independent professional advice from appropriately qualified advisers before making any financial decision.
The Bitcoin Storm does not take, accept, or purport to take deposits and does not provide custody services. Participation, if and when it opens, would be effected by the swap of whitelisted on-chain tokens into the protocol treasury under encoded protocol rules — not by deposit, loan, or custodial arrangement. The protocol does not pay interest and does not offer any rate of return. No capital return is promised to any participant. No yield is promised. No financial outcome of any kind is promised. Whether any surplus is distributed at the end of the protocol cycle, and if so on what basis, depends on treasury performance under the encoded protocol rules and on the final design approved by counsel. Participation, if and when it opens, would carry substantial risk including the risk of total loss of capital.
Participation, if and when it opens, will not be available to persons resident or located in the United States, Canada, or any other jurisdiction where local law does not permit it. Participation will be restricted to persons aged 21 or over. Geographic and age restrictions will be technically enforced at launch. You are solely responsible for determining whether registration or participation is lawful in your location. We make no representation that this page or any future protocol participation is appropriate or lawful for use in all jurisdictions.
Participation will only open if and when (a) specialist counsel has delivered a satisfactory legal opinion on the regulatory classification of the protocol; (b) any required authorisations have been obtained in Gibraltar and any other relevant jurisdictions; (c) a Gibraltar operating entity has been established with named directors and a designated compliance officer; and (d) an independent code audit has been completed and its report published. If any of these conditions is not satisfied, participation will not open. Pre-registered users will be informed of any decision not to launch or of any material change in the protocol design.
All content on this page — including text, design, protocol concepts, and branding — is the property of The Bitcoin Storm. Unauthorised reproduction, distribution, or commercial use is prohibited without prior written consent. For licensing enquiries contact the email address published in the footer of this page.
To the maximum extent permitted by applicable law, The Bitcoin Storm, its founders, employees, and contributors shall not be liable for any direct, indirect, incidental, special, consequential, or exemplary damages arising from your access to or use of this page, or from any reliance placed on any information on this page. Our aggregate liability in connection with this page shall not exceed zero, as no financial transaction takes place on this page.
This page may contain forward-looking statements regarding the intended design, functionality, launch timing, and scope of The Bitcoin Storm protocol. Such statements are subject to significant uncertainty and change and are not promises or guarantees. Actual outcomes may differ materially from those contemplated on this page.
These Terms are governed by and construed in accordance with the laws of Gibraltar. Any disputes shall be subject to the exclusive jurisdiction of the courts of Gibraltar.
We reserve the right to update these Terms at any time. The date at the top of this document reflects the most recent revision. Continued use of this page after any change constitutes acceptance of the revised Terms.
This Privacy Policy explains how The Bitcoin Storm ("we", "us", "our") collects, uses, and protects your personal data when you use this website. We are the data controller for the purposes of the UK GDPR and EU GDPR.
When you submit a registration of interest on this page, we collect your first name and email address. We do not collect payment information, identification documents, or any sensitive personal data at this stage. We may also collect anonymous technical data such as page visit counts via analytics tools.
We process your name and email address on the basis of your consent — specifically, your act of submitting the registration form. You may withdraw this consent at any time by unsubscribing via any email we send you, or by contacting us directly. Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.
Your name and email are used solely to send you updates about the Bitcoin Storm protocol — including documentation releases, development progress, and, if and when participation opens in your jurisdiction, information about how to participate. We will not use your data for unrelated marketing, will not share it with advertisers, and will not sell it to any third party under any circumstances.
Kit (ConvertKit) — We use Kit (operated by ConvertKit, LLC, a US-based company) to manage our email list and send communications. When you submit the registration form, your name and email are transmitted to and stored by Kit. Kit acts as a data processor on our behalf. Kit is certified under the EU-US Data Privacy Framework and implements appropriate safeguards for international data transfers. You can review Kit's privacy policy at kit.com/privacy.
Google Fonts — This page loads fonts from Google Fonts. Google may collect your IP address as part of this request. We do not control Google's data practices. You can review Google's privacy policy at policies.google.com/privacy.
Netlify — This page is hosted on Netlify, which may collect server logs including IP addresses for security and operational purposes. You can review Netlify's privacy policy at netlify.com/privacy.
Kit (ConvertKit) is based in the United States. By submitting your registration, your data will be transferred to and processed in the US. This transfer is covered by appropriate safeguards under the EU-US Data Privacy Framework and UK adequacy provisions. If you have questions about these safeguards, contact us using the details below.
We retain your name and email for as long as you remain subscribed to our communications, or until you request deletion. Upon unsubscribing or requesting deletion, your data will be removed from our active list within 30 days. Anonymous analytics data may be retained for up to 24 months.
You have the following rights regarding your personal data:
Right of access — You may request a copy of the personal data we hold about you.
Right to rectification — You may request correction of inaccurate or incomplete data.
Right to erasure — You may request deletion of your personal data ("right to be forgotten").
Right to restriction — You may request that we restrict processing of your data in certain circumstances.
Right to data portability — You may request your data in a structured, machine-readable format.
Right to object — You may object to processing based on legitimate interests.
Right to withdraw consent — Where processing is based on consent, you may withdraw it at any time.
To exercise any of these rights, contact us at [email protected], or via Telegram @thebitcoinstorm. We will respond within 30 days.
If you are in the UK, you have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk. If you are in the EU, you have the right to lodge a complaint with your local supervisory authority.
We take reasonable technical and organisational measures to protect your personal data against unauthorised access, loss, or disclosure. However, no internet transmission is completely secure. Please do not submit sensitive personal information beyond your name and email address.
This page is not directed at persons under the age of 18. We do not knowingly collect personal data from minors. If you believe a minor has submitted data to us, please contact us at [email protected] and we will delete it promptly.
We may update this Privacy Policy from time to time. The date at the top of this document reflects the most recent revision. Continued use of this page after changes constitutes acceptance of the revised policy.
This Cookie Policy explains what cookies are, which cookies this page uses, and how you can control them. It should be read alongside our Privacy Policy.
Cookies are small text files placed on your device by a website. They allow the site to recognise your device on return visits, remember your preferences, and understand how you interact with the page. Some cookies are set by us directly; others are set by third-party services we use.
Essential cookies — These are necessary for the page to function and cannot be switched off. They include cookies that remember your cookie consent choice. Without these, parts of the page may not work correctly. No consent is required for essential cookies.
Preference cookies — These remember choices you make, such as your consent status. They are retained for up to 12 months.
Analytics cookies — If you consent, anonymous data about how you use this page may be collected to help us understand visitor behaviour and improve the page. No personally identifiable information is collected via analytics cookies.
Kit (ConvertKit) — When you submit the registration form, Kit may set a cookie or tracking pixel to confirm form submission and manage your subscription preferences. This operates under Kit's own cookie and privacy policy (kit.com/privacy).
Google Fonts — This page loads fonts from Google's servers. Google may set cookies or collect your IP address as part of this request. This operates under Google's privacy policy (policies.google.com/privacy).
Netlify — Our hosting provider may set technical cookies for security and operational purposes. These operate under Netlify's cookie policy (netlify.com/privacy).
You can accept or decline non-essential cookies using the banner shown when you first visit this page. You can also clear cookies at any time via your browser settings — most browsers allow you to refuse or delete cookies. Please note that disabling essential cookies may affect the functionality of this page.
For more information on managing cookies in your browser, visit allaboutcookies.org.
We do not use advertising, retargeting, or behavioural tracking cookies. We do not share cookie data with advertisers.
We may update this Cookie Policy as our technology or legal obligations change. The date at the top of this document reflects the most recent revision.