Files
smom-dbis-138/config
zaragoza444 33e93165f6
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m29s
CI/CD Pipeline / Security Scanning (push) Successful in 2m40s
CI/CD Pipeline / Lint and Format (push) Failing after 46s
CI/CD Pipeline / Terraform Validation (push) Failing after 26s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 26s
Validation / validate-genesis (push) Successful in 27s
Validation / validate-terraform (push) Failing after 28s
Validation / validate-kubernetes (push) Failing after 12s
Validation / validate-smart-contracts (push) Failing after 13s
Validation / validate-security (push) Failing after 1m17s
Validation / validate-documentation (push) Failing after 18s
fix: normalize production configs, types, and cross-platform frontend build
Repair double-spaced source files, align middleware/exchange types with production JSON, and fix vite build on Windows/Linux.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-06-28 14:45:38 -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.