Subscription Agreement to On-Chain Mint: Eight Events, Four Regulations, One Snapshot

The scenario

The investor, for purposes of this scenario, is an institutional family office named in the offering documents. The fund is a Delaware-domiciled tokenized private fund. The fund's compliance stack uses Sumsub for identity verification, VerifyInvestor for accreditation review, Chainalysis for wallet screening, and DocuSign for the executed subscription agreement. The fund administrator forwards events into OMINEX as each upstream provider returns a result. The fund's tokenization platform reads the OMINEX attestation when it mints the on-chain interest.

Eight events, in sequence. Five upstream providers. One signed snapshot.

The eight events, rendered

The interactive panel below shows the same workflow that runs on the HowItWorks page. Each step references a real event id from the registry. Each step is independently expandable to show the regulations the event helps discharge.

What each event is doing

The investor opens the subscription portal in their browser. The fund's onboarding system presents the offering documents. OMINEX records the presentation event. This is the first compliance event the substrate captures, and it sounds trivial. It is not. SEC Rule 204-2 requires the firm to maintain a record of communications related to any advisory recommendation. The presentation event preserves the moment the offering documents were made available to a specific identified subject, with a timestamp the firm cannot retroactively modify. When the subscription is later challenged in a wind-down, by an LP advisory committee, or by counsel during a Reg D 506(c) examination, the firm proves the offering documents were presented at moment T, in the version with hash H, to subject X, without reconstructing anything.

The investor begins identity verification through the embedded Sumsub flow. Sumsub returns a verification result fifteen minutes later. The fund's onboarding system forwards the structured event to OMINEX. The event payload includes the Sumsub envelope reference, the verification methods used, the determinative result, and a timestamp at the moment the upstream provider's webhook arrived. OMINEX records the event, signs it, and binds it to the subject record. The same event satisfies BSA / FinCEN customer identification, PATRIOT Act §326, and the customer-side leg of Reg D 506(c) reasonable steps where the verification method also covers accredited status.

The investor proceeds to accreditation. The fund routes the income-verification request to VerifyInvestor. VerifyInvestor reviews two years of tax returns and an attorney letter. The attesting party is a CPA acting under their professional license. VerifyInvestor returns the verification result. The fund forwards the event. OMINEX records it as accreditation.income_verified and binds the verifying party's reference to the subject record. This event is the load-bearing one for the fund's reasonable-steps demonstration. SEC C&DI Question 260.36 establishes that third-party verification by a qualified party (CPA, attorney, broker-dealer, or RIA) is a non-exclusive safe harbor under Reg D 506(c). The OMINEX-recorded event preserves the verifying party's reference. If the exemption is later challenged, the issuer's reasonable-steps defense is the OMINEX snapshot showing the verification event. The defense does not require the issuer to produce internal records or rely on its own credibility.

OMINEX runs the OFAC SDN list screening against the subject's identity attributes. The result is recorded as screening.ofac_cleared. The same event is bound to the subject record with a timestamp and the OFAC list version that produced the clear result.

The investor submits a wallet address and signs a challenge message proving control. The fund's portal verifies the signature against the address. The structured event is forwarded to OMINEX as wallet.ownership_verified. A separate event, wallet.bound, records the formal binding of the address to the subject record. The subsequent Chainalysis wallet screening runs against the address. Chainalysis returns a clear sanctions result. The fund forwards wallet.sanctions_cleared. The OMINEX substrate now contains five events tied to the subject record: identity, accreditation, OFAC screening, wallet ownership verification, and wallet sanctions screening. Each event references the upstream provider's record and carries an OMINEX signature.

The investor signs the subscription agreement in DocuSign. DocuSign's webhook posts the envelope-completed event back to the fund. The fund forwards document.signed to OMINEX with the executed PDF's SHA-256 hash. The OMINEX substrate now binds the executed subscription agreement to the subject record by document hash, not by storing the document.

The fund accepts the subscription, records the capital commitment and terms, and releases the subscription event to the tokenization platform. OMINEX records fund.subscription_received. The tokenization platform reads the OMINEX attestation, confirms the subject record satisfies the fund's eligibility rules, and mints the on-chain interest.

Eight events. Five upstream providers. One signed snapshot.

What the snapshot does for the firm

The snapshot the fund auditor reads contains every event reference, every provider reference, the document hash, the wallet address, the issuance and expiry timestamps, the satisfies field listing the regulations the snapshot discharges (Reg D 506(c), Investment Adviser Rule 204-2, BSA / FinCEN, OFAC), the retention class anchored to the strictest applicable rule, and the OMINEX issuance signature. The snapshot is independently verifiable. The auditor verifies the snapshot through the OMINEX verification API. The auditor reads the satisfies field. The auditor pulls the bound events through the public verification API. The auditor does not ask the firm to produce a database export, reconstruct evidence, or vouch for internal controls.

The recordkeeping work is done. The reasonable-steps work is done. The CIP work is done. The OFAC work is done. The Adviser Rule 204-2 record is done. The fund's annual audit, the SEC examination of the adviser, the institutional allocator's diligence pack, and any later litigation request all draw from the same substrate. The firm exports snapshots for the relevant period. The work is retrieval, not reconstruction.

The next time the same investor subscribes to another OMINEX-integrated offering, the firm reads the existing snapshot rather than re-running the verification. The next time the SEC examiner shows up, the firm exports the snapshots covering the examination period rather than reconstructing them from internal databases.

Where the same pattern shows up elsewhere

The eight-event flow is the canonical tokenized fund subscription. The same architectural pattern, with different events from the same registry, runs through every other vertical surface on the marketing site. A broker-dealer's tokenized-trade workflow is six events ending in a per-trade snapshot. A custodian's pre-custody intake is six events ending in a custody confirmation snapshot. A stablecoin issuer's mint-and-reserve event sequence is six events ending in a reserve-attestation snapshot. The vocabulary is the same. The snapshot fields are the same. The retention classes follow the same rules. The examiner reads the same kind of record.

The marketing site renders this through the WorkflowFlow component. The product renders it through the verification API. The audit evidence renders it through the snapshot export. There is no abstraction layer between the three. The vocabulary is the same vocabulary, the substrate is the same substrate, and the firm using OMINEX speaks the same language to its customers, its providers, its auditors, and its examiners.

If the thing that resonates is the auditor reading the snapshot independently, you understand the product. If the thing that resonates is the recordkeeping multiplier, where one signed event satisfies multiple regulatory recordkeeping obligations, you understand the architecture. If both resonate, you are looking at what we built OMINEX to do.

Closing

The marketing site shows this flow in two surfaces. The HowItWorks page renders it as the eight-step WorkflowFlow component, which embeds an interactive snapshot panel. The vertical pages each render their own buyer-specific workflow using the same component and the same event vocabulary. The walkthrough you just read is the long-form editorial complement to the visual rendering. They are saying the same thing in different registers.

If you want to wire the same flow into your own product, sandbox evaluation routes through the structured intake at /enterprise/intake. Solutions engineering responds inside two business days.