2f58965f39
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 28s
CI/CD Pipeline / Security Scanning (push) Successful in 1m8s
CI/CD Pipeline / Lint and Format (push) Failing after 11s
CI/CD Pipeline / Terraform Validation (push) Failing after 16s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 24s
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 30s
Validation / validate-genesis (push) Successful in 8s
Validation / validate-terraform (push) Failing after 18s
Validation / validate-kubernetes (push) Failing after 2s
Validation / validate-smart-contracts (push) Failing after 3s
Validation / validate-security (push) Failing after 12m27s
Validation / validate-documentation (push) Failing after 4s
Verify Deployment / Verify Deployment (push) Failing after 11s
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
.envwhere 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.