Pool Composition

A deployment is neither one pool nor one pool per pair. Assets are grouped into a small number of cores: each core holds legs that share a reserve, a curve family and a risk configuration. Below: why the cut, the roster each chain’s cores carry (generated from its deploy manifest), and what each class of core means.

Why several cores rather than one

Nothing in the protocol requires more than one pool. The grouping is an economic choice on three counts.

DriverConsequence
A shared curve must fit every leg it servesA core’s legs are priced by one shape scaled per asset. Similar depth and volatility profiles take that scaling well; a stablecoin and a single-name equity in one core force a shape that suits neither, since the width that keeps a $1 leg tight is nowhere near the width an equity needs
Correlated legs make inventory mean-revertFlow that drains one leg tends to arrive against another, so the skew that prices the imbalance also gets paid to undo it. Assets with no relationship accumulate one-sided inventory
Isolation bounds a failureA depeg, a dead feed or a halted asset stops only the core it belongs to. A stablecoin losing its peg does not take the equity book down with it

Legs inside a core are similar enough to share a curve and net against each other; cores differ enough that a failure stays in its core. The cut is a configuration decision, and composition is expected to change as rosters grow, as an asset’s behaviour diverges from the core it was placed in, or as a new class justifies its own core.

Every asset anchors directly to the base, so each core is a flat star on its base. That is the shape the manifests use, not the protocol’s: the anchor tree admits depth up to 4, and an asset may anchor to any correlated parent (Anchor Path Pricing).

Rosters below track the deployment manifests; per-pool membership authority is the receipt record each deploy ceremony writes per (pool, leg). Pool addresses: Contract Addresses. Per-asset metadata: Asset Registry.


Cores by chain

Monad

CoreCodeBaseLegsStatus
CoreCUSDCUSDC, WMON, CBBTC, WBTC, WETH, XAUT0created

Balances change by the block and are not recorded here: GET /v1/assets/pools and GET /v1/liquidity report them live.

Leg parameters: Monad

Launch config, from the deploy manifest; live values are on-chain and can differ after launch (read the pool’s Admin). Status is from the pool records. theta, minFee and minDisp in basis points (the manifest stores PBPS, parts per million), refBand and depegHalt in basis points, seedUsd the genesis seed.

CoreLegStatusClassCurvethetaminFeeminDispkapparefBanddepegHaltseedUsd
CoreUSDCdeployedstablebell_1000.512150–20002480
CoreWMONdeployedvolatilebell_500612.16150150–790
CoreCBBTCdeployedvolatilebell_50024.13150150–990
CoreWBTCdeployedvolatilebell_500383150150–0
CoreWETHdeployedvolatilebell_50036.14150150–700
CoreXAUT0deployedvolatilebell_500820150150150–0

Arc Testnet

CoreCodeBaseLegsStatus
StableSUSDCBUSDCB, USDT, USDS, USD1, PYUSDcreated
ForexFUSDCBUSDCB, EURC, QCAD, AUDF, JPYC, KRW1not created
CryptoXUSDCBUSDCB, USDT, WETH, WBTC, CBBTC, BNB, XAUT, PAXG, EURCcreated
EquityEUSDCBUSDCB, INTC, AMD, NVDA, ASML, SPCX, AVGO, TSLA, MSFT, ORCL, METAnot created

Balances change by the block and are not recorded here: GET /v1/assets/pools and GET /v1/liquidity report them live.

Leg parameters: Arc Testnet

Launch config, from the deploy manifest; live values are on-chain and can differ after launch (read the pool’s Admin). Status is from the pool records. theta, minFee and minDisp in basis points (the manifest stores PBPS, parts per million), refBand and depegHalt in basis points, seedUsd the genesis seed.

CoreLegStatusClassCurvethetaminFeeminDispkapparefBanddepegHaltseedUsd
StableUSDCBdeployedstablecn_w100_d100_flat0.250.922500–2500400
StableUSDTdeployedstablecn_w100_d100_wall0.261.81.766001501000400
StableUSDSdeployedstablecn_w100_d100_wall0.261.42.29600150–400
StableUSD1deployedstablecn_w100_d100_wall0.323.484.69600150500400
StablePYUSDdeployedstablecn_w500_d100_wall0.872.261.58600150–400
ForexUSDCBnot createdstablecn_w100_d100_flat0.250.922500–2500400
ForexEURCnot createdfxcn_w500_d500_flat51215.661500250–400
ForexQCADnot createdfxcn_w500_d500_flat51214.721500250–400
ForexAUDFnot createdfxcn_w500_d500_flat51224.931500250–400
ForexJPYCnot createdfxcn_w500_d500_flat51220.51500250–400
ForexKRW1not createdfxcn_w500_d500_flat51237.41500250–400
CryptoUSDCBdeployedstablecn_w100_d100_flat0.250.922500–2500400
CryptoUSDTdeployedstablecn_w100_d100_wall0.261.81.766001501000400
CryptoWETHdeployedvolatilecn_w500_d500_flat51520.342000300–400
CryptoWBTCdeployedvolatilecn_w500_d500_flat51218.872000300–400
CryptoCBBTCdeployedvolatilecn_w500_d500_flat51218.872000300–400
CryptoBNBdeployedvolatilecn_w500_d500_flat51218.422000300–400
CryptoXAUTdeployedvolatilecn_w500_d500_flat517.5151800200–400
CryptoPAXGdeployedvolatilecn_w500_d500_flat520.03151800200–400
CryptoEURCdeployedfxcn_w500_d500_flat51215.661500250–400
EquityUSDCBnot createdstablecn_w100_d100_flat0.250.922500–2500400
EquityINTCnot createdvolatilecn_w500_d500_flat51819.52500300–400
EquityAMDnot createdvolatilecn_w500_d500_flat51819.52500300–400
EquityNVDAnot createdvolatilecn_w500_d500_flat51819.52500300–400
EquityASMLnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquitySPCXnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquityAVGOnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquityTSLAnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquityMSFTnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquityORCLnot createdvolatilecn_w500_d500_flat51519.52500300–400
EquityMETAnot createdvolatilecn_w500_d500_flat51519.52500300–400

BNB Chain

CoreCodeBaseLegsStatus
CoreCUSDCUSDC, USDT, USD1, U, WBNB, BTCB, ETH, XAUT, QQQbplanned

Balances change by the block and are not recorded here: GET /v1/assets/pools and GET /v1/liquidity report them live.

Leg parameters: BNB Chain

Launch config, from the deploy manifest; live values are on-chain and can differ after launch (read the pool’s Admin). Status is from the pool records. theta, minFee and minDisp in basis points (the manifest stores PBPS, parts per million), refBand and depegHalt in basis points, seedUsd the genesis seed.

CoreLegStatusClassCurvethetaminFeeminDispkapparefBanddepegHaltseedUsd
CoreUSDCplannedstablebell_1000.512600–2000150000
CoreUSDTplannedstablebell_1000.61.21.826001001000150000
CoreUSD1plannedstablebell_1000.72.33.5600100500125000
CoreUplannedstablebell_1000.752.42.5260010050075000
CoreWBNBplannedvolatilebell_50012.52517600300–0
CoreBTCBplannedvolatilebell_50012.52516600300–0
CoreETHplannedvolatilebell_50012.52520600300–0
CoreXAUTplannedvolatilebell_5007.51510600300–0
CoreQQQbplannedequitybell_50012.52520600300–0

Roster symbols are upper-case and dot-free; the on-chain symbol() of a testnet mock differs (Asset Registry).

Stable core

The trading legs and the base are $1-pegged and run the depeg-band guards (Flow Guards). Risk parameters derive from measured density; shipped values are generated from the deployment manifests, not hand-tuned.

Crypto core

Wrapper variants of one asset can collapse onto one mark feed or keep their own; the Feed column of Asset Registry is the authority per chain.

Forex core

Non-USD fiat stablecoins, so unlike the stable core these are not $1-pegged: each marks against its own currency, and every non-base leg carries an independent breaker feed on the reference tier. A leg far from parity is sized from the real ceremony mark, never a peg default. The core is created once its currencies are signed.

Equity core

Created once its equity price source is live. Fee floors are fitted from measured density and ship with the listing, never as class defaults; a leg waits for tape and does not use a neighbour’s parameters. Rosters are picked by measured tick activity on the venue feed, not by general popularity; re-measure before changing one.

Faucet twins

A testnet base that is a mintable twin sits on every core. It owns no feed of its own: it reads the USDC-USD lane and has no reference band, only the parity halt (Asset Registry). Membership authority is the ceremony’s per-pool receipts, not any roster summary, the tables above included.

Future work: yield-bearing pooling

No NAV-accruing asset is listed today. A NAV wrapper’s fair value is its share price, which drifts upward, so bands sized around a $1 peg would fire on ordinary accrual. Planned for a later phase as a dedicated cohort with its own class, never inside the stable core: sUSDS, sUSDe, syrupUSDC, syrupUSDT, USYC. Requirements: NAV-aware marks (share price, not 1peg)andnon-pegparametrization(\kappa_{\text{cov}} > 0$ on every listed asset including the hub; see Parametrization and kappa).

See also