733 million people go to bed hungry tonight. Not as a statistic. As a fact. Bitcoin Storm is a protocol built to generate wealth. The Storm Community Fund is the acknowledgement that generating wealth at scale carries a responsibility — one that does not depend on anyone's goodwill to execute. It is built into the settlement mechanics. It is yours to direct. It cannot be redirected by anyone else. And every charity that receives it must operate on a standard of on-chain transparency that the sector has resisted for decades.
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.
There are facts about the world that most people know in the abstract but rarely sit with. Numbers that appear in reports, get cited in speeches, and then disappear behind the next headline. We are going to put them here, plainly, without softening them.
These are not acts of God. They are the outcomes of systems — financial, political, distributional — built by people. The question is never whether the money exists. It always exists. The question is whether there is a mechanism to move it toward the people who need it — one that cannot be captured, redirected, or quietly forgotten.
Bitcoin Storm is a financial protocol. But a protocol that may accumulate a treasury measured in billions carries an obligation that goes beyond its participants. The Storm Community Fund is how Bitcoin Storm meets that obligation — and it does so in a way that no pooled vote, no foundation, and no founder can replicate.
At the Year 5 settlement, after every obligation has been honoured — all 1,825 daily draw winners paid, all contingent Year 5 distributions processed, all interest settled, Performance Fee made — the remaining treasury surplus is divided equally among all 10 million participants.
Each participant receives their share into their Storm wallet. But 10% of that individual share arrives locked. It is yours — entirely, legally, unconditionally yours — but the protocol will not release it until you direct it to a qualifying charity of your choice.
You open your Storm wallet. You browse the qualifying charity registry — searchable by cause, region, and organisation type. You choose one charity or split your locked amount across several. You confirm. If the charity operates a dedicated ICP wallet (the locked route — described in detail in Chapter 05), the protocol releases the funds directly to the charity's wallet on-chain. If the charity operates outside the on-chain rail (the unlocked route — described in Chapter 07), the portion you directed releases from your Storm wallet to your own verified bank account, and you transfer it to the charity by traditional means. Either way, the locked-until-directed commitment holds. Either way, the on-chain record of where you directed your portion is permanent, public, and verifiable by anyone.
No committee decides for you. No governance vote can override your choice. No founder can redirect your 10% to a cause they prefer. It is yours to direct, to the cause you believe in, in the amount the protocol calculated as your share.
The Participant Pool holds 95% of the treasury in ICP. In a strong ICP cycle that pool does not stay at its entry value. At the Year 5 settlement, after all protocol obligations are met, the surplus depends on how far ICP has appreciated and how much of the 10M capacity has been filled. Below are three honest scenarios.
The Storm Community Fund is not a feature. It is a settlement mechanic — as fixed and automatic as the daily draw payout. Here is the complete sequence.
The model described so far would work even if every charity in the registry handled donations the way charities have always handled donations — mixed into general operating accounts, audited annually after the fact, reported on twelve months later in a glossy summary. The Storm Community Fund could distribute $1 billion through that system and the mechanics would still execute. But it would miss the larger opportunity.
The protocol that distributes the money runs on-chain. Every transaction is verifiable in real time. Every Storm participant who directs their locked 10% knows exactly when it left their wallet, where it went, and how much arrived. To then drop that money into a black box at the receiving end — where what happens next is reported quarterly, annually, or never — is a contradiction. The Storm Community Fund holds its receiving charities to the same standard the protocol holds itself to.
To be listed in the Storm Charity Registry — and therefore eligible to receive any portion of the locked 10% from any Storm participant — an organisation must operate a dedicated ICP wallet, on the Internet Computer Protocol, specifically for Storm-routed donations. This is non-negotiable.
The requirement applies regardless of whether the charity already accepts cryptocurrency through other channels, runs a fiat-only operation, or has its own internal donation infrastructure. None of that disqualifies them. None of that satisfies the requirement either. Storm donations arrive into an ICP wallet whose entire purpose is Storm donations, and whose every inflow and outflow is publicly visible on the Internet Computer blockchain in perpetuity.
In practical terms, this means an ICP-native account and wallet address — an account on the Internet Computer Protocol where the dedicated wallet can receive ICP and ICP-issued stablecoins. Setting one up is straightforward and free. Any charity unfamiliar with the process will find step-by-step guidance in the Storm Charity Registry application materials, including wallet creation, address verification, security setup, and disbursement workflows. No technical background is required to operate the wallet day-to-day. The Storm Community Fund operates a support channel for registered charities through the protocol cycle to assist with operational questions as they arise.
Traditional charity audit standards are retrospective. An organisation publishes its annual accounts twelve months after the fact, with auditor sign-off. Donors must trust that the period between gift and report has been handled with integrity, with no real-time mechanism to verify it.
The dedicated Storm wallet is continuous. Every Storm participant who directed funds to a charity can check that charity's wallet at any moment — the day after they donated, six months later, six years later. They see the exact balance. They see what's gone out. They see where it went next, if it left the wallet on-chain. The audit cycle moves from annual to permanent, from retrospective to live.
This isn't a comment on the integrity of existing charity audit practices. Most charities run audited and well-governed operations. The point is that on-chain transparency is a different standard — not a higher-quality version of the same audit, but a structurally different audit cycle. Storm participants are participating in a deterministic on-chain protocol. The charitable distribution leg of that protocol matches the same standard.
With a Year 5 surplus of $10 billion, the Storm Community Fund channels $1 billion of charitable distribution through wallets that meet this standard. The cumulative attention on those wallets — from 10 million donors, journalists, regulators, and the charity sector itself — creates a transparency reference point that no single donor, foundation, or government has been able to establish on its own.
Some major charities have, in fact, already moved in this direction. UNICEF's CryptoFund has accepted and disbursed cryptocurrency on-chain since 2019. The UN World Food Programme runs Building Blocks, an on-chain aid distribution system, in active operation across multiple refugee contexts. The infrastructure to operate transparent on-chain wallets is not exotic, and the largest humanitarian organisations are not as far from this standard as outside observers often assume. For charities operating at the scale the Storm Community Fund engages with, listing represents an opportunity to publicly demonstrate the transparency posture donors increasingly expect — rather than an operational ask they have never seen before.
The pace of broader sector adoption will be progressive rather than instantaneous. Mid-tier charities — smaller national bodies, specialist organisations, regional bodies — face genuine operational considerations: existing treasury policies, audit firm capability, finance team training. These are solvable, but they take time. The Storm Community Fund creates the demand pull and the public reference point. The sector responds at the pace it responds. Over a five-year cycle and successive cycles after that, the on-chain transparency standard moves from novel to expected across an increasing share of the charitable sector. Not because anyone forced it. Because donors, given the choice, will increasingly direct their money toward organisations operating to that standard.
The dedicated wallet requirement does create entry friction for the smallest charitable organisations — the local food banks, single-cause local charities, and small specialist bodies that may lack the operational capacity to manage on-chain infrastructure. That is a real cost, and it deserves explicit acknowledgement. The Storm Community Fund operates the standard it operates because the alternative — lowering the standard to accommodate every potential recipient — would defeat the structural point. But Storm participants retain the other 90% of their Year 5 share, free of any restriction, to direct through any traditional charitable channel they choose. The dedicated wallet requirement applies to the locked 10% routed through the Storm Charity Registry. It does not constrain how participants give the rest of their money, or where.
The Storm Charity Registry application opens following Gibraltar Financial Services Commission authorisation of the protocol. The registry is not live before that point.
Charities wishing to register early interest can email charities@thebitcoinstorm.io with the organisation name, registered jurisdiction, primary mission area, and a contact point. You will be added to a pre-launch interest list and contacted directly as soon as applications open, with the full setup guidance — ICP wallet creation, address verification, security setup, disbursement workflows — provided alongside the application materials.
No commitment is implied by registering interest. The pre-launch list is a courtesy — we want charities ready to be listed on Day 1 of authorisation rather than scrambling to set up infrastructure when participants are already directing donations.
The Storm Charity Registry is open — any organisation that meets the criteria can apply for listing. The criteria are objective, verifiable, and encoded before launch. No discretion. No founder preference. No lobbying. If you meet the criteria, you are listed.
The registry will be seeded before launch with a pre-verified set of globally recognised humanitarian organisations — UN World Food Programme, Médecins Sans Frontières, Red Cross, UNICEF, and others meeting the criteria — so that participants have immediate choices available from Day 1. Any qualifying organisation can apply to be added at any time during the protocol cycle.
The dedicated ICP wallet requirement described in Chapter 05 is structurally non-negotiable for the main Storm Charity Registry. The transparency standard the protocol applies to itself extends to every charity that benefits from it through the on-chain rail — that argument was made and stands.
But the registry exists to serve the participant's choice, not to limit it. There is a second category of organisation the main rail systematically misses: the smaller charities, the local bodies, the operations doing direct work whose internal capacity, treasury policy, or operating context makes a dedicated ICP wallet impractical. Local food banks. Single-cause specialist bodies. Regional bodies serving niche populations. Charities operating in jurisdictions where public crypto association affects donor demographics, or in environments where transparent on-chain operations could compromise the people they serve. For each of these reasons — some operational, some principled — legitimate charities will not adopt the dedicated wallet model. They should not be excluded from the Storm Community Fund because of it.
This chapter describes how those charities are reached, while preserving the integrity of the locked 10% earmark and the transparency the protocol commits to.
The Storm Charity Registry is a single list. Every approved charity appears in it. When a participant browses the registry, each entry is visually flagged as either locked-route (a charity operating a dedicated ICP wallet, receiving funds on-chain) or unlocked-route (a charity that has elected not to operate an on-chain wallet and receives funds via traditional banking rails). The participant sees both clearly, browses both equally, chooses freely between them. Splits across multiple charities are allowed in either direction or in any mix.
When the participant clicks an unlocked-route charity, a short message appears explaining what the choice means in practical terms:
The participant confirms the choice. The portion they directed to that charity releases from the locked Storm wallet to their own verified bank account at the prevailing on-chain market rate. They transfer it to the charity by whatever means the charity accepts. The on-chain record retains permanent evidence of the participant's direction (which charity, what date, what amount), even though the final transmission happens off-chain.
An earlier draft of this chapter described a Storm-operated Small Charities Pool — the protocol receiving allocated funds, holding them, converting to fiat, and disbursing them quarterly via bank transfer to small-charity beneficiaries. That model created custodial responsibilities and money-services-business obligations that would have required separate regulatory permissions and added counterparty risk. The current model removes all of that. The Storm never holds, custodies, or transfers any portion of unlocked-route funds. The participant does. The Storm's role is to publish the verified beneficiary list, flag the route at the point of choice, release the locked portion on direction, and record the on-chain evidence of where it was directed. Beyond that, the transmission is the participant's responsibility — with the participant's tax-relief eligibility intact and the charity's existing donation infrastructure unchanged.
The unlocked route serves a second purpose alongside operational practicality. Some charities will value it because it allows them to receive Storm-routed funds without publicly advertising the source. Their listing on the Storm Charity Registry is public. Their inclusion is verifiable. But they are under no obligation to mention the Storm on their own communications, integrate Storm branding, or make any public announcement about their participation. They simply receive bank transfers from individual donors, which they account for in their own books as ordinary philanthropic income. For organisations whose donor demographics or operating jurisdictions make crypto-association undesirable, this matters. The Storm does the public list. The charity does the charitable work, with no operational or reputational obligation to advertise their inclusion.
This is not opacity. The system is fully visible to anyone curious enough to look at the published registry and the public flow dashboard. It is, instead, quietness — the option for charities to receive funds without amplifying the source, while the source itself remains on the public record for any observer or regulator who wants to confirm it.
Unlocked-route applications open following Gibraltar Financial Services Commission authorisation of the protocol, on the same timeline as the main registry. Charities wishing to register early interest can email smallcharities@thebitcoinstorm.io with the organisation name, registered charity number, jurisdiction, primary mission area, three years of operational history, the bank details to be published alongside the listing, and a contact point.
No technical setup required. No public association with the Storm required. The Storm's role is to publish the verified listing and record on-chain direction events; everything else — the donor receiving the bank transfer, the charity confirming receipt, the operational fundraising relationship — remains a matter between the donor and the charity, the way charitable giving has always worked.
The alternative — a community governance vote that pools all charitable allocation and decides collectively — sounds democratic. In practice it concentrates power, rewards whoever can mobilise the most votes, and produces a mandate that may represent only a fraction of participants. A 20% turnout vote on a $1 billion allocation is not a mandate. It is a capture opportunity.
The individual locked wallet model avoids every one of those failure modes.
It is constitutionally fairer. A participant in rural Kenya and a participant in London each receive their share and each direct their 10%. The person with a larger surplus share directs more in absolute terms — but the decision is theirs alone, made on equal terms with everyone else.
It is legally cleaner. A pooled governance vote moving $1 billion to third parties raises complex questions about liability and fiduciary responsibility. Individual charitable giving at scale — each participant directing their own locked portion — is a well-understood legal mechanism in virtually every jurisdiction.
It creates a moment rather than a statistic. A governance vote produces a transaction. The individual model produces 10 million moments — people sitting with money that is provably theirs, choosing who receives it. People will talk about it. They will share the charity they chose and why. It becomes part of the Bitcoin Storm story in a way a committee decision never could.
The Storm Community Fund is encoded into the settlement mechanics before the canister launches following completion of regulatory authorisation. The following commitments will be verified by independent audit prior to launch and cannot be altered by any operator or governance action after that point.
Bitcoin Storm is built to make money for its participants. The Storm Community Fund is the acknowledgement that making money at scale carries a responsibility that goes beyond the participants. Ten percent of surplus is not a sacrifice. At $10 billion it is $1 billion — directed by 10 million free decisions toward the people the financial system was never designed to reach.
That is what the Storm can do. That is what it will do.