https://t.me/+DOylgFv1jyJlNzM0
Why this matters
The deploy tooling (scripts/deploy-config.json, scripts/deploy.ts) references the four contract WASM artifacts, and the backend/frontend read contract IDs from env, but there is no committed registry of which contract IDs are deployed on which network (testnet/futurenet/mainnet). Contributors wiring the backend or running E2E flows have to ask in chat for the current testnet IDs. A single source-of-truth table avoids repeated onboarding friction and mismatched envs.
Acceptance criteria
Files to touch
docs/deployed-contracts.md (new)
README.md, CONTRIBUTING.md
Out of scope
- Automating address publication from the deploy script
- Committing any secrets/keys
https://t.me/+DOylgFv1jyJlNzM0
Why this matters
The deploy tooling (
scripts/deploy-config.json,scripts/deploy.ts) references the four contract WASM artifacts, and the backend/frontend read contract IDs from env, but there is no committed registry of which contract IDs are deployed on which network (testnet/futurenet/mainnet). Contributors wiring the backend or running E2E flows have to ask in chat for the current testnet IDs. A single source-of-truth table avoids repeated onboarding friction and mismatched envs.Acceptance criteria
docs/deployed-contracts.md) with a per-network table: contract name -> deployed contract ID -> deploy date / versionFiles to touch
docs/deployed-contracts.md(new)README.md,CONTRIBUTING.mdOut of scope