chore(contracts): record testnet deployment - #1020
Merged
Merged
Conversation
Deploys the registry and demo-emitter contracts to Stellar testnet via deploy/deploy_testnet.sh and commits the resulting contract IDs and wasm hashes. This is what flips CI's verify-provenance job from skip to a real check, and what apps/web's fireDemoEvent.ts needs to stop returning DemoEmitterNotConfiguredError on the /demo/contracts "Fire test event" button. registry: CCM4U5BGSLAGD2OYHAQUYLXVZNWI4EECJYPVJMOBSYI434FZ5Z2LGIWO demo-emitter: CAP6TJP7WVVSAK5BKKAA32J6G7RPT6X6Q7US7SMBGZ3NZ73HSXFNFCRH Both wasm hashes verified against on-chain state via `stellar contract fetch` before committing.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…uild The first deployment (939be5ae.../e16bedfd...) redeployed here was built locally without CARGO_HOME normalization: soroban-sdk's ledger.rs embeds its own absolute source path via a panic-location capture, so the wasm hash differed by build machine even with identical source and identical rustc version. verify-provenance's independent rebuild in CI (CARGO_HOME= /home/runner/.cargo) correctly caught the drift and failed. Rebuilt with RUSTFLAGS="--remap-path-prefix=$CARGO_HOME=/home/runner/.cargo" to match CI's embedded path exactly, confirmed the local build hash equals CI's independently-rebuilt hash, and redeployed both contracts from that exact wasm. registry: CDSCV5WBIK74OXFQLJMBMJHBWYBNEFGQGEG2YBKVKJSIWKP676AJF2QA demo-emitter: CBWXJ3AJZ7Y57XZWZV75VZRRSCZ5DT5VLPKKSC6FYG4YI4ELO5AXBBVP
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
registryanddemo-emitterto Stellar testnet viacontracts/deploy/deploy_testnet.shand commits the resulting contract IDs and wasm hashes todeployed.testnet.json.verify-provenancein.github/workflows/contracts.ymlfrom an automatic skip (placeholder detection) to a real hash-comparison check.apps/web/lib/fireDemoEvent.tsalready reads this file as a fallback whenDEMO_EMITTER_CONTRACT_IDisn't set - no code change needed there, this file alone should unblock the/demo/contracts"Fire test event" button onceDEMO_EMITTER_SECRETis also configured (see follow-up below).registry:
CCM4U5BGSLAGD2OYHAQUYLXVZNWI4EECJYPVJMOBSYI434FZ5Z2LGIWOdemo-emitter:
CAP6TJP7WVVSAK5BKKAA32J6G7RPT6X6Q7US7SMBGZ3NZ73HSXFNFCRHFollow-up (not in this PR, needs secrets only the repo/Vercel owner can set)
SOROBAN_CONTRACT_ID(registry id above) +SOROBAN_INVOKER_SECRETforintegration.yml's nightly test.DEMO_EMITTER_CONTRACT_ID(demo-emitter id above) +DEMO_EMITTER_SECRET(a key scoped only to the harmless no-argping()call - deliberately separate fromSOROBAN_INVOKER_SECRET).Test plan
stellar contract fetchbefore committing (see commit message)verify-provenancejob goes green (real check now, not a skip)