Point frontend at the preprod contract e354e672 - #11
Merged
Conversation
Deployed 2026-09-03T00:27Z on preprod ("Shielded Night" / sNight / 6),
from the src/managed build this repo commits (byte-identical at 0b0a358 and
main). Not locked: it stays upgradeable until a lock is chosen deliberately.
The PreProd entry appears in the network dropdown as soon as this lands.
acedward
added a commit
that referenced
this pull request
Sep 3, 2026
Brings in from main: PR #11 (frontend/.env PREPROD_ADDRESS=e354e672...) and PR #12 (scripts/verify-deployment.ts --allow-unlocked + scripts/verify-args.ts + tests + docs, plus a bun-1.4 lockfile regeneration with new root overrides compact-js 2.5.1 / onchain-runtime-v3 3.0.0 and a frontend onchain-runtime-v3 3.0.0 override). Conflict resolution: package.json / frontend/package.json kept this branch's own v9 overrides (ledger-v9 1.0.0-rc.3, compact-runtime 0.19.0, onchain-runtime-v4 4.0.0-rc.3, plus frontend's compact-js 2.5.5-rc.8) and documented in the //overrides comment why main's v8-line overrides (compact-js 2.5.1, ledger-v8 8.1.0, onchain-runtime-v3 3.0.0) do not apply to this dependency graph: ledger-v8 and onchain-runtime-v3 are not in this tree at all, and compact-js is already pinned exact here so needs no defensive override. bun.lock and frontend/bun.lock were not hand-merged: both were deleted and regenerated with bun 1.4.0 over a git-archive-style export (no root .env mounted or read), then verified frozen-installable, exactly one copy each of ledger-v9 / compact-runtime / onchain-runtime-v4 / compact-js in both trees, and zero copies of ledger-v8 / onchain-runtime-v3. Everything else (README, TESTING, frontend/.env, scripts/verify-deployment.ts, scripts/verify-args.ts, its unit test) auto-merged cleanly with no conflicts.
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
1 participant
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.
Records the ShieldedNight contract deployed on preprod so the network dropdown offers PreProd (hosted page after the next manual
deploy.ymlrun; any stack page that serves this build).e354e6725893397e6a2dfa44522a017fabb5d9c92efed50288711f5f865c8950MN_ENV=preprod, name "Shielded Night" /sNight/ 6 decimalssrc/managed/as committed — byte-identical onmainand on0b0a358(PR #9), which is the tree the deploy ran fromMN_ENV=preprod CV_ADDRESS=e354e672… bun run verify:deployment→ all 11 circuits' on-chain verifier keys==local keysscripts/lock.tsfrom the deploying machine/wallet is the one-way door when wanted. The verify script's non-zero exit on an unlocked contract is expected today (see theEXPECT_LOCKEDdiscussion in the organizer's Q8).Only
frontend/.envchanges, which is the committed audit trail for deployed addresses per the README. Non-breaking.