Files
smom-dbis-138/config
zaragoza444 ab1c46787b
Some checks failed
CI/CD Pipeline / Security Scanning (push) Has been cancelled
CI/CD Pipeline / Lint and Format (push) Has been cancelled
CI/CD Pipeline / Terraform Validation (push) Has been cancelled
CI/CD Pipeline / Solidity Contracts (push) Has been cancelled
CI/CD Pipeline / Kubernetes Validation (push) Has been cancelled
Validation / validate-genesis (push) Has started running
Validation / validate-terraform (push) Has been cancelled
Validation / validate-kubernetes (push) Has been cancelled
Validation / validate-smart-contracts (push) Has been cancelled
Validation / validate-security (push) Has been cancelled
Validation / validate-documentation (push) Has been cancelled
feat: production exchange/settlement configs and M2 token integration
Update production middleware and exchange configs, expand settlement adapter for M2 load/transfer flows, and align frontend dex config with dynamic M2 token registry.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-28 14:42:10 -07:00
..

config — reference JSON (non-secret)

Files such as address-inventory.chain138.json and runtime-env.chain138.json are reference snapshots produced during dotenv cleanup. They hold public contract addresses and RPC URLs — not private keys or API secrets.

  • Do not treat these as a replacement for .env where secrets are required.
  • When Chain 138 deployment addresses change, update canonical docs (parent repo docs/11-references/ADDRESS_MATRIX_AND_STATUS.md) and refresh these files if your tooling depends on them.

See parent repo docs/00-meta/SUBMODULE_HYGIENE.md for submodule workflow.