Issuance & Redemption

BlackRock BUIDL Subscription

Tokenized money market fund — 3(c)(7) qualified purchaser, $5M minimum, 9 chains, Securitize as transfer agent.

Vendors

BlackRock · Securitize · BNY Mellon

Compliance center

3(c)(7) qualified purchaser at Identity + $5M minimum at Negotiation

issuancebuidlblackrocksecuritizetokenized-fundaccredited-investorwhitelist
Filter by shape:
|
I4 · ISSUANCEBlackRock BUIDL subscription·5 stations(3 compliance, 2 infra)·blackrock · securitize
S1INTENTS2S3DISCOVERYS4NEGOTIATIONS5TRANSPORTS6S7FACILITATIONS801Accreditation02Sanctions03NAV Check04Mint05Custody
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the BlackRock BUIDL subscription path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
5 stations across 5 of 8 segments. 3 are compliance checkpoints, 2 are infrastructure.
2 code-enforced3 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONINVESTOR GATE
L4 ACCOUNTINVESTOR GATE

Step 1 · Qualified Purchaser VerificationPolicy-EnforcedINGESTDETECTALERT

"The investor eligibility gate — Securitize verifies 3(c)(7) qualified purchaser status before proceeding."

Securitize (SEC-registered transfer agent) verifies that the prospective investor meets Investment Company Act § 3(c)(7) qualified purchaser criteria: $5M+ in investments, accredited investor status, or qualified institutional buyer (QIB) designation. KYC (D1) and licensing (D8) verified. This is the compliance heavyweight — the highest bar in the stablecoin universe. Policy-enforced at L4–L5.

Counterparty
Securitize (transfer agent) + BlackRock compliance team
Latency
Hours to days · manual compliance review
Finality
Investor approved or rejected
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONDocument & screening

Step 2 · Subscription Agreement & AMLPolicy-EnforcedINGESTDETECTALERT

"The subscription gateway — investor signs fund agreement and source-of-funds documentation passes AML/CFT screening."

Investor executes subscription agreement (SEC Form N-PX equivalent for digital fund) and provides source-of-funds evidence. Securitize and BlackRock conduct AML screening (D2) for sanctions, PEPs, and typologies. This is the document boundary — the bridge between traditional fund law and on-chain settlement. D1 (identity), D2 (sanctions reporting), and D8 (licensing) are active.

Counterparty
Securitize legal + BlackRock fund administrator (PwC)
Latency
Days · document assembly and screening
Finality
Subscription agreement accepted and AML cleared
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONNAV oracle

Step 3 · NAV Strike & AllocationPolicy-EnforcedINGESTDETECTALERT

"The NAV gate — fund administrator confirms daily NAV and allocates subscription at market price."

PwC (SEC-registered fund administrator) calculates daily NAV based on BUIDL holdings (short-term Treasuries, overnight repo, cash). Subscription amount is allocated at NAV. This is the prudential checkpoint — D9 (capital and valuation requirements) and D14 (consumer protection via fair pricing) fire. Policy-enforced at L3.

Counterparty
PwC (fund administrator) + BNY Mellon (custodian)
Latency
~1s · NAV published daily at 4pm ET
Finality
Allocation confirmed — mint authorized
Vendors
Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONMINT (WHITELIST)
L2 CONSENSUSMINT (WHITELIST)
◆ Enforcement Line — code-enforced at this layer

Step 4 · On-Chain Mint + WhitelistCode-Enforced

"The issuance boundary — BUIDL tokens are minted only to whitelisted addresses. The smart contract IS the transfer agent."

BUIDL tokens minted natively on settlement chain (Ethereum, Avalanche, Polygon, Arbitrum, Optimism, Aptos, or Solana). Smart contract enforces whitelist at mint time — only addresses pre-approved by Securitize receive tokens. This is the compliance heavyweight moment: transfer restrictions are code-enforced via ERC-3643 or equivalent compliance layer. L3 Execution (mint contract with whitelist oracle) and L2 Consensus are lit. The contract is the transfer agent — enforcement is code at the application boundary.

Counterparty
Securitize on-chain whitelist + BUIDL mint contract
Latency
~12s–2s · single block confirmation per chain
Finality
Mint finalized — BUIDL in whitelisted wallet
Vendors
Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET
◆ Enforcement Line — code-enforced at this layer

Step 5 · Investor Wallet (Whitelisted)Code-Enforced

"The investor's fund share balance — BUIDL tokens in whitelisted wallet, transfer-restricted by contract."

BUIDL tokens arrive in the investor's whitelisted wallet. Only addresses that have passed Securitize approval can hold or receive BUIDL — the transfer restriction is code-enforced in the smart contract. Investor can redeem daily at NAV via Circle atomic settlement (USDC, same-day finality). BNY Mellon custodizes the backing assets (Treasuries, repo, cash). Recordkeeping (D11) and tax reporting (D12) obligations apply. This is the most regulated path in the Issuance rail.

Counterparty
Investor's whitelisted address + Securitize oracle
Latency
Instant on mint confirmation
Finality
Final · BUIDL held and accruing yield daily
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

TOOL 01 · 4 PHASES × 5 LAYERS

Fund Lifecycle Stack

Interactive 5-layer stack across issuance, holding, redemption, and transfer — comparing Circle USYC, BlackRock BUIDL, and FOBXX.

Key question: Is the mint gated by an on-chain registry (code-enforced, L3) or by an off-chain API call to the transfer agent (policy-enforced, L4/L5)?

Circle USYCArc · $2B+BlackRock BUIDLEthereum · $2BFranklin Templeton FOBXXStellar · $700M+Generic ERC-20 WrapperAny EVM · VariesL5 APPLICATIONCircle PortalPOLICYD1 D8Securitize PortalPOLICYD1 D8Franklin Templeton P...POLICYD1 D8Any UIL4 MIDDLEWARECircle Compliance En...POLICYD1 D2Securitize Complianc...POLICYD1 D2FT Transfer AgentPOLICYD1 D2No Compliance LayerL3 EXECUTIONUSYC Mint ContractCODED8 D16BUIDL ERC-20 MintCODED8Stellar Asset ControlsCODED8 D16ERC-20 MintCODEL2 CONSENSUSMalachite BFTCODEEthereum PoSStellar Consensus (S...Any EVML1 NETWORKArc NetworkEthereum P2PStellar NetworkP2PGateMonitorObligationCode-enforcedPolicy-enforced

Circle USYC

Circle as issuer + fund administrator. USYC minted natively on Arc. Accredited investor check at L4 (Circle's compliance engine). NAV from Hashnote's calculation agent, published on-chain.

BlackRock BUIDL

Securitize as transfer agent. Minted on Ethereum. Accredited check at L5 (Securitize portal, fully off-chain). NAV from BlackRock, published via Securitize.

Franklin Templeton FOBXX

Franklin Templeton as both fund manager and transfer agent. Minted on Stellar. Authorization flags at L3 (Stellar's built-in asset controls). NAV from Franklin Templeton.

Generic ERC-20 Wrapper

No fund administrator. No compliance checks. Anyone can mint if they call the contract. No NAV enforcement whatsoever.

TOOL 02 · 4 ISSUERS COMPARED

NAV Enforcement Comparator

NAV calculation, publication, and enforcement comparison across 4 tokenized fund issuers with audit trail verification.

NAV QUESTION
Circle USYC
Arc
BlackRock BUIDL
Ethereum
Franklin Templeton FOBXX
Stellar
Generic ERC-20 Wrapper
Any EVM
NAV Calculator
Who calculates NAV?
L4POLICY
Hashnote (now Circle)
L5POLICY
BlackRock
L5POLICY
Franklin Templeton
Nobody
NAV Publication
Where is NAV published?
L3CODE
On-chain at L3 (Arc)
L4POLICY
On-chain via oracle at L4
L5POLICY
Off-chain at L5
Not published
On-chain Enforcement
Is NAV enforceable on-chain?
L3CODE
Yes — mint/redeem gated by NAV
L4POLICY
No — NAV is informational
L5POLICY
No — transfer agent controls
No — no NAV exists
NAV Failure Mode
What happens if NAV calculation fails?
L3CODE
Mint paused — oracle dependency
L4POLICY
Redemptions continue at stale NAV
L5POLICY
Fund admin discretion
No safeguard
Audit Trail
Who can verify NAV history?
L3CODE
Anyone — on-chain
L4POLICY
Securitize portal — whitelisted
L5POLICY
Fund administrator — on request
No audit trail
CODE-ENFORCED
POLICY-ENFORCED
ABSENT — THE GAP

The pattern: Circle USYC publishes NAV on-chain at L3 — the only fund where NAV enforcement is code-enforced. BlackRock BUIDL and Franklin Templeton FOBXX rely on off-chain fund administrators. The Generic ERC-20 wrapper column shows what institutional investors see when tokenization happens without compliance architecture: empty cells. The empty cells are the point.

Other Issuance & Redemption Paths

SETTLEMENT CHAINS