Zero-liquidity routing
Transfers are designed to move through issuer-authorized channels instead of liquidity pools.
Institutional Settlement Surfaces
Aethelred documents stablecoin routing as zero-liquidity-pool infrastructure for institutional flows, not as an AMM bridge or generic payments product. The current source surface combines CCTP V2 for Circle burn-and-mint routing, TEE issuer mint flows for non-CCTP assets, proof-of-reserve monitoring, Merkle audit roots, relayer bonding, and governance controls around the live InstitutionalStablecoinBridge.sol contract.
The docs explicitly frame this as issuer-authorized routing rather than pooled bridge liquidity.
Reserve anomalies, oracle staleness, velocity breaches, and tx-limit breaches are designed to trigger circuit-breaker behavior.
Stablecoin infrastructure uses a dedicated five-key institutional control model with a 3-of-5 threshold for critical operations.
Overview
The stablecoin layer is currently documented as a routing and control surface for institutional settlement. It is not published here as a consumer wallet product, a public stablecoin issuance program, or a live partner roster.
Transfers are designed to move through issuer-authorized channels instead of liquidity pools.
USDC-style flows use Circle CCTP V2; non-CCTP flows use issuer-gated TEE attestations.
Proof-of-reserve feeds, deviation checks, heartbeat windows, and Merkle audit roots all exist in the current contract design.
The implementation exists in the repository and is described as a testnet routing contract, so this page documents surface area and controls rather than a live asset registry.
Routing Modes
Aethelred separates routing by asset type and trust model, which is why the stablecoin surface reads more like settlement infrastructure than like a universal bridge.
Used for Circle burn-and-mint routing. The contract exposes bridgeOutViaCCTP, relayCCTPMessage, and relayCCTPFastMessage for stablecoins that already support Circle's issuer-native transport path.
Used for non-CCTP assets. The contract exposes mintFromAttestedRelayer and redeemTeeStablecoin for issuer-approved mint and redemption flows anchored to enclave measurements and issuer signer sets.
| Mode | Asset Class | Primary Entry Points | Trust Surface | Why It Exists |
|---|---|---|---|---|
| CCTP V2 | Circle-supported assets such as USDC | bridgeOutViaCCTP, relayCCTPMessage, relayCCTPFastMessage | Circle burn-and-mint messaging plus bonded relayers | Maintains issuer-native settlement instead of synthetic pooled liquidity. |
| TEE Issuer Mint | Non-CCTP stablecoins | mintFromAttestedRelayer, redeemTeeStablecoin | Issuer signer quorum plus approved enclave measurements | Allows issuer-controlled issuance and redemption when a direct CCTP-style channel does not exist. |
Risk Controls
The current stablecoin configuration surface is not just routing metadata. It includes explicit ceilings, thresholds, and monitoring hooks intended to constrain issuer and relayer behavior.
mintCeilingPerEpoch and dailyTxLimit cap stablecoin expansion and transfer volume at the configuration level.
hourlyOutflowBps and dailyOutflowBps create velocity controls around exits and redemptions.
monitorReserve uses reserve feeds, deviation thresholds, and heartbeat windows to trigger pause behavior on anomalies.
recordMerkleAuditRoot and verifyReserveMerkleProof bind off-chain reserve reporting back into verifiable on-chain evidence.
The whitepaper and tokenomics both describe circuit breakers for reserve anomaly, oracle staleness, velocity breach, and transaction-limit breach. The contract adds Chainlink Automation entry points via checkUpkeep and performUpkeep so the monitoring loop is operational rather than aspirational.
Governance and Economics
Stablecoin infrastructure is controlled through a narrower key set and stronger operational constraints than generic application flows, which is appropriate for issuer-routed value transfer.
Control Model
The published model uses five institutional governance keys: issuer, issuer recovery, foundation, auditor, and guardian.
| Control | Current Source | Meaning |
|---|---|---|
| Governance threshold | 3-of-5 | Critical operations require agreement across the institutional signer set. |
| Minimum action delay | 7 days | The contract hard-codes a floor through MIN_GOVERNANCE_ACTION_DELAY. |
| Joint unpause | 3 to 5 signatures with issuer anchor | unpauseWithJointSignatures requires valid unique signers and an issuer-side anchor. |
Economic Alignment
The current design adds economic consequences to message relay instead of assuming good behavior from routing operators.
DEFAULT_RELAYER_BOND_REQUIREMENT is set to 500,000, and tokenomics explicitly describes a 500,000 AETHEL relayer bond requirement.
postRelayerBond, withdrawRelayerBond, and slashRelayerBond make participation, exit, and penalty flows part of the contract surface.
Contract Surface
This page is not an ABI dump. It focuses on the functions that define routing, governance, reserve monitoring, and relayer operations in the live repository.
| Function | Why It Matters |
|---|---|
| configureStablecoin | Defines the asset, routing type, reserve feed, quotas, and heartbeat/deviation thresholds. |
| setIssuerSignerSet | Publishes the issuer signer quorum used for issuer-gated mint paths. |
| setEnclaveMeasurement | Approves or revokes enclave measurements used by TEE issuer-mint flows. |
| mintFromAttestedRelayer | Executes issuer-approved minting for TEE issuer-mint assets. |
| bridgeOutViaCCTP | Initiates Circle burn-and-mint routing for supported assets. |
| relayCCTPMessage / relayCCTPFastMessage | Handles standard and fast relayed CCTP settlement paths for bonded relayers. |
| redeemTeeStablecoin | Burns balances for issuer-controlled redemption on non-CCTP assets. |
| monitorReserve | Checks proof-of-reserve state and can pause minting when thresholds are breached. |
| recordMerkleAuditRoot / verifyReserveMerkleProof | Anchors reserve audit evidence and lets downstream systems verify it later. |
| checkUpkeep / performUpkeep | Supports automated reserve checks and circuit-breaker execution. |
Pair this page with the Financial Services reference for workflow context, and with the Smart Contracts page for the wider contract surface around bridges, governance, and verification.
Current Boundary
The stablecoin layer is meaningful enough to document, but not so mature that we should blur the difference between repository-backed design and publicly launched settlement corridors.
The current docs describe routing modes and governance controls, but they do not publish a live list of issuers, custodians, or active settlement partners.
This site does not publish a mainnet-ready supported-asset registry with contract addresses and production domains.
The published material frames stablecoins as institutional routing infrastructure, not as a retail wallet or consumer payments product.
The contract itself is described as a testnet routing contract, so this page documents current architecture and controls rather than claiming an already-live issuance network.