Skip to main content
These addresses come from the protocol’s network registry at revision d008ee1a. A registry entry identifies a configured address; it does not establish contract wiring, active markets, or feed availability.
Confirm the network passphrase and deployed contract links before using an address. Redeployment can change addresses independently of this table.
Require the two price-aggregator reads to agree. The controller does not expose public getters for its swap aggregator, accumulator, or position-NFT address; verify those through deployment records and contract storage.

​
Mainnet

RPC https://stellar-gateway.xoxno.com, passphrase Public Global Stellar Network ; September 2015.

​
Testnet

RPC https://stellar-testnet-gateway.xoxno.com, passphrase Test SDF Network ; September 2015. The published SDK 1.0.228 lists testnet price aggregator CAALOOTIDXCX7D7FMQIBSSAJLPKOM3GMXS4UUSTDIG42JCRRJHOPUHOP. It differs from the registry entry above. Read-only RPC simulations of price_aggregator() on governance and the controller both returned the registry address at ledger 5078359, checked on 2026-10-07T23:23:02Z. Use that address for this snapshot. Repeat both reads before an integration relies on the wiring. Use the registry’s hub_ids and spoke_ids mappings to resolve configured ids. Read get_spoke and get_spoke_asset on the controller to inspect a deployed spoke and its listings. Configured definitions alone do not prove a live listing. RWA oracle definitions can reference the XOXNO adapter. Verify each configured feed’s availability before relying on it; a registry entry does not prove a current price. See Oracles.

​
Next

Deployment

Build, deploy governance, and bring up the protocol.

Governance ABI

Governance entrypoints including the controller() lookup.