← Glossary

Arc Network

Circle institutional Layer-1 for stablecoin finance, featuring deterministic finality. It uses USDC as native gas and supports atomic PvP settlement to eliminate Herstatt risk in global FX operations.

Definition

Circle's Malachite Consensus and Deterministic Finality

Settlement infrastructure comparison — Arc vs Ethereum PoS vs permissioned DLT

Attribute Arc Network Ethereum PoS Permissioned DLT
Finality model Deterministic · <1s benchmark Probabilistic → Economic ~14min Deterministic · varies by impl.
Gas token USDC · ~$0.01/tx target ETH · volatile market price None · permissioned access
Benchmark throughput ~3,000 TPS · 20 validators ~15–45 TPS Varies by implementation
Validator model Permissioned set · approved institutions Proof-of-Stake · anonymous Known consortium
Basel capital alignment Supports criteria for potential Group 1 path Group 2 · 1,250% risk weight Off-chain — not classified
Privacy model Opt-in planned · selective disclosure Fully transparent Configurable by operator
Cross-chain interop CCTP + Gateway · native Circle Third-party bridges Limited · bespoke
EVM compatibility Yes · Prague hard fork Yes · native Varies

Arc's primary architectural distinction is deterministic BFT finality. On proof-of-work and many proof-of-stake networks, a transaction passes through a probabilistic state — it has been broadcast and included in a block, but it could theoretically be reversed by a chain reorganization if a longer competing chain emerges. Ethereum's proof-of-stake achieves economic finality through the Casper FFG mechanism in approximately 14 minutes, but finalized blocks carry residual reversal risk through socially-coordinated hard forks. For institutional settlement operations, this probabilistic model creates a fundamental problem: a system of record cannot mark a trade as settled against a position that might be reversed.

Arc's Malachite consensus resolves this by implementing Tendermint BFT with a permissioned validator set. The Tendermint protocol uses a two-phase voting process: validators first broadcast pre-votes indicating a block is valid, then broadcast pre-commits. When more than two-thirds of the validator set pre-commits to the same block, that block is committed and final — the two-thirds threshold ensures that two conflicting blocks cannot both be finalized, making reorganizations impossible. Benchmark testing shows the process completing in under 350 milliseconds with 20 geographically distributed validators. The binary nature of the result — a transaction is either unconfirmed or final, with no intermediate state — is the design property that makes Arc suitable for systems of record. For downstream operational systems, the block commitment is the trigger: IBOR cash positions can be updated, accounting entries booked, and Rule 17a-3 settlement records written the moment the block is committed, without waiting for confirmation depth. For a comparative treatment of blockchain finality models, see Settlement Finality (DLT/Blockchain). For the T+0 architecture context, see T+0 Settlement Operations.

USDC as Native Gas and Predictable Fee Architecture

Arc uses USDC as the native gas token. On most blockchains, transaction fees are paid in a volatile speculative asset, creating an accounting asymmetry: the settlement instrument is a stable dollar-denominated asset, but the operational cost to settle it fluctuates with token market prices. Arc removes this asymmetry. The fee formula is: fee = gas units × base_fee_in_USDC. Market-driven price volatility is eliminated as a cost variable. The protocol's fee smoothing mechanism uses an exponentially-weighted moving average (EWMA) of block utilization to adjust the base fee gradually, dampening the fee spikes that institutional treasury desks encounter on general-purpose blockchains during network congestion. The target transaction cost is approximately $0.01. For institutional operations, gas fees become predictable USD-denominated line items — no volatile token position is required to fund settlement activity, and the unit of account for value transfer and settlement cost is identical. An additional capability enabled by the Prague hard fork is EIP-7702, which allows a USDC wallet address to temporarily operate as a smart contract. This enables Gas Station functionality — an institution or application can absorb transaction fees on behalf of other participants programmatically, without requiring each counterparty to maintain a gas reserve. Arc also supports paymaster integration, allowing other stablecoins to be used for fee payment, which broadens the model beyond USD-denominated workflows.

Programmable Compliance: Opt-In Privacy and Selective Disclosure (Planned)

Privacy features on Arc — confidential transfers and view keys — are on the development roadmap and represent a planned architecture, not a currently deployed capability. When implemented, the model establishes what the Arc Litepaper describes as programmable compliance: the ability to configure transaction confidentiality and audit access programmatically, rather than relying on either full public transparency or full anonymity. Confidential transfers shield transaction amounts from the public ledger while keeping sender and receiver addresses visible, ensuring compatibility with blockchain analytics tools and AML monitoring. View keys allow an institution to issue a cryptographic key granting a specific third party — an auditor, regulator, or compliance officer — scoped read-only access to encrypted transaction data. Selective disclosure means the institution controls which transactions each authorized party can see, rather than providing blanket ledger access. This satisfies the core compliance tension: transaction details are protected from public visibility, regulatory examination access is preserved programmatically, and the institution retains full visibility into its own customer activity for Travel Rule and transaction monitoring purposes. The cryptographic backend is planned to begin with Trusted Execution Environments (TEEs), with a modular design supporting future integration of Multi-Party Computation, Fully Homomorphic Encryption, and zero-knowledge proofs.

Atomic PvP FX Settlement and the Elimination of Herstatt Risk

Arc's FX settlement mechanism combines off-chain Request-for-Quote execution with atomic on-chain settlement through a smart contract escrow. When two counterparties agree to exchange USDC for EURC, both legs of the swap are locked into the escrow contract before either is released. The contract releases both legs simultaneously in a single atomic transaction. If either leg is absent when the configurable settlement window closes, the contract returns the encumbered balance to the originating wallet — no capital is trapped, and no manual dispute process is required. This programmable clawback is a key operational risk control with no direct equivalent in traditional FX settlement. The payment-versus-payment (PvP) structure eliminates Herstatt risk — the exposure created when one party delivers its leg of an FX swap before confirming receipt of the other. In correspondent banking, this exposure window is managed through coordination systems that operate within business-day schedules. On Arc, the PvP guarantee is enforced by the smart contract and the deterministic finality of the block containing it, and the settlement operates on a continuous 24/7 basis. Arc's crosschain liquidity architecture — CCTP for cross-chain USDC transfer and Gateway for chain-abstracted balances — addresses liquidity fragmentation by allowing USDC to flow from Arc to any connected blockchain without manual rebalancing, using sub-second CCTP transfers enabled by Arc's deterministic finality.

How it works

  1. USDC wallet provisioning and SSI registration. The broker-dealer or asset manager establishes a custody wallet on Arc, provisioned with USDC as both the settlement asset and the gas reserve. The wallet address is registered as a standing settlement instruction (SSI) in Devancore, mapped to the legal entity, account structure, and counterparty record. The USDC contract address on Arc — a protocol-reserved vanity address at 0x3600000000000000000000000000000000000000, and the applicable CCTP domain (domain 26) — are stored as enrichment reference data. The wallet is designated as the Arc settlement rail in the routing logic alongside the firm's Fedwire ABA routing number and CHIPS UID.

  2. Programmable compliance screening at enrichment. Before any on-chain instruction is generated, the counterparty's settlement wallet address is screened against OFAC's Specially Designated Nationals list using a compliance integration — Arc's ecosystem includes Elliptic and TRM Labs as integrated providers of blockchain analytics, wallet screening, and real-time transaction monitoring. The screening result is recorded in the trade record under Rule 17a-3. No instruction is generated for an unscreened or flagged wallet address. For StableFX trades, both the counterparty wallet and the escrow contract address are validated. Because on-chain transactions on Arc are irreversible once a block is committed, pre-transfer screening operates as an absolute hard gate.

  3. Smart contract trade registration and escrow funding. For DvP securities settlement or StableFX currency swaps, the trade is registered in the relevant Arc smart contract. The USDC cash leg is encumbered in the contract escrow. For StableFX, the counterparty's EURC or other stablecoin leg must be funded before the configured settlement window closes. If either leg is absent at window expiry, both are returned to the originating wallets — the programmable timeout eliminates the risk of capital remaining locked in an underfunded escrow.

  4. Malachite BFT finality — the two-phase voting process. The transaction is broadcast to the Arc validator set. Validators execute the Tendermint two-phase voting process: pre-vote (validators confirm the block is valid) and pre-commit (validators confirm their commitment to the block). When more than two-thirds of the validator set pre-commits, the block is committed and all transactions within it are final and irreversible. Under benchmark conditions, the process completes in under 350 milliseconds. No confirmation depth counter is required — block commitment is the terminal settlement event.

  5. Finality event listener — the IBOR and regulatory record update. Devancore operates as the finality event listener for Arc-settled trades: at the moment a block is committed, the finality event is consumed and downstream updates execute without a confirmation depth threshold. The AccountPosition settlementStatus transitions from PENDING to CONFIRMED, the settlement record is written to the Rule 17a-3 trade log with block number, transaction hash, and finalization timestamp, and the net capital computation is updated to reflect the settled position. Because Arc's finality is binary, Devancore's Arc integration requires no rollback logic, no retry mechanism, and no confirmation-depth configuration. This is the Unified Atomic Ledger model: the blockchain settlement event and the system-of-record update are the same event.

  6. StableFX atomic PvP execution and USYC settlement distinctions. For currency conversion trades — USDC to EURC — the FxEscrow contract executes the swap atomically in a single block. Both legs are released simultaneously when both are present, or both are returned when either is absent. The IBOR records both the outgoing USDC debit and the incoming EURC credit as a single settlement event at the agreed RFQ exchange rate. For USYC settlements, accrued interest is computed between trade date and settlement date — analogous to accrued interest in bond settlement — and recorded separately from the principal transfer. Gas fees for each settlement transaction are captured as a USD-denominated operating expense at the ~$0.01 target rate, distinct from the settlement debit.

  7. Cross-chain liquidity via CCTP and Gateway. For firms maintaining USDC positions across multiple blockchain networks, Circle Gateway provides chain-abstracted balances aggregating Arc holdings with positions on other supported chains. Devancore's dual-rail cash position aggregates the Arc on-chain balance, any CCTP cross-chain transfer in progress, and fiat positions on Fedwire and CHIPS into a unified USD cash record for the Rule 15c3-3 reserve formula and the daily net capital computation. CCTP domain 26 identifies Arc-originated transfers in the cross-chain transfer record. CCTP transfer status — whether a transfer has been burned on Arc and minted on the destination chain — is a distinct break type in the cash reconciliation workflow with no equivalent in traditional fiat settlement. For the dual-rail architecture, see Cash Reconciliation Software.

In Devancore™

Arc as the Native Settlement Rail and the Unified Atomic Ledger

Devancore's data model treats Arc as a first-class settlement rail alongside Fedwire and CHIPS. The InstrumentOnChain model registers Arc-native assets — USDC, EURC, USYC — with their respective contract addresses, the Arc chain identifier, and decimal precision. The PlaceOfSettlement record for an Arc-settled trade carries BLOCKCHAIN as the settlement rail type and ARC as the network identifier. Core position, P&L attribution, and net capital computations operate identically for Arc-settled positions as for traditionally settled ones — no parallel accounting stack is required. This unified architecture — one ledger recording blockchain and fiat settlement events with the same primitives — is the Unified Atomic Ledger model that underpins Devancore's hybrid settlement thesis.

Finality Event Listener — IBOR Update at Block Commit

Devancore acts as the finality event listener for Arc: rather than polling for confirmation depth, the integration consumes Arc block finality events directly. The moment a block is committed by the Malachite validator set, Devancore triggers a deterministic sequence — the AccountPosition settlementStatus transitions from PENDING to CONFIRMED, block number, transaction hash, and finalization timestamp are written to the Rule 17a-3 record, and the net capital computation is updated in the same operation. No confirmation counter is maintained, no retry logic is required, and no rollback mechanism is needed. For institutional operations teams, this means Arc settlement latency does not add a post-settlement reconciliation step: the blockchain event and the system-of-record update are the same event.

USDC Gas Fee Tracking as USD Operating Expense

Gas fees on Arc are denominated in USDC at approximately $0.01 per transaction — a fixed USD operating expense rather than a mark-to-market position. Devancore captures the gas cost of each settlement transaction as a separate line in the transaction record, not as a settlement debit. Because the gas token is USDC rather than a volatile asset, no fair-value adjustment is required on the gas reserve balance. The gas reserve wallet balance is monitored as part of the daily prefunding check: if the USDC balance in the settlement wallet falls below the threshold required to fund pending settlement activity plus estimated gas costs, Ops Copilot surfaces a prefunding exception before settlement instructions are generated.

StableFX PvP Settlement and USYC Accrued Interest

For cross-currency settlement on Arc, Devancore generates StableFX registrations against the FxEscrow smart contract. The trade record captures both legs of the swap — USDC outflow and EURC inflow — as a single settlement event with the agreed exchange rate, settlement window, and counterparty wallet. On block finality, both legs update in the IBOR simultaneously. The configured settlement window timeout is recorded in the trade record: if the window expires with one leg absent, the return of the encumbered USDC is captured as a settlement reversal with the timeout timestamp. For USYC settlements, the AccountPosition record includes an accrued interest field computed from trade date to settlement date — the yield-bearing nature of USYC requires the same accrual treatment applied to short-duration bond settlement, distinct from pure stablecoin parity settlement.

Programmable Compliance Integration (Elliptic and TRM Labs)

Devancore's enrichment workflow integrates with Arc's compliance vendor ecosystem for wallet address screening before settlement instruction generation. Both Elliptic and TRM Labs provide blockchain analytics and real-time screening APIs within the Arc environment. The screening result is logged against the trade record alongside entity-level counterparty screening, and the screening gate is a hard block — no Arc settlement instruction is generated for an unscreened or flagged wallet address. When Arc's planned view key architecture is available, Devancore will extend the compliance record to include view key issuance events: the identity of authorized parties, the scope of disclosure granted, and the regulatory examination context, creating an auditable chain of custody for confidential transaction data.

Related terms

Stablecoin Settlement
T+0 Settlement Operations
Delivery Versus Payment
Settlement Finality DLT Blockchain
Tokenized Collateral Repo Settlement
Cash Reconciliation Software
Position Reconciliation Software
Broker-Dealer Net Capital Rule