Regulation D 506(b) for Token Offerings: Non-Solicitation Framework

Regulation D 506(b) predates its publicly marketed counterpart by decades — the original private placement exemption has been available since the adoption of Regulation D in 1982. Unlike 506(c), which permits general solicitation to verified accredited investors, 506(b) prohibits any form of public marketing but compensates with two advantages: no mandatory accredited investor verification (self-certification is sufficient) and permission to include up to 35 non-accredited but “sophisticated” investors per offering.

Core Requirements

No General Solicitation

The defining restriction of 506(b) is its prohibition on general solicitation and general advertising. The issuer may not publicly market the offering through websites, social media, press releases, industry conferences, or any channel that reaches persons with whom the issuer does not have a preexisting substantive relationship.

For security token issuers, this restriction fundamentally limits the utility of 506(b). Blockchain projects that depend on community awareness, network effects, and broad token distribution cannot effectively leverage 506(b)’s framework because they cannot publicly announce the offering’s existence. This explains why 506(c) dominates the security token market — accounting for 78% of all digital asset Form D filings versus 18% for 506(b) — despite its more rigorous verification requirements. The total Reg D market raised $2.15 trillion in 2024, with STO issuance growing from $5.6 billion to $6.66 billion between 2024 and 2025.

Preexisting Relationship Requirement

The SEC and courts have held that the issuer must have a preexisting “substantive relationship” with each offeree — meaning the issuer had sufficient information about the offeree’s financial situation and sophistication before the offering commenced. This requirement effectively limits 506(b) to issuers with established investor networks or those working with broker-dealers who have preexisting client relationships.

Non-Accredited Investor Allowance

506(b) permits up to 35 non-accredited investors per offering, provided each non-accredited investor is “sophisticated” — meaning they have, either alone or with a purchaser representative, sufficient knowledge and experience in financial and business matters to evaluate the merits and risks of the investment.

When non-accredited investors participate, the issuer must provide them with information substantially equivalent to what would be included in a registration statement — a significant disclosure burden that most token issuers prefer to avoid by restricting sales to accredited investors.

Self-Certification

Unlike 506(c), which requires affirmative verification of accredited investor status, 506(b) allows issuers to rely on investor self-certification. A purchaser questionnaire in which the investor represents their accredited status is generally sufficient, provided the issuer has no reason to believe the representation is false.

This reduced verification burden lowers compliance costs by approximately $50-$100 per investor compared to 506(c). For offerings with hundreds of investors, this savings can be material — though it comes at the cost of general solicitation prohibition.

Use Cases for Token Issuers

Despite 506(c)’s dominance, 506(b) retains utility in specific scenarios:

Institutional capital raises. When a token issuer is raising capital from a known group of institutional investors — venture funds, family offices, strategic partners — the preexisting relationship requirement is naturally satisfied, and the general solicitation prohibition is not a meaningful constraint.

Bridge financings. Security token projects that need interim funding from existing investors or close associates can use 506(b) to execute quickly without the verification overhead of 506(c).

Conversion offerings. When traditional securities holders are being offered the opportunity to convert existing holdings to tokenized format, the preexisting relationship with the issuer satisfies 506(b)’s requirements.

Integration with Other Exemptions

Token issuers conducting 506(b) offerings must be careful about integration with concurrent offerings under other exemptions. A simultaneous 506(b) offering (no solicitation permitted) and a 506(c) offering (solicitation permitted) for the same security could jeopardize the 506(b) exemption if the 506(c) marketing is deemed to constitute solicitation for the 506(b) offering.

Rule 152 provides safe harbors for concurrent offerings, but the analysis is fact-specific and requires careful coordination between the offerings. Most practitioners advise sequential rather than concurrent offerings when mixing 506(b) and 506(c).

For a comprehensive comparison of offering exemptions, see our analysis of Reg D vs. Reg A+ and our offering timeline checklist. For platform-specific guidance, review our entity profiles of Securitize and tZERO.

Disclosure Requirements for Non-Accredited Investors

When non-accredited investors participate in a 506(b) offering, the disclosure burden increases substantially. The issuer must provide:

Financial statements. For offerings up to $2 million, the issuer’s balance sheet (within 120 days of the start of the offering) and statements of income, cash flows, and retained earnings for the two most recent fiscal years — reviewed by an independent accountant. For offerings between $2-$7.5 million, audited financial statements. For offerings exceeding $7.5 million, audited financial statements prepared in accordance with U.S. GAAP.

Non-financial information. Substantially the same information that would be included in a registration statement on Form S-1 — business description, risk factors, management biographies, use of proceeds, and capitalization table. For security tokens, this includes detailed disclosure of smart contract architecture, transfer agent arrangements, custody framework, and planned secondary market listing.

This disclosure burden is why most 506(b) token offerings restrict sales to accredited investors only — the cost of preparing non-accredited investor disclosure ($50,000-$100,000) often exceeds the benefit of including a few non-accredited but sophisticated investors.

Smart Contract Considerations for 506(b)

Security tokens issued under 506(b) face the same smart contract compliance requirements as 506(c) tokens:

• Rule 144 holding period enforcement — the smart contract must prevent resale until the applicable holding period expires (6 months for reporting issuers, 12 months for non-reporting issuers).
• Accredited investor whitelist — secondary market buyers must be verified accredited investors. The smart contract checks the transfer agent’s whitelist before processing any transfer.
• Volume limitations — for affiliate resales under Rule 144, the smart contract should enforce the 1% or average weekly volume limitations.

Interoperability standards like ERC-1400 and ERC-3643 support these compliance features natively, enabling automated enforcement of securities law requirements on-chain.

Form D Filing

506(b) offerings require the same Form D filing as 506(c) — within 15 calendar days of the first sale, on SEC EDGAR. The Form D identifies the exemption claimed (506(b), not 506(c)), the number of accredited and non-accredited investors, and basic offering information.

State blue sky notice filings are also required in each state where investors reside, though federal preemption prevents states from imposing substantive registration requirements.

506(b) vs. 506(c) Decision Matrix

For most security token offerings, 506(c) is the stronger choice because blockchain projects require public visibility to build community and network effects. 506(b) is reserved for situations where the investor base is pre-identified and general solicitation adds no value.

The cost advantage of 506(b) — lower verification costs ($0-$10 per investor vs. $50-$150 for 506(c) documentary verification) — is offset by the requirement to maintain preexisting substantive relationships with all investors and the prohibition on any form of public marketing. For token issuers with established investor networks, 506(b) can save $50,000-$200,000 in verification and marketing costs. For issuers building new investor bases, 506(c)’s general solicitation permission is essential despite the higher per-investor verification cost.

506(b) in Practice: Token Offering Use Cases

Despite 506(c)’s dominance in the security token market, 506(b) remains appropriate for specific scenarios:

Institutional co-investment. When a small group of institutional investors (family offices, venture funds, hedge funds) co-invest in a tokenized asset, 506(b) avoids the verification paperwork while relying on preexisting relationships. These investors are typically already known to the issuer and can be verified through substantive relationship documentation.

Private fund tokenization. Existing private funds converting to tokenized structures often use 506(b) because their investor base is already established through preexisting relationships. Converting a traditional limited partnership to a tokenized fund interest does not require general solicitation if the investor base remains unchanged.

Dual offering strategy. Some issuers conduct a 506(b) offering to a known investor base while simultaneously preparing a 506(c) offering for broader distribution. The integration doctrine analysis must confirm these are treated as separate offerings under Rule 152 safe harbors.

506(b) and the Preexisting Relationship Standard

The preexisting substantive relationship requirement is the most litigated and fact-specific element of 506(b) compliance. SEC enforcement actions and no-action letters have established several principles:

Timing requirement. The relationship must predate the offering. An investor who learns about the issuer through general advertising and then establishes a relationship before subscribing does not satisfy the preexisting relationship standard. The SEC has held that relationships formed as part of the offering process — even if they involve substantive financial discussions — do not qualify.

Substantive knowledge. The issuer (or its broker-dealer agent) must have sufficient information about the investor’s financial circumstances, investment experience, and investment objectives to evaluate whether the offering is suitable. A social or personal relationship, without financial knowledge, is insufficient. This is why broker-dealer intermediation is common in 506(b) offerings — the broker-dealer’s existing client relationships automatically satisfy the preexisting relationship requirement.

Investor database approaches. Some token platforms maintain investor databases where potential investors register and provide financial information before any specific offering is available. The SEC has indicated that these databases can establish preexisting relationships if: (1) the investor provides substantive financial information at registration, (2) a reasonable period elapses between registration and the offering announcement, and (3) the platform evaluates the information before including the investor in offering communications.

Legal Risk Analysis for 506(b) Token Offerings

The consequences of a 506(b) violation are more severe than for 506(c) because the violation typically involves general solicitation — which taints the entire offering, not just a single investor transaction. If an issuer conducts what it believes is a 506(b) offering but inadvertently engages in general solicitation (through a social media post, a blog article, or a conference presentation that discusses the offering), the entire exemption is lost. All securities sold under the invalidated exemption become unregistered securities, giving every investor a rescission right under Section 12(a)(1) of the Securities Act.

This binary risk profile — where a single marketing mistake can invalidate the entire offering — is a primary reason that sophisticated token issuers prefer 506(c) despite its higher verification costs. The enforcement consequences of a Section 5 violation extend beyond rescission to include potential SEC enforcement action, bad actor disqualification for future offerings, and state-level penalties under blue sky laws.

506(b) in the Current Regulatory Environment

The SEC’s evolving digital asset policy under Chairman Atkins — including the Crypto Task Force’s six roundtables through Q1 2026 and the March 2026 SEC-CFTC joint token taxonomy guidance — has not altered the fundamental 506(b) framework, but the Task Force’s emphasis on classification clarity may benefit 506(b) issuers by reducing uncertainty about which tokens require securities compliance. The SEC brought 125 cryptocurrency-related enforcement actions between 2021 and 2024 generating $6.05 billion in penalties according to Cornerstone Research, with enforcement pace declining 60% to 13 actions in 2025. For 506(b) token issuers, the risk profile remains binary: a single instance of general solicitation invalidates the entire exemption. The December 11, 2025 SEC no-action letter allowing the DTC to operate tokenization services on permissionless blockchains could eventually integrate 506(b) security tokens into traditional settlement infrastructure, potentially expanding the institutional appetite for privately placed digital securities. Meanwhile, ATS platforms like tZERO (near-24/7 trading since December 2025), Securitize Markets ($4 billion+ tokenized AUM), and INX continue to build secondary market infrastructure that 506(b) tokens can access after Rule 144 holding periods expire.

The Howey test applies regardless of which exemption is used — 506(b) provides an exemption from registration, not from securities classification. Token issuers should complete their securities classification analysis before selecting an offering exemption. For broker-dealer obligations specific to 506(b) offerings, see our guide. For the Reg D vs. Reg A+ comparison, see our analysis. For ATS platform listing after the holding period, see our platform comparison. For enforcement actions involving Reg D violations, see our tracker. For the SEC’s Reg D overview, see SEC Regulation D.