How to Register a Blockchain-Based Securities Offering with the SEC Under Regulation D (Rules 506(b) vs. 506(c))
Most blockchain-based securities offerings in the U.S. can be sold without SEC registration by relying on Regulation D—most often Rule 506(b) or Rule 506(c)—and filing a Form D within 15 days after the first sale. Reg D is a “safe harbor” exemption that still requires strict compliance with investor eligibility, solicitation limits, and anti-fraud rules. This article explains how to structure, document, and file a Reg D token offering, comparing 506(b) vs. 506(c) and highlighting common compliance pitfalls.
Regulation D and “Blockchain-Based Securities”: the Starting Point
When a startup issues tokens (or token-linked notes/SAFTs) to raise capital, the legal question is rarely “Is this on a blockchain?”—it’s whether the instrument is a “security” under federal law. Many token offerings are treated as securities offerings because purchasers reasonably expect profits based on the efforts of others (a classic Howey-type analysis). Once an offering is a securities offering, the default rule is SEC registration unless an exemption applies.
Regulation D (“Reg D”) is the most common pathway for U.S. private placements, including blockchain-based offerings, because it offers a predictable exemption framework and federal preemption of most state registration requirements for Rule 506 offerings (states can still require notice filings and fees). In practice, most token issuers choosing Reg D are deciding between:
- Rule 506(b) (no general solicitation; allows some non-accredited investors if sophisticated and disclosures are provided), and
- Rule 506(c) (general solicitation permitted; all purchasers must be accredited investors and the issuer must verify accredited status).
What “Registering” Means Under Reg D (and What It Doesn’t)
Reg D is not “registration” in the sense of an IPO registration statement. It is an exemption from registration. The key filing is Form D, a notice filing submitted electronically on the SEC’s EDGAR system after sales begin.
That distinction matters: you do not get SEC “approval” for a Reg D token offering. Compliance depends on meeting the exemption’s conditions, providing accurate disclosures, and ensuring marketing and sales practices match the chosen rule.
Rule 506(b) vs. Rule 506(c): A Practical Comparison for Token Issuers
Rule 506(b): Private offering—no general solicitation
Rule 506(b) is the traditional private placement exemption. It allows an issuer to sell to an unlimited number of accredited investors and up to 35 non-accredited investors who are sophisticated (or have a purchaser representative). However, including non-accredited investors triggers heightened disclosure expectations similar to registered offerings in many situations.
Key tradeoffs for blockchain offerings:
- No general solicitation (no public marketing). Token projects with active communities must be careful: broad social media promotion that “conditions the market” can be treated as solicitation.
- Investor mix flexibility may help if strategic community members are not accredited, but it increases disclosure and liability sensitivity.
- Verification burden is lighter: issuers can generally rely on investor self-certification (e.g., accredited investor questionnaire), provided they reasonably believe the investor is accredited.
Rule 506(c): Public marketing allowed—verification required
Rule 506(c) permits general solicitation (public ads, demo days, podcasts, community announcements), but every purchaser must be accredited and the issuer must take reasonable steps to verify accredited status. This is often attractive for token issuers with large online followings—if they can operationalize verification.
Key tradeoffs for blockchain offerings:
- Marketing flexibility aligns with community-driven fundraising, but messaging must still avoid misstatements and exaggerated performance claims.
- Accredited-only sales may exclude many community members, particularly retail token enthusiasts.
- Verification is not optional: “check-the-box” questionnaires alone are generally insufficient.
Quick decision matrix
Choose 506(b) if you can keep fundraising relatively private and want flexibility to include a limited number of sophisticated non-accredited investors (with robust disclosures). Choose 506(c) if you plan to publicly market the raise and can implement accredited investor verification workflows.
Step-by-Step: How to Conduct a Reg D Blockchain Securities Offering
1) Define the security and the offering structure
In blockchain fundraising, the “security” may be:
- Token purchase agreement for future delivery (often discussed as a SAFT-like structure, though labels do not control legal outcome),
- Token-linked SAFE or note,
- Equity in the issuer (sometimes bundled with token rights), or
- Revenue-sharing or profit-interest instruments.
Structuring choices impact disclosures, transfer restrictions, custody/escrow mechanics, and the path to eventual token distribution. Work backward from operational reality: when will tokens be minted, who controls smart contract admin keys, how are proceeds used, and what rights do purchasers receive?
2) Select 506(b) or 506(c) and align marketing accordingly
Before you post about the raise, decide which rule you are using. Under 506(b), avoid public announcements like “We’re raising” on X/LinkedIn/Discord, broadly distributed pitch decks, or “open invite” webinars. Under 506(c), you may market publicly—but you must gate actual purchases behind verification and subscription processes.
Practical example: A DePIN project with 50,000 Discord members wants to announce the raise publicly. That profile generally fits 506(c) better—provided the project can verify accredited investors and sell only to them. If the same project instead wants to sell to a handful of known crypto funds and angels through warm introductions, 506(b) may be workable.
3) Prepare offering documents: PPM (often), subscription package, and token disclosures
Reg D does not always require a Private Placement Memorandum (“PPM”), especially when selling only to accredited investors, but a well-drafted disclosure package can materially reduce litigation and enforcement risk. Token offerings frequently require extra risk disclosure due to technical and regulatory uncertainties.
Common document set:
- Private Placement Memorandum (PPM) (or offering memo) describing the business, token utility (if any), economics, and risks.
- Subscription Agreement (investor representations, legends, transfer restrictions, AML/KYC covenants, risk acknowledgments).
- Accredited Investor Questionnaire (506(b)) or verification procedures and certifications (506(c)).
- Token purchase/SAFT-like agreement with delivery conditions, network milestones, lockups, and transfer restrictions.
- Side letters (if needed) for strategic investors—carefully drafted to avoid inconsistent rights or disclosure gaps.
Token-specific disclosure topics commonly expected by sophisticated investors (and relevant under anti-fraud rules): smart contract risks, admin key control, audit status, token supply schedule, vesting, insider allocations, market-making plans, exchange listing uncertainty, sanctions exposure, and how the project will handle forks, airdrops, or protocol changes.
4) Build investor onboarding: KYC/AML, OFAC screening, and wallet controls
Although Reg D is a securities exemption, token offerings often face heightened expectations around compliance operations. Many issuers implement:
- Customer identification/KYC and OFAC sanctions screening,
- Source-of-funds checks for higher-risk subscriptions,
- Wallet address collection and screening (where tokens are delivered),
- Geofencing and contractual restrictions to prevent prohibited jurisdictions.
These steps can mitigate enforcement and reputational risk, and they can be critical if the token might later trade or be distributed more broadly.
5) Enforce transfer restrictions and “restricted securities” handling
Securities sold under Rule 506 are typically restricted securities. Investors cannot freely resell them into public markets without an exemption (commonly Rule 144, subject to holding periods and other conditions) or registration.
For tokenized securities, transfer restrictions may need both:
- Contractual controls (legends, lockups, covenants), and
- Technical controls (smart-contract whitelisting, transfer hooks, or transfer agent-style controls) to prevent immediate secondary trading that could undermine the exemption or create broker-dealer/exchange issues.
6) File Form D on EDGAR (timing matters)
After the first sale occurs, the issuer must file Form D with the SEC within 15 calendar days. A “sale” can occur when the investor is irrevocably committed (often at countersignature and acceptance of funds), not when tokens are delivered months later.
Form D requires basic information such as issuer identity, executive officers, size of offering, exemption relied upon, and types of investors. While Form D is a notice filing (not merit review), inaccuracies can create avoidable scrutiny and can complicate later financings.
7) Make state “blue sky” notice filings (even though 506 preempts registration)
Rule 506 offerings are “covered securities,” which generally preempt state registration requirements. However, many states still require notice filings (often a copy of Form D), consent
