Expand description
Persistent deployment records for sdkt project deploy.
Every contract deployed by sdkt project deploy is recorded in a
.sdkt-deployments.json file next to .sdkt.toml, mapping each contract
alias to its on-chain contract ID. The record is written incrementally at
loop exit, so a deploy that fails halfway still preserves the contracts that
did land on-chain (see issue #74).
Records are scoped per network: deployments to testnet and mainnet live
under different keys and never overwrite each other. A re-run with
--skip-deployed reads the record and skips any alias whose recorded
contract ID still exists on-chain (verified via getLedgerEntries, not just
by the presence of a file entry).
Structs§
- Deployment
Record - A single deployed-contract record for one alias on one network.
- Deployment
Record File - The on-disk record file: a map of network key → (alias → record).
Constants§
- DEPLOYMENT_
RECORD_ FILE - Default name of the deployment record file (written next to
.sdkt.toml). - FUTURENET_
PASSPHRASE - MAINNET_
PASSPHRASE - TESTNET_
PASSPHRASE - Well-known passphrases mapped to human-readable network keys.
Functions§
- network_
key - Derive the stable per-network record key from the resolved network settings.