Rule 506(c) Requirement

Platform Satisfaction

General solicitation permitted

OTCM Protocol's Predictive Marketing AI Module (Layer 9) conducts general solicitation within Rule 506(c) parameters

All purchasers are accredited investors. Verification methods include: (1) income verification through IRS forms, (2) net worth verification through asset statements, (3) written confirmation from registered broker-dealer, investment adviser, licensed attorney, or CPA.investors

Unlike Rule 506(b) offerings where issuer may rely on investor representations, Rule 506(c) requires affirmative verification through documented methods, justifying general solicitation privileges.

🔹 9.3.2 Accredited Investor Categories

🔹11.3.2 9.3.3 Third-PartyFee VerificationStructure Pathway— Regulation D Offering Phase

TheOTCM preferredProtocol verificationcharges pathwaya involves5% third-partyplatform professionalfee confirmationon fromthe qualifiedgross professionals:

//purchase, Third-Partybefore Verificationproceeds Interface

interfaceremitted ThirdPartyAccreditationVerificationto {the issuer. This fee structure applies across the entire lifecycle of ST22 transactions, including both the primary offering phase and all subsequent secondary market trading on CEDEX.

/** 

• Verification pathway utilizing third-party professionals
• as permitted under 17 CFR 230.506(c)

*/

pathway: 'THIRD_PARTY';

// Verifier information

verifier: {

type: 'RIA' | 'CPA' | 'ATTORNEY' | 'BROKER_DEALER';

name: string;

licenseNumber: string;

licensingAuthority: string; // e.g., 'SEC', 'State Bar of California'

firmName: string;

firmAddress: string;

contactPhone: string;

contactEmail: string;

};

// Attestation details

attestation: {

date: Date;

accreditationMethod: 'INCOME' | 'NET_WORTH' | 'PROFESSIONAL' | 'ENTITY';

verificationPeriod: { // Time period reviewed

start: Date;

end: Date;

};

documentsReviewed: string[]; // e.g., ['Tax Return 2023', 'Tax Return 2024']

attestationStatement: string;

};

// Document evidence

attestationLetter: {

documentHash: string; // SHA-256 hash

uploadTimestamp: Date;

fileSize: number;

mimeType: 'application/pdf';

};

// Verification status

status: 'PENDING' | 'VERIFIED' | 'REJECTED';

expirationDate: Date; // Typically 90 days from verification

// On-chain record

onChainRecord: {

transactionSignature: string;

blockHeight: number;

recordTimestamp: Date;

};

}

Acceptable third-party verifiers include:

• Registered Investment Advisers (RIAs): SEC or state-registered investment advisers with fiduciary duty
• Certified Public Accountants (CPAs): Licensed accounting professionals in good standing
• Securities Attorneys: Attorneys in good standing specializing in securities law
• FINRA-Registered Broker-Dealers: Broker-dealer firms registered with FINRA

🔹 9.3.4 Self-Certification Pathway

For investors unable to obtain third-party verification, the Portal enables self-certification subject to enhanced review and audit procedures:

// Self-Certification Interface

interface SelfCertificationAccreditation {

/**

• Self-certification pathway with enhanced scrutiny
• Subject to audit review confirming consistency

*/

pathway: 'SELF_CERTIFICATION';

// Certification details

certification: {

date: Date;

method: 'INCOME' | 'NET_WORTH' | 'PROFESSIONAL';

selfDeclaredValues: {

// For income method

annualIncome?: {

year1: number;

year2: number;

expectedCurrent: number;

};

// For net worth method

netWorth?: {

totalAssets: number;

totalLiabilities: number;

primaryResidenceValue: number; // Excluded

netWorthExcludingResidence: number;

};

};

};

// Required supporting documents

supportingDocuments: {

required: [

'BANK_STATEMENTS_3_MONTHS',

'BROKERAGE_STATEMENTS_3_MONTHS',

];

optional: [

'TAX_RETURNS_2_YEARS', // Strongly recommended

'PROPERTY_VALUATIONS', // If net worth claim

'BUSINESS_FINANCIALS', // If business income

];

uploadedDocuments: {

documentType: string;

documentHash: string;

uploadTimestamp: Date;

}[];

};

// Consistency validation (ML-powered)

consistencyAnalysis: {

liquidAssetsDetected: number; // From bank/brokerage statements

incomePatternDetected: number; // From deposit patterns

consistentWithClaim: boolean;

confidenceScore: number; // 0-100

flags: string[]; // Any inconsistencies

};

// Audit risk assessment

auditRisk: {

priority: 'LOW' | 'MEDIUM' | 'HIGH';

factors: string[];

nextAuditDate?: Date;

};

// Legal acknowledgments

acknowledgments: {

perjuryWarning: boolean; // 'I understand false statements may result in...'

rescissionRisk: boolean; // 'I understand investment may be rescinded if...'

auditConsent: boolean; // 'I consent to audit of accreditation status...'

signatureTimestamp: Date;

signatureHash: string;

};

}

⚠️ Audit Risk

Self-certified investors are subject to random audit review. Inconsistencies between self-certified status and demonstrated liquid assets trigger manual compliance review and potential investment rescission. False certification constitutes securities fraud.

🔹 9.3.5 Non-Accredited Investor Pathways

For investors unable to satisfy accreditation requirements, the Portal enables participation through Regulation A+ Tier 2 offerings:

📋 15 U.S.C. Section 77b(b) and 17 CFR Section 230.251

Regulation A+ Tier 2 permits offerings up to $75,000,000 annually to both accredited and non-accredited investors, subject to investment limits for non-accredited investors.

🔹 9.3.6 Accreditation Expiration & Renewal

Accreditation status is not permanent and requires periodic renewal:

• Standard Expiration: 90 days from date of third-party verification
• Self-Certification: 90 days, subject to earlier audit-triggered review
• Professional Certification: Valid while license remains in good standing (verified monthly via FINRA BrokerCheck)
• Renewal Process: Same verification requirements as initial accreditation; prior accreditation does not expedite process

🔍 9.4 Automated AML Screening

The OTCM Portal integrates with blockchain analytics providers to implement comprehensive anti-money laundering screening, analyzing 200+ transaction features to identify suspicious activity patterns and ensure compliance with Bank Secrecy Act requirements.

🔹 9.4.1 200+ Feature Risk Analysis

The AML screening system analyzes over 200 distinct features across six primary categories:

// AML Risk Scoring Model

// Composite risk score (0-100)

// Category-level scores

// Risk classification

// Specific flags triggered

// Recommended action

// Risk Tier Thresholds

TheEmpire Portal implements real-time monitoring of all investor transactions post-issuance:

// Transaction Monitoring Configuration

interface TransactionMonitoringConfig {

// Real-time triggers (per-transaction)

realTimeRules: {

// Large transaction alert

largeTransactionThreshold: number; // $10,000 USD equivalent

// Rapid succession detection

rapidSuccession: {

transactionCount: number; // 3+ transactions

timeWindowMinutes: number; // within 10 minutes

};

// Structuring detection

structuringDetection: {

targetThreshold: number; // $10,000 (CTR threshold)

toleranceRange: { min: number; max: number }; // $9,000 - $9,999

transactionCount: number; // 2+ transactions in range

timeWindowHours: number; // within 24 hours

};

// Round number detection

roundNumberAlert: {

enabled: boolean;

threshold: number; // e.g., $5,000+

consecutiveCount: number; // 3+ round amounts

};

};

// Batch analysis (daily)

batchRules: {

velocityAnalysis: boolean; // Transaction frequency vs baseline

peerGroupComparison: boolean; // Deviation from similar investors

geographicAnomalies: boolean; // Unusual IP/location patterns

networkAnalysis: boolean; // New connections to flagged wallets

behaviorProfiling: boolean; // Deviation from established pattern

};

}

🔹 9.4.4 Suspicious Activity Detection

The system identifies suspicious activity patterns that may indicate money laundering, fraud, or sanctions evasion:

• Structuring: Breaking transactions into smaller amounts to avoid reporting thresholds
• Layering: Rapid movement of funds through multiple addresses to obscure origin
• Velocity Anomalies: Sudden increase in transaction frequency or volume
• Geographic Inconsistencies: Transactions from unusual locations or VPN usage
• Coordinated Activity: Multiple accounts acting in concert
• Criminal Exposure: Transactions with addresses associated with known criminal activity

🔹 9.4.5 SAR Filing Automation

When suspicious activity is detected, the Portal automates Suspicious Activity Report filing with FinCEN:

📋 31 CFR § 1010.320 — SAR Filing Requirements

Financial institutions must file SARs for transactions involving $5,000 or more if the institution knows, suspects, or has reason to suspect the transaction involves funds derived from illegal activity, is designed to evade reporting requirements, or has no lawful purpose.

// SAR Filing Automation

async function evaluateSARRequirement(

investor: Investor,

suspiciousActivity: SuspiciousActivityDetection

): Promise<SARFilingResult> {

// Evaluate SAR filing criteria

const sarCriteria = {

amountThreshold: suspiciousActivity.totalAmount >= 5000,

suspiciousPattern: suspiciousActivity.patternConfidence >= 70,

criminalExposure: suspiciousActivity.criminalExposure > 0,

structuringDetected: suspiciousActivity.structuringScore >= 50,

sanctionsRisk: suspiciousActivity.sanctionsRisk > 0,

};

const requiresSAR = Object.values(sarCriteria).some(c => c === true);

if (requiresSAR) {

// Build SAR report

const sarReport: SARReport = {

filingInstitution: {

name: 'OTCM Protocol, Inc.',

ein: 'XX-XXXXXXX',

address: '...',

},

subjectInformation: {

name: investor.legalName,

address: investor.residentialAddress,

identificationNumber: investor.kycDocumentNumber,

walletAddresses: investor.associatedWallets,

},

suspiciousActivity: {

dateRange: suspiciousActivity.dateRange,

totalAmount: suspiciousActivity.totalAmount,

activityType: suspiciousActivity.activityTypes,

narrative: generateSARNarrative(suspiciousActivity),

},

transactionDetails: suspiciousActivity.transactions,

};

// Submit to FinCEN BSA E-Filing

const filingResult = await fincenAPI.submitSAR(sarReport);

// Record SAR filing on-chain (hash only, not content)

await recordSARFiling(investor.walletAddress, {

filingDate: Date.now(),

bsaId: filingResult.bsaId,

reportHash: hash(sarReport),

// Note: SAR content is confidential and not stored on-chain

});

return {

filed: true,

bsaId: filingResult.bsaId,

filingDate: new Date(),

};

}

return { filed: false, reason: 'SAR criteria not met' };

}

🔹 9.4.6 Account Freezing Procedures

When high-risk activity is detected, accounts may be frozen pending investigation:

🌍 9.5 Global Investor Eligibility

The OTCM Portal accommodates global investor participation while implementing jurisdiction-based restrictions to ensure compliance with US sanctions laws and international AML standards.

🔹 9.5.1 Regulation S Framework

The Portal enablesverifies non-USU.S. nationalperson investor participation through the Regulation S framework:

📋 17 CFR Section 230.903 — Regulation S Offshore Transactions

Permits securities offerings to foreign persons in offshore transactions without SEC registration, provided (1)status; no directed selling efforts ininto theU.S. United States, (2) the issuer reasonably believes all offerees are outside the United States, and (3) appropriate offering restrictions are implemented.markets

interface RegulationSCompliance {

// Offshore transaction requirements

offeringLocation: 'OFFSHORE'; // Must be outside United States

buyerLocation: string; // Non-US jurisdiction

sellerLocation: string; // Any jurisdiction

// No directed selling efforts

directedSellingEfforts:No {conditioning of the U.S. market for the securities

usMediaAdvertising:

usDirectedWebsite:AI false;Module //(Layer No9) enforces Rule 506(c) targeting for U.S. wallets; Reg S outreach targets non-U.S. wallets only

Non-U.S. person certification

Investor certifies non-U.S. person status under Rule 902(k)

Empire Stock Transfer KYC includes IP geolocation and document verification of US IPsresidency

usRoadshows:

usBrokerEngagement: false; // No US broker solicitation

};

// Buyer certification requirements

buyerCertification: {

nonUSPersonCertification: boolean; // Required

residencyVerification: {

method: 'DOCUMENT' | 'IP_GEOLOCATION' | 'BOTH';

verificationDate: Date;

documentType?: string;

ipCountry?: string;

};

};

// Distribution compliance (Category 3 - Equity)

distributionCompliance: {

restrictionPeriod: 40; // 40-day12-month distribution compliance period

flowbackRestriction:Non-U.S. boolean;investors //may not offer or sell to U.S. persons for 12 months

Transfer Hook Control 24 enforces 12-month lock on Reg S investor wallets — Error 6024 on premature transfer

Restrictive legend

Securities must bear restrictive legend during compliance period

ST22 token metadata includes Reg S restriction flag readable by CEDEX matching engine

Flowback restriction

Prevents immediate USresale resaleinto U.S. markets

Transfer Hook Control 18 screens Reg S transfers against U.S.-person buyer wallets during compliance period