The Model — In One Paragraph
A fixed $100 participation, capped at 10,000,000 participants. Capital is committed for a five-year cycle.
275 BTC distributed to 275 winners drawn from the founding cohort of one million — one Bitcoin to each winner, selected by sealed VRF on-chain, paid at Year 5 alongside the daily-draw winners.
1 BTC per sealed slot — 1,825 daily slots total across the five-year cycle, sealed by VRF against the full 10,000,000-participant universe from Day 1. Every participant has identical odds regardless of when they joined. Any sealed slot belonging to an unfilled position is re-drawn against actual participants at Year 5 so no winning slot is wasted. All Bitcoin (the 275 founding and the 1,825 daily) is purchased at Year 5 from treasury profit above cost basis — and only if profit is sufficient to cover the full 2,100 BTC obligation at Year 5 market price. If profit is insufficient, no Bitcoin is purchased and all profit instead flows into the pro-rata cash distribution.
Founding-million participants remain eligible for the daily 1 BTC draws across all five years — the founding draw and the daily draws are independent. A founding participant can win in both.
Year 5 surplus — whatever remains after the on-chain treasury satisfies its obligations is distributed: 20% to the founder, 80% to participants pro rata.
Downside honest: outcomes depend entirely on ICP market performance across the five-year cycle. If the Participant Pool does not appreciate above cost basis, there is no profit — no Bitcoin is purchased and no founder fee is paid. Participants share the pool pro rata (which may be less than $95). The $5 Operating Fee is consumed regardless. The $100 entry is at risk. No principal return is promised.
The Bitcoin distribution mechanics are subject to Gibraltar authorisation. If the required authorisation is not obtained, the protocol does not launch.
01
Classification
02
Custody
03
Promotion
04
AML / VASP
05
Tax
06
Operational
07
Governance
08
Jurisdictional
09
Consumer
10
Strategic
Regulators may attempt to classify the Bitcoin Storm under existing financial frameworks. Potential exposure areas include:
Exposure Areas
- Collective Investment Scheme (CIS): misinterpretation that capital is pooled for shared financial return
- Alternative Investment Fund (AIF): risk if capital deployment is viewed as discretionary asset management
- Security Classification: if profit expectation or reliance on managerial efforts is inferred
- Lottery / Prize Regulation: mischaracterisation of BTC allocations as chance-based rather than deterministic
- Future-Token Reservation Risk: the operating entity's reservation of right to consider issuing a token after the Year 5 settlement event must not be communicated in a way that could be construed as a token-offering announcement, a token-sale solicitation, or a representation regarding any specific terms, timing, value, or distribution of any future token
Specific Sub-Risks
Year 5 Participant Distribution Risk
The Year 5 pro-rata Pool distribution and 80% residual-profit allocation may be mischaracterised by regulators as a profit distribution or dividend. All documentation must consistently describe this as a deterministic protocol output governed by pre-defined Capital Architecture rules — not a discretionary allocation or performance bonus. Outcomes are contingent on ICP market performance; no specific profit amount is promised.
Founding Million Sealed Draw Risk
The 275 BTC sealed VRF draw exclusive to the first 1,000,000 participants may be mischaracterised as: (i) a regulated lottery or prize promotion — mitigated by the fact it is a deterministic protocol mechanic; (ii) an investment contract creating profit expectation — mitigated by the structural rule that Bitcoin is purchased only from treasury profit above cost basis; (iii) treasury performance risk — all participant-facing documentation must state that BTC payouts occur only if Year 5 profit is sufficient to purchase the full 2,100 BTC obligation, and are not guaranteed.
Mitigation
- Deterministic architecture documentation
- No token issued at launch — consistent communication that participation results in a non-transferable Engine slot, not a token
- Explicit "no profit rights" language in all disclosures
- Consistent articulation of capital architecture segmentation: $950M Participant Pool / $50M Operating Fee Reserve
Risk Considerations
- Allegations of indirect custody through structural control
- Interpretation of swap mechanics as capital pooling
- Misunderstanding of Engine Positions as financial instruments
Structural Position
- Users retain wallet control at all times
- No pooled custodial account exists
- Engine Positions are non-transferable and non-tokenised
- The $50M Operating Fee Reserve is predefined at intake and segregated from participant principal
Key Requirement
Audit transparency is critical to defending the custody position.
Risk Triggers
- Use of "returns," "yield," "profit," or "growth" terminology
- Implication of upside linked to capital performance
- Suggestion of managed investment structure
- Miscommunication around deterministic BTC allocations
Mitigation
- Standardised communications framework
- Prohibition of speculative phrasing
- Mandatory risk disclaimers
- Clear articulation of principal-first surplus logic
Potential Exposure
- Classification as VASP or equivalent depending on jurisdiction
- Large-volume transaction monitoring
- Sanctions screening obligations
- Wallet screening and blacklist requirements
- Cross-border regulatory reporting triggers
Extended AML Framework
Given the $1B aggregate intake capacity and up to 10,000,000 participant swaps, the Bitcoin Storm will require a robust AML compliance programme including: (i) VASP classification analysis under FATF Recommendation 15; (ii) appointment of a regulated KYC/AML technology provider with blockchain analytics capability (e.g. Chainalysis, Elliptic, or equivalent); (iii) transaction monitoring thresholds with SAR procedures in place prior to launch; (iv) real-time wallet screening against OFAC SDN, EU consolidated sanctions list, and UN sanctions; (v) geofencing — technical and legal restriction of access from jurisdictions where VASP registration has not been obtained.
Risks Include
- Swap events treated as disposals
- BTC allocations treated as income
- Year 5 settlement timing affecting cost basis
- Interpretation of the 20% Performance Fee under local tax law
- Cross-border reporting obligations
Participant Responsibility
Participants must independently assess local tax treatment. Bitcoin Storm does not provide tax advice.
Risk Factors
- Smart contract configuration errors
- Treasury allocation misconfiguration
- Cross-chain integration vulnerabilities
- Exploit attempts targeting allocation mechanics
- Infrastructure downtime
- Cybersecurity threats
Mitigation
- Independent code audits
- Multi-layer security review
- Continuous monitoring and reporting
Risks
- Founder influence interpreted as managerial discretion
- The 20% Performance Fee misinterpreted as performance compensation
- Centralised operational control concerns
- Transparency expectations from global regulators
Mitigation
- Clear documentation of deterministic execution
- Public reporting of capital flows
- Separation between governance and outcome calculation
- Optional transparency or DAO-style governance mechanisms where appropriate
Risk Considerations
- U.S. securities exposure
- UK financial promotion restrictions
- EU MiCA compliance requirements
- Singapore structured-product rules
- Canadian investment-contract interpretation
- Local licensing obligations in emerging markets
Mitigation
- Geofencing where required
- Targeted disclosures
- Jurisdiction-specific communication controls
Risks
- Participants perceiving the Engine as an investment
- Confusion between deterministic allocation and speculation
- Misinterpretation of surplus logic
- Inaccurate public messaging by third parties
Mitigation
- Prominent disclaimers
- Clear explanation of non-financial structure
- Removal of performance-oriented language
- Educational documentation
Risks
- Regulatory reinterpretation after launch
- Retroactive classification attempts
- Policy shifts affecting digital assets
- Increased scrutiny due to BTC allocation scale
Mitigation
- Conservative structural design
- Comprehensive documentation
- Multi-jurisdictional legal review
- Clear articulation of capital architecture segregation ($950M / $50M)
Conclusion — Core Compliance Defence
The Bitcoin Storm regulatory risk profile centres primarily on misclassification risk, not structural investment characteristics. The core compliance defence rests on five pillars:
| Defence Pillar | Status |
|---|
| Deterministic architecture — no human discretion over outcomes | ✓ Confirmed |
| No pooled ownership — capital pools are capital segments, not investment funds | ✓ Confirmed |
| No discretionary management — all logic encoded prior to launch | ✓ Confirmed |
| No profit rights — surplus distribution under fixed on-chain rules only | ✓ Confirmed |
| No token at launch — protocol entry results in a non-transferable Engine slot, not a token; future token reserved as a post-Year-5 possibility only | ✓ Confirmed |
Ongoing Requirements
Ongoing legal oversight, disciplined communications, and consistent documentation of Capital Architecture remain essential to maintaining regulatory clarity across all jurisdictions.