You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
counter_contract_increment.rs (and related docs/web-client tutorials) reference a hardcoded counter contract address that was deployed with v0.14 tools on devnet.
AccountId is derived from the code commitment, which uses the Poseidon2 hash function in v0.14. This means:
v0.13-deployed contract addresses are invalid for v0.14 clients (procedure hash mismatch)
A v0.14 contract deployed with the same deterministic seed on testnet will produce mtst1XYZ (same suffix as mdev1XYZ)
Required action (when testnet upgrades to v0.14)
Run deploy_counter_deterministic.rs with the same seed against testnet RPC
Verify the resulting address suffix matches the devnet deployment
Context
counter_contract_increment.rs(and related docs/web-client tutorials) reference a hardcoded counter contract address that was deployed with v0.14 tools on devnet.AccountId is derived from the code commitment, which uses the Poseidon2 hash function in v0.14. This means:
mtst1XYZ(same suffix asmdev1XYZ)Required action (when testnet upgrades to v0.14)
deploy_counter_deterministic.rswith the same seed against testnet RPCrust-client/src/bin/counter_contract_increment.rsto the combined form (following the PR fix: deploy tutorial addresses on both testnet and devnet #177 pattern) so it works on both networksNote
counter_contract_fpi.rsis not affected — it deploys in-session and requires no hardcoded address.