Contracts and events

This page is the on-chain reference for Noether: every deployed contract address on the live stack, how to confirm what a running gateway is pointed at, and the complete list of events each contract emits with exact field order, so indexers and integrations can decode them without guesswork.

Deployed contracts (Stellar testnet)

The production stack, which testnet.noether.exchange and the gateway at https://noether-api.proudmeadow-533cf0d8.germanywestcentral.azurecontainerapps.io serve:

Snapshot from the gateway on 2026-09-18, stack deployed 2026-07-21. Live values: the gateway's /v1/health response.

Notes:

• NOE is a classic Stellar asset, code NOE, issued by GA7PCANKNREYVUMU6CCOPJHVE5XCRUCFLZ6CGS3GX4BNDBR63QAVLVUZ, wrapped as a Stellar Asset Contract (the NOE address above). It is pre-minted to the liquidity vault and moved by transfer; there is no runtime minting.
• USDC is a test asset issued for Noether, also wrapped as a Stellar Asset Contract. It has no real-world value.
• Noeracle is the external signed-price source. The market reads prices through the shim, and the router relays signed attestations into Noeracle at trade time. See Oracle and price feeds.
• Addresses change whenever contracts are redeployed or the Stellar testnet resets. Do not hardcode them; read them from GET /v1/health at startup.
• All amounts and prices on-chain use 7-decimal fixed point: raw 10_000_000 = 1.0.

Deployed contracts (Stellar mainnet, guarded mode)

Deployed on 2026-10-03. The stack is live but dark: the market is paused (mode 1: no new positions; closes, cancels and withdrawals stay possible), the liquidity vault holds no funds, and every admin operation needs two of three keys. Since 2026-10-05 the vault's deposit cap is set to zero and creating a trader vault is limited to the admin, so no funds can enter before the opening. Trading opens after the independent audit; see Security and audits. The settlement asset on mainnet is Circle's USDC.

Every address is verifiable on stellar.expert: the deployed code hashes equal the testnet builds for the market, vault, router, shim and referral contracts; the vault factory carries two fixes that landed after the testnet deployment (see the changelog). market.get_pause_state returns [1, 1791048662]. There is no mainnet gateway, keeper or indexer while the stack is paused.

Verify what a deployment actually serves

The gateway echoes the contract addresses it resolved at boot from GET /v1/health. This is the ground truth for what the live API is pointed at:

curl -s https://noether-api.proudmeadow-533cf0d8.germanywestcentral.azurecontainerapps.io/v1/health

{
  "status": "ok",
  "network": "testnet",
  "contracts": {
    "market":        { "address": "CBHHWFAY...KYKNN", "source": "env" },
    "vault":         { "address": "CBSWA5P7...ZBSYE", "source": "env" },
    "noeracleShim":  { "address": "CDRQJDCZ...SWU6N", "source": "env" },
    "noetherRouter": { "address": "CBDVQKYE...T44LG", "source": "env" },
    "usdcToken":     { "address": "CA63EPM4...TVNR4", "source": "manifest" },
    "noeToken":      { "address": "CADEAZ3T...BQ4H5", "source": "env" },
    "vaultFactory":  { "address": "CAG5E6IM...NQKT7", "source": "env" },
    "referral":      { "address": "CB4A2OHP...2REND", "source": "env" }
  },
  "indexer": { "lastLedger": 4731934, "ledgerAgeSeconds": 6 },
  "market": { "pauseState": { "mode": 0 } },
  "counts": { "chainOpenPositions": 47, "indexedOpenPositions": 47, "drift": false }
}

Addresses are abbreviated here; the live response returns them in full. Each entry carries a source field telling you whether the address came from the deployment manifest or an environment override. See System endpoints for the full health response shape.

The contracts themselves agree on the wiring: the router's get_market and get_noeracle, the shim's get_noeracle, the vault's get_market_contract, the vault factory's get_market and the referral registry's get_market all return the addresses above. You can call any view function as a read-only simulation with the Stellar CLI, for example stellar contract invoke --id <MARKET> --network testnet --source-account <ANY_FUNDED_ACCOUNT> -- get_asset_risk --asset BTC; append -- --help instead of a function name to list a contract's functions and their documentation.

Network configuration

The testnet passphrase, RPC and Horizon endpoints are on Networks, together with the mainnet parameters for the guarded deployment above.

Event reference

Soroban contracts publish events as a tuple of topics plus a data payload. Below, the topic symbol is shown in quotes and the data tuple lists fields in their exact on-chain order. Conventions:

• direction serializes as the Direction enum: Long = 0, Short = 1.
• Amounts, sizes, prices and rates are i128 values in 7-decimal fixed point.
• IDs (position_id, order_id) are u64; a vault factory vault_id is u32; addresses are Stellar Address values; asset is a Symbol such as BTC.

These events are what the Noether indexer consumes to build the REST projections (positions, trades, leaderboard, vaults, referrals) and the WebSocket event streams. See WebSocket.

Market contract

order_cancelled reasons:

Liquidity vault contract

The indexer archives every topic above except aum_cap_set, shortfall_bps_set, reserve_cap_set and asset_cap_set.

Vault Factory contract (Trader Vaults)

Vault factory events carry the vault ID as a second topic, so you can filter per vault without decoding payloads.

The indexer archives every per-vault topic; allowlist_set, max_vaults_set and admin_rotated carry no vault ID and are not decoded.

Referral contract

The indexer archives code_created, referrer_set, trade_recorded and claimed.

Reading events yourself

Events are available three ways:

• Soroban RPC: getEvents against https://soroban-testnet.stellar.org, filtered by the contract addresses above.
• Noether gateway: the indexer archives the decoded events and serves them over REST (GET /v1/events, filterable by topic, contract, from_ledger, to_ledger and before_ts) and streams them over WebSocket. See the REST API and WebSocket references.
• Explorer: each address in the table above links to the contract's page on a Stellar block explorer, which shows recent invocations and events.

Next steps

• Architecture: how the market, vault, router and oracle fit together
• Oracle and price feeds: the Noeracle price chain these contracts depend on
• Networks: testnet details and the mainnet plan