Repository navigation
feat(devnet): point /devnet at the beta.3 contracts (social v8, blog v3, storefront v3) - #565
Merged
Merged
Conversation
…v3, storefront v3) Moutai was wiped for Platform 4.2.0-beta.3, so every beta.2 contract this file named is gone and /devnet has been reading ids that do not exist. All ten contracts were republished under the maker in one fresh group after burning identity nonces 1-20, which would otherwise have reproduced the beta.1 and beta.2 ids against different schemas. The ids and the topology flags move together in this one commit: deploy.yml rebuilds /devnet from this file on every push to staging, and a v8 client against a v7 contract fails totally rather than degrading. The bundled snapshot is regenerated from the live chain (10/10). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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
Points
/devnetat the Platform 4.2.0-beta.3 contracts. Moutai was wiped for beta.3, so every id this file named is gone and the deployed site has been reading contracts that do not exist since the reset.All ten contracts were republished under the maker in one fresh group
9eHKb3jFZwoG428DUHqJ9ftUbqeYrt7CCmGrwuGVHYbt, registered on the social create. Identity nonces 1-20 were burned first: a contract id isgenerateId(owner, nonce), so a maker restored at nonce 0 would have reproduced the beta.1 ids on nonces 1-10 and the beta.2 ids on 11-20 while the schemas behind them changed — and both the browser SDK's contract cache andlib/contracts/bundledare keyed by id with every version equal to 1, so a cached v7 body would pass the staleness check and the client would silently run v7 semantics against v8.CuSB2obg51YgNsqw3hoqNLdxVVVSU4wgnL2BN5rx5S3uBrTRnGoGQFLPdnqriu7H4jv6Pfk1S5aSdovTzXzZjdQhAVYWRFXXQr3eKj6dCi1beDeyRKWp7iq7e2pkXE8sZpRoD5pMHWHEDaYAHeFRk3rHS5reP5h3L8Sf4476jXjH2arSCvxssNPzgvW1iJ51AxvLXtRu1vePDzkB1HiAxxBdVBr64KeUaXoJ61FqTibWBgiyKq9ZBz3rbm5xcs73vbtV3VeC6tmPMAoURDrYhh7kquovbg4MotPqmLf6rKukTGmB4pgd4yaAufauUGCV2rm1FezyjQVbY1xW2a6dTskWAnsxQW3pEn7AnUi3eGoVzHUMrMh5J2C5LeAGhCc4Ru8nymFg4DxsCR8aL9B85hT2y86DDRcF1ejUvnA3TLt2jQmmQwTqig9AThe ids and the topology flags move in this one commit (
v8social,v3blog,v3storefront).deploy.ymlrebuilds/devnetfrom this file on every push tostaging, and a v8 client against a v7 contract fails totally rather than degrading, so the two must never sit in separate commits.Changes
.env.devnet: the ten ids, the topology flags, the new group id, and a rewritten deployment note recording what social v8 / blog v3 / storefront v3 add and listing every superseded beta.2 id as DO-NOT-REUSE.lib/contracts/bundled/devnet-moutai.json: regenerated from the live chain withNETWORK=devnet node scripts/snapshot-contracts.mjs --prune(10/10 written, stale entries pruned).Verification
state: verifiedfor all ten.npx vitest run lib/contracts— 4 passed.npm run build:devnet— clean static export.$actionFeeAgreement(feat(contracts): social v8, blog v3, storefront v3 on the 4.2.0-beta.3 grammar #563) together.Follow-up
The corpus reseed and the verification batteries (
verify-v8.mjsplus the five feature batteries) are still running. Their results and the full deployment-evidence section fordocs/PLATFORM_BETA3_UPGRADE.mdland in a follow-up commit on this branch, so/devnetdoes not stay broken waiting for them. The site will fill in as seeding proceeds.🤖 Generated with Claude Code