Contract addresses & events

This page is the on-chain reference for Noether: every deployed contract address on the live stack, the network configuration to reach them, 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 — what https://noether.exchange and the gateway at https://noetherapi-production.up.railway.app serve — deployed 2026-07-06:

Notes:

• NOE is a SAC-wrapped classic Stellar asset — code NOE, issuer GCKIUOTK3NWD33ONH7TQERCSLECXLWQMA377HSJR4E2MV7KPQFAQLOLN (the admin account). It is pre-minted to the Liquidity Vault and moved by transfer; there is no runtime minting.
• 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 for the full price chain.
• All amounts and prices on-chain use 7-decimal fixed point: raw 10_000_000 = 1.0.

Verify what a deployment actually serves

The gateway echoes the exact 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://noetherapi-production.up.railway.app/v1/health

{
  "status": "ok",
  "network": "testnet",
  "contracts": {
    "market":        { "address": "CAE3U7JK…YMEC", "source": "manifest" },
    "vault":         { "address": "CBLVZZ55…2UL6", "source": "manifest" },
    "noeracleShim":  { "address": "CBY4YLPY…T6UK", "source": "manifest" },
    "noetherRouter": { "address": "CDH4CY3X…44S4", "source": "manifest" },
    "usdcToken":     { "address": "CA63EPM4…VNR4", "source": "manifest" },
    "noeToken":      { "address": "CD7VRBXI…TDP5", "source": "manifest" },
    "vaultFactory":  { "address": "CAZPVI2P…TVP5", "source": "manifest" },
    "referral":      { "address": "CCV5NWLG…GXEE", "source": "manifest" }
  }
}

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.

Network configuration

The public testnet RPC endpoint is rate-limited; for anything beyond light reads, use your own or a paid RPC provider. Mainnet is planned but not live — no Noether contracts are deployed there. See Networks for details.

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, and prices are i128 values in 7-decimal fixed point.
• IDs (position_id, order_id) are u64; addresses are Stellar Address values; asset is a Symbol like BTC.

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

Market contract

order_cancelled reasons:

Liquidity Vault contract

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.

Referral contract

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 raw events and serves them over REST (GET /v1/events) and streams them over WebSocket. See the REST API and WebSocket references.
• Explorer — each stellar.expert link above shows a contract’s recent invocations and events.

Next steps

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