This is the proposed delivery model for the Bitcoin Storm marketing programme. The deliverable is one million paid founding participants in eighteen months. You sit at the top as Lead Operator. Beneath you sits a structured network of up to fifty sub-affiliates — small influencers, regional marketers, niche community operators — each capped at ten thousand paid users, each on a performance-tied retainer escalator, each paid a one-Bitcoin bonus on Bonanza Day if they hit ten thousand. Six of the highest-performing sub-affiliates are promoted to deputy roles, each overseeing approximately eight of the others, each eligible for an additional 1 BTC at Year 5 if their cohort segment delivers. They report to you. You orchestrate. The protocol pays.
The structure is designed so that you don't have to deliver one million users yourself, you have to deliver a system that does. You are the architect of the campaign and the owner of the result. Everything in this document is the proposed mechanic — what we believe is the most efficient distribution shape for a regulated capital protocol. It is offered as a proposal, not a mandate; if you take the role, you take the mechanics with the latitude of a Lead Operator to refine them.
One operator with one audience — even a very good one — cannot deliver one million paid users in eighteen months. The maths doesn't work, and the audience doesn't either. A single-voice campaign produces a single-shape audience; a regulated capital protocol with a five-year cycle and a $100 entry needs distribution that touches dozens of communities, multiple registers, and a wide spectrum of trust signals.
The conventional answer is to hire an agency or stand up a five-person KOL cohort. We've considered both and rejected both. Agencies optimise for billable hours rather than user count. KOL cohorts produce reputational dilution — everyone shares credit, no one owns the result, and the lead voice loses control of message and pacing. Neither structure matches the protocol's actual problem, which is: aggregate small audiences efficiently, without losing editorial control or compliance posture.
The proposed shape is different. One Lead Operator at the top — you — with full attribution authority and full sourcing control. Beneath you, up to fifty sub-affiliates, each running their own audience inside a tight commercial envelope you set. They don't compete with you, they extend you. You don't manage personalities, you manage performance against numbers.
The proposed structure is intentionally simple. Three layers.
Each sub-affiliate is a small operator with their own audience — a podcast, a newsletter, a regional marketing shop, a niche community manager. They are capped at ten thousand paid users each. No sub-affiliate becomes a critical dependency. If one underperforms or behaves badly, you exit the contract; the other forty-nine continue. If one over-performs, they hit the cap and the cap holds — the model rewards consistency, not viral spikes that are hard to govern and hard to attribute.
The deputy layer sits between you and the cohort. Six deputies, each overseeing approximately eight sub-affiliates. Deputies are not external hires — they are promoted from inside the contracted sub-affiliate cohort once you've identified the strongest operators. Each deputy keeps their own sub-affiliate retainer and their underlying 1 BTC bonus track; the deputy stipend ($3,000/month during bootstrap, ~$2,800/month from month five) is on top. Each deputy is also eligible for an additional 1 BTC at Year 5 if their cohort segment of approximately eight sub-affiliates collectively delivers at least 60,000 paid users — same conditional structure as your $12M (target hit AND protocol settles profitably). Total deputy budget across the engagement: $300,000 stipend pool plus 6 BTC contingent at Year 5. The bonus alignment is what turns the deputy role from a side-job into a genuine career-grade opportunity for the right sub-affiliates.
You decide who joins the network and who exits. You decide who gets promoted to deputy. You decide the pacing. You decide which jurisdictions get coverage and which don't. You report to the founder on programme-level performance; deputies report to you on cohort-segment performance; sub-affiliates report to deputies on individual delivery. One layer between you and direct supervision. One layer between you and the founder.
Each sub-affiliate operates on the same proposed deal: a retainer that escalates as paid users come in, hard performance gates that exit them if they stall, and a one-Bitcoin bonus paid on Bonanza Day if they hit ten thousand paid users.
The retainer starts small and rises with verified paid signups. The intention is simple: a sub-affiliate who isn't producing isn't earning, and a sub-affiliate who is producing earns enough to focus.
| Tier | Threshold reached | Monthly retainer |
|---|---|---|
| Probationary | 0–99 paid users | $500 / month |
| Tier 1 | 100 paid users | $1,000 / month |
| Tier 2 | 500 paid users | $2,000 / month |
| Tier 3 | 1,500 paid users | $3,500 / month |
| Tier 4 | 4,000 paid users | $5,500 / month |
| Tier 5 | 7,500 paid users | $7,500 / month |
| Cap reached | 10,000 paid users | Retainer stops · Bonus locks |
Tier promotions take effect from the first of the month following threshold confirmation. There is no demotion mechanism — once a sub-affiliate hits Tier 3, they stay at Tier 3 unless terminated. This protects them from short-term churn anxiety and lets them focus on long-form audience building.
Each sub-affiliate who delivers ten thousand paid users within the eighteen-month engagement window receives one Bitcoin on Year 5 Bonanza Day, paid from protocol surplus alongside the founding draw and daily distributions. This is the headline. Every sub-affiliate is recruiting against the same Bitcoin-denominated outcome you are.
The bonus is binary, not pro-rata. A sub-affiliate at 9,999 users at the gate date receives no bonus. This is deliberate — pro-rata bonuses produce a cliff at half delivery; binary bonuses produce a push to the cap. The structure rewards completion, not effort.
The escalator only works if it is paired with hard exit dates. The proposed gates are simple, public, and contractually binding:
You hold the authority to exit any sub-affiliate at any gate. The contract has no severance, no notice period beyond the current month's retainer, and no claim on the bonus. This is the entire mechanism by which the programme stays clean.
Attribution is the technical core of any affiliate model and the place programmes most often go wrong. The proposed mechanics are simple and verifiable.
Each sub-affiliate receives a unique referral link of the form thebitcoinstorm.io/?ref=XXX and a short alphanumeric promo code. The link captures click-through signups; the promo code captures users who heard about the protocol on a podcast or in a newsletter and arrived via search. A user is credited when their $100 entry swap is confirmed on-chain — not when they sign up for the email list, not when they complete KYC, not when they say they will. Once confirmed, the credit is permanent.
Because the protocol is structurally non-refundable — entry is a one-way token swap, not a deposit — there is no refund clawback to manage. A credited user stays credited. Attribution disputes between sub-affiliates resolve via timestamp and last-touch — whichever attribution event was most recent before the swap is the one that holds. You arbitrate any edge cases.
Sub-affiliates do not write their own protocol copy. They draw from a Storm Copy Library — pre-approved phrasing, claims, statistics, and disclaimers reviewed by counsel. They are free to speak to why they personally find the protocol interesting, in their own voice and register; they are not free to speak to what the protocol does in their own words. That distinction is the whole compliance posture of the programme.
The library is yours to maintain in collaboration with counsel. Sub-affiliates who deviate from the library — making yield claims, drawing comparisons to lottery products, asserting guaranteed returns — are exited immediately and forfeit the bonus. This is the only zero-tolerance clause in the proposed contract.
Multi-account signups, fake KYC submissions, and related-party signups are detected by the protocol's standard registration flow and do not count toward any sub-affiliate's tally. Restricted-jurisdiction signups (United States, Canada, others as specified) are blocked at the registration layer regardless of which referral link delivered them; sub-affiliates who attempt to recruit from restricted jurisdictions are exited.
The sub-affiliate structure does not replace the Lead Operator economics. It sits underneath them.
Your terms remain as proposed in the Lead Operator term sheet: $50,000 monthly retainer for up to eighteen months — the first four months funded personally by the founder so you carry no credit risk on the protocol, with months five onward paid from the ring-fenced Operating Fee Reserve — and a $12 million performance bonus at Year 5 Bonanza Day if the founding-million target is hit and the protocol settles profitably. Capped, paid from protocol surplus, never from participant capital.
The sub-affiliate retainers and bonuses are funded separately, from the same reserve and surplus structure. They are not deducted from your bonus. You are not paying out of your own number to make the system work — the system is a capital structure the protocol pays for, and you orchestrate it.
If the system delivers as designed — you at the top, fifty sub-affiliates active at various tiers, the founding million hit by month eighteen — the financial outcome to you is approximately:
| Component | Source | Approx. value |
|---|---|---|
| Monthly retainer (18 months) | Founder personal (mo. 1–4) + Operating Fee Reserve (mo. 5–18) | $900,000 |
| Year 5 performance bonus | Protocol surplus on Bonanza Day | $12,000,000 |
| Total to Lead Operator | — | ~$12,900,000 |
The bonus is conditional on hitting the user target and on the protocol settling profitably; the retainer is conditional on month-by-month delivery against the agreed campaign plan. No payment is made without delivery, on either side of the deal.
The deal only works if the Lead Operator has full operational control. The proposed grants of authority are explicit:
The structural intent is that you have everything you need to deliver, and nothing in the agreement creates a layer between you and the work. You are not running this for the founder; you are running this with the founder, alongside.
Most affiliate programmes in this space are open, uncapped, paid in stablecoin, and disconnected from the underlying product economics. This one is none of those things.
It is closed, not open. Capped at fifty sub-affiliates, recruited and vetted by you, with explicit termination rights. There is no public sign-up form. No race to the bottom. No spam vector.
It is capped per affiliate, not unlimited. Ten thousand paid users per sub-affiliate, no exceptions. The cap protects against a single sub-affiliate becoming a critical dependency or capturing disproportionate marketing influence. It also protects them from chasing volume past the point of credible audience trust.
It is paid in Bitcoin from protocol surplus, not stablecoin from operating cash. Every sub-affiliate's bonus is denominated in the same asset the protocol distributes. They are aligned with the protocol's success at Year 5, not just with their own sign-up rate.
It is gated, not perpetual. Sub-affiliates who stall are exited. There is no long tail of underperforming retainers eating the Operating Fee Reserve. The structure self-cleans.
It is editorially controlled, not laissez-faire. The Storm Copy Library is the compliance perimeter. Sub-affiliates speak in their own voice about why the protocol matters; they do not invent claims about what it does. This protects the protocol's regulatory posture, the sub-affiliates from accidental misrepresentation, and you from reputational exposure.
This document is a proposal — the proposed mechanics for the delivery model that sits beneath the Lead Operator role. The numbers and structures are recommendations from the founder's design notes, not contractual terms; they exist to give you a concrete picture of how the programme would run if you took it.
The next steps, if this is the kind of role and structure you would consider:
The two decisions are: (1) is this a role you would run, and (2) are these the right mechanics for it. Both are negotiable; both are yours to weigh. The proposal is offered with the latitude that any senior operator gets: take it as written, refine it, or push back on the parts that don't fit your reading of how to deliver.