|
|
||
|---|---|---|
| .. | ||
| entitlement-deploy.sepolia.json | ||
| entitlement-deploy.template.json | ||
| membership-deploy.sepolia.json | ||
| membership-deploy.template.json | ||
| offers.template.json | ||
| README.md | ||
| runtime-addresses.base-sepolia.json | ||
Deployment Directory
Place versioned deployment manifests here:
- chain id
- contract addresses
- deployment tx hashes
- verifier links
- policy hash snapshot
Template:
membership-deploy.template.jsonentitlement-deploy.template.jsonoffers.template.jsonruntime-addresses.base-sepolia.json(runtime-wired snapshot for cross-repo address parity)
Recommended process:
- Run
npm run deploy:sepolia/npm run deploy:mainnetfor membership ornpm run deploy:entitlement:sepolia/npm run deploy:entitlement:mainnetfor offer entitlements. - Copy the matching template to a dated file (for example
membership-base-sepolia-2026-02-18.json). - Offer override files may include non-contract metadata (for example
execution_profile) for downstream catalog parity; deploy script ignores unknown keys and only applies on-chain fields. - Fill all deployment fields from script output and explorer links.
- If you need per-offer pricing, copy
offers.template.json, edit values, and pass it viaOFFERS_JSON=/path/to/file.json.
Address parity rule:
- Keep
runtime-addresses.base-sepolia.jsonsynchronized with/Users/vsg/Documents/VSG Codex/web/docs/deployment/contract-addresses.base-sepolia.json. - Any runtime address change must update both repos in the same change set.