Read carefully. Sign once. Apply always.
This is the universal compliance posture for every sub-affiliate operating under the Bitcoin Storm Lead Operator. Every sub-affiliate signs this document on onboarding. Every entry from the Storm Copy Library inherits these rules and may layer additional asset-specific permissions on top — but never below them.
The rules below exist for three reasons. First, the protocol is regulated; every word published in its name must be defensible in front of counsel. Second, you are paid in Bitcoin from protocol surplus on Bonanza Day — protecting the protocol's regulatory standing protects your eventual bonus. Third, sub-affiliates speaking with one voice produces stronger marketing than fifty voices speaking differently.
Breach of any zero-tolerance clause results in immediate termination, retainer cessation, and forfeiture of the Bitcoin bonus. The Lead Operator has full authority to enforce. There is no appeals process for zero-tolerance breaches.
Section 01 · What You Can Always Do
Things every sub-affiliate is free to do.
The following are universal permissions that apply to every entry in the Storm Copy Library, regardless of platform, audience, or mechanic. Where individual library entries grant additional permissions, those layer on top of these.
- Use any approved Storm Copy Library entry verbatim on the platform it was approved for.
- Speak in your own voice about why you find the protocol interesting, your reaction to its design, your aesthetic or philosophical view. Personal opinion on the protocol's existence is yours to express.
- Append your unique referral link (
thebitcoinstorm.io/?ref=XXX) and/or your promo code to any post.
- Use the official logo, screenshots, and brand assets from the official asset folder only.
- Link to thebitcoinstorm.io and any of its public documents (whitepaper, risk register, compliance whitepaper, etc.).
- Quote any text directly from the protocol's public documents with proper attribution.
- Direct interested parties to the official channels: thebitcoinstorm.io, the OpenChat / Telegram / X handles, the public documentation set.
- Disclose your sub-affiliate status openly. Honesty about the relationship is required (see Section 03), not optional.
- Discuss publicly disclosed protocol economics — the $100 entry, 10M cap, 5-year cycle, 80/20 surplus split, 10% charity earmark — using the language of the public documents.
- Decline to post any specific asset you do not personally support. Sub-affiliates retain editorial conscience.
Section 02 · What You Can Never Do
The zero-tolerance clause.
The following list is the regulatory perimeter of the programme. Any breach is grounds for immediate termination, no notice, no severance, no Bitcoin bonus. The Lead Operator's decision is final. Read this section twice.
- Describe the protocol as a lottery, sweepstake, raffle, gambling product, or game of chance. The protocol is not any of these.
- Imply or assert any guaranteed return, yield, interest, or rate of any kind.
- Use the words "investment," "fund," "deposit," or "savings" to describe the protocol, or any synonym for these.
- Claim the protocol "guarantees" any specific BTC distribution — all BTC purchases are conditional on Year 5 treasury appreciation; this conditionality must never be stripped from any communication.
- Make ROI, expected value, or comparative odds claims against any other product, including other crypto products, savings accounts, traditional investments, or gambling products.
- Rewrite protocol mechanics in your own words. You may speak about why you find the mechanic interesting; you may not speak about what the mechanic does. Mechanic descriptions must come from approved Library assets only.
- Recruit users from restricted jurisdictions — United States, Canada, and any others specified by the protocol's geographic restriction list. Targeting these markets, including via geo-targeted ads, is a hard breach.
- Post without your referral attribution. Uncredited posts do not count toward your tally and may be treated as evidence of off-channel recruiting.
- Combine the protocol with any third-party product, exchange, custody service, financial offer, or unrelated promotion. The protocol is presented standalone or not at all.
- Run paid ads on any platform without explicit Lead Operator written approval. Organic posting is the default; paid amplification is gated.
- Use the protocol's brand for engagement-farming: giveaways, follow-for-follow campaigns, fake testimonials, paid amplification networks, comment-pod tactics.
- Speak to media or press on behalf of, or about, the protocol without Lead Operator written approval and counsel review.
- Make protocol-related claims about regulatory status beyond what is published in the official documents (e.g., "Gibraltar-authorised" when the public position is "authorisation pending").
- Encourage participation by anyone you reasonably believe to be vulnerable, in financial distress, under 21, or otherwise not the right participant for a five-year capital protocol with risk of total loss.
- Pose as the founder, the Lead Operator, or any official spokesperson. Always identify yourself as a sub-affiliate; never speak with the authority of the protocol itself.
Section 03 · Disclosure Requirements
Tell people they are looking at an ad.
Sub-affiliates are paid for paid signups. That makes you a paid promoter under UK ASA, US FTC, EU DSA, and equivalent regulators worldwide. Disclosure is non-negotiable. The discipline of disclosure also protects the protocol's regulatory posture — an undisclosed sub-affiliate post is materially worse than no post at all.
Required disclosure
Every post, video, podcast read, newsletter, email, or any other piece of content where you mention the Bitcoin Storm must include one of the following, visibly and unambiguously:
- #ad — placed at the top of any social post, before the body text, not buried at the end.
- #paidpartnership — equivalent on platforms where #ad is contested.
- "Paid affiliate of Bitcoin Storm" — on long-form content (videos, podcasts, newsletters), spoken or visible at the start of the segment.
- Platform-native paid-partnership tag — YouTube paid promotion disclosure, Instagram branded content tag, X "Promoted" label, etc., where the platform offers one.
- Written disclosure in the first 100 words for written articles, blog posts, and newsletters: "I am a sub-affiliate of Bitcoin Storm. If you participate via my link, I receive performance-based payment."
Disclosure must be present in the same medium as the message. A disclosure on your bio page does not count for an individual post. A disclosure in episode notes does not count for a podcast read. Each unit of content carries its own disclosure.
Section 04 · Tone & Voice
Sound like yourself, not like a brochure.
The protocol's voice is measured, declarative, and quietly confident. Sub-affiliates are not asked to mimic it — you were recruited because your voice has earned an audience — but you are asked to keep within a register the protocol can stand behind.
Tone permissions and limits
- Speak in your own register — casual, editorial, technical, contemplative, whatever has earned your audience.
- Express genuine personal opinion: "I find this interesting because..."
- Acknowledge complexity. The protocol rewards thoughtful framing more than aggressive promotion.
- Reference the protocol's documents directly — readers who care will read; readers who don't won't be persuaded by overclaim anyway.
- Be honest about risk where it comes up. The protocol is up-front about it; you should be too.
- No urgency manufacturing beyond what the mechanic itself produces. The 1M cohort cap is genuinely time-bounded; "buy now or miss out" framing on top of that is amateur.
- No shilling cadence — do not post the protocol multiple times per day, do not flood your own audience.
- No FUD against competitors or comparable products. The protocol stands on its own merits.
- No emotional manipulation: do not target loneliness, fear, greed, or status anxiety.
- No fake personal stories, fabricated case studies, or invented testimonials.
- No engagement-bait framing: "Like if you agree", "Repost if you understand", "Tag a friend who needs this", etc.
Section 05 · Frequency & Pacing
How often, and when.
The Lead Operator sets the campaign calendar. Sub-affiliates work within it. Outside the campaign calendar, default rules apply.
- Maximum one Bitcoin Storm post per day per platform per sub-affiliate.
- Minimum three days between repeats of the same Library asset. Variations and different assets do not count as repeats.
- Long-form content (podcasts, newsletters, videos): no more than one Bitcoin Storm segment per week unless coordinated through the Lead Operator.
- Coordinated campaign moments (e.g., countdown to the millionth slot) override defaults — the Lead Operator will issue specific cadence guidance for these.
- Quiet periods may be called by the Lead Operator (e.g., during regulatory reviews, audits, sensitive news cycles). All sub-affiliate activity pauses on a Lead Operator quiet-period instruction within 24 hours of receipt.
Section 06 · Attribution & Reporting
How you get credited.
Attribution is the technical core of how you get paid. The mechanics are simple, on-chain, and verifiable.
- 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. On-chain confirmation is the trigger.
- Once confirmed, attribution is permanent. The protocol is non-refundable by design; there is no clawback mechanism.
- Last-touch attribution holds. If a user clicks two referral links before paying, the most recent click before swap confirmation is the credited link.
- Promo code overrides link. If a user arrives via one referral link but enters a different sub-affiliate's promo code at registration, the promo code wins.
- The Lead Operator arbitrates all disputes. Attribution edge cases resolve to the Lead Operator's decision. Final and not subject to founder review.
- Multi-account, fake KYC, and related-party signups are detected by the protocol's standard registration flow and do not count toward your tally.
- Restricted-jurisdiction signups are blocked at the registration layer regardless of which referral link delivered them. They never count.
Reporting
Sub-affiliates receive a monthly statement from the Lead Operator showing: paid users credited, current tier, retainer due, distance to the next tier threshold, distance to the 10,000 cap, and gate-status against the upcoming performance gate. Disputes are raised within seven days of the statement; after that the statement is final.
Section 07 · If Something Goes Wrong
The escalation path.
Things will go wrong. A piece of content will be wrong, a user will complain, a regulator will ask a question, a competitor will write a hostile post. The escalation path exists so that sub-affiliates know exactly what to do.
- If you make a mistake in posted content — wrong claim, missing disclosure, accidental zero-tolerance breach — notify the Lead Operator immediately and delete the offending content. Self-reported breaches are treated more leniently than discovered breaches. The Lead Operator decides whether termination applies.
- If a user complains, do not respond on the platform. Forward the complaint to the Lead Operator within 24 hours. The Lead Operator and / or counsel will decide on the response.
- If a regulator contacts you in connection with the protocol, do not respond beyond confirming you received the contact. Forward immediately to the Lead Operator and to legal contact (provided on onboarding).
- If press contacts you, do not respond. Direct all press to the Lead Operator.
- If a competitor or critic posts hostile content, do not respond on the platform. The protocol does not engage in public disputes. Forward concerning posts to the Lead Operator if you believe a structured response is warranted; otherwise ignore.
- If you discover another sub-affiliate breaching these rules, raise it with the Lead Operator. Do not call them out publicly.
- If you have any doubt about whether a planned post is within these rules, ask the Lead Operator before posting. The cost of asking is minutes; the cost of getting it wrong is termination.
Section 08 · Acknowledgement & Signature
Sign once. Carries forever.
By signing below, the sub-affiliate confirms they have read, understood, and accepted the Sub-Affiliate House Rules in full. The rules apply for the duration of the engagement and survive any termination — specifically, the confidentiality, attribution-dispute, and zero-tolerance enforcement clauses continue beyond contract end.
The rules may be updated by the Lead Operator with seven days' written notice. Continued participation after the notice period constitutes acceptance of the update. Sub-affiliates who do not accept an update may exit without penalty during the notice period.
Signed and acknowledged
Sub-Affiliate Signature & Date
Lead Operator Counter-Signature & Date
Sub-Affiliate Trading Entity (if any)