Skip to main content
Network: Stellar Testnet (Test SDF Network ; September 2015) Soroban RPC: https://soroban-testnet.stellar.org Horizon: https://horizon-testnet.stellar.org
Always cross-check against the live GET /config on the backend (https://trustline-rpxt.onrender.com/config) before sending a transaction — it’s the source of truth the frontend and SDK actually resolve against.

​
Current deployment

​
Superseded (kept for reference — do not build against these)

​
Why score_registry never moves but the others do

Every score ever published lives in one registry contract, permanently. The credit_line and lending_vault contracts, by contrast, get redeployed as the credit-risk engine and safety rails evolved — each redeploy is a fresh contract instance, but it re-reads the same permanent score history. This is deliberate: an agent’s track record shouldn’t reset just because the pricing or vault logic improved underneath it.

​
x402 excluded addresses

A small set of addresses are never counted as a revenue counterparty by the independence engine — facilitator/fee-sponsor infrastructure, the vault contract itself, and the testnet faucet (see Sybil / independence model for why funder addresses must be excluded rather than counted as revenue). The live, current list is always in GET /config’s implied exclude set — check backend/src/config.ts’s DEFAULT_EXCLUDE or the deployed X402_EXCLUDE_ADDRESSES env var for the authoritative list.