zaragoza444
1cce8ed08f
Some checks failed
CI/CD Pipeline / Solidity Contracts (push) Failing after 1m14s
CI/CD Pipeline / Security Scanning (push) Successful in 2m27s
CI/CD Pipeline / Lint and Format (push) Failing after 45s
CI/CD Pipeline / Terraform Validation (push) Failing after 22s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 25s
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 37s
Validation / validate-genesis (push) Successful in 28s
Validation / validate-terraform (push) Failing after 25s
Validation / validate-kubernetes (push) Failing after 10s
Validation / validate-smart-contracts (push) Failing after 11s
Validation / validate-security (push) Failing after 1m16s
Validation / validate-documentation (push) Failing after 18s
Verify Deployment / Verify Deployment (push) Failing after 55s
Production server binds Gitea on :3000, so token-aggregation now uses :3100 with a dedicated production env profile and nginx upstream. Co-authored-by: Cursor <cursoragent@cursor.com>
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.