Skip to content

deployed-contracts.md

Latest commit

 

History

History
60 lines (39 loc) · 1.94 KB

deployed-contracts.md

File metadata and controls

60 lines (39 loc) · 1.94 KB
Raw

Deployed Contract Registry

This is the single source of truth for deployed Soroban contract IDs across all networks. Update this file whenever a contract is (re-)deployed.

Secrets note: contract IDs are public addresses — safe to commit. Never commit secret/admin keys here.

Testnet (Test SDF Network ; September 2015)

RPC: https://soroban-testnet.stellar.org
Explorer: https://stellar.expert/explorer/testnet

Contract Contract ID Deploy Date Version / Commit
loan_manager not yet recorded — —
lending_pool not yet recorded — —
remittance_nft not yet recorded — —
multisig_governance not yet recorded — —
token (USDC-like pool token) not yet recorded — —

How to fill this in: after running scripts/deploy.ts, copy the printed contract IDs into the table above and open a PR. Include the deploy date (YYYY-MM-DD) and the short git commit SHA or release tag.

Environment variables that consume these IDs

Backend (backend/.env)

Contract Env var
loan_manager LOAN_MANAGER_CONTRACT_ID
lending_pool LENDING_POOL_CONTRACT_ID
remittance_nft REMITTANCE_NFT_CONTRACT_ID
multisig_governance MULTISIG_GOVERNANCE_CONTRACT_ID
token POOL_TOKEN_ADDRESS

Frontend (frontend/.env)

The frontend does not currently read contract IDs directly from env. It calls the backend API, which resolves contract addresses at runtime using the backend vars above.

Futurenet

No contracts deployed yet.

Mainnet

No contracts deployed yet.

Updating this file

  1. Deploy (or redeploy) via scripts/deploy.ts.
  2. Copy the contract IDs from the deploy output into the relevant table row.
  3. Set the same IDs in your local backend/.env (and CI secrets for staging/production).
  4. Commit the updated table in the same PR as any contract change.