chore(devnet): evo-sdk 4.2.0-dev.5 + re-provision moutai after the wipe - #319
Conversation
…e wipe Moutai was re-genesised and upgraded to platform 4.2.0-dev.5 (protocol 14 current). The core chain survived, so all three identities were restored with their original ids by rebuilding chain asset-lock proofs from the original type-8 outpoints recorded in .devnet-locks.local - no faucet round needed. All contracts re-registered under the maker. Contract ids are hash(owner, nonce) and the nonce sequence replayed, so the old ids reattached to different contracts; .env.devnet now maps: social v3-topology AtEKZmw9... (owner-first indexes, bots funded 1000 YAPP, price set), profile 4CD14N..., and the eight feature contracts on the recycled ids (DM 3414JJ..., keyExchange 9Mrjgs33..., etc). evo-sdk bumped to 4.2.0-dev.5 (exact pin), which carries the protocol v14 ranked/HAVING/refersTo JS bindings (#4450) and the indexOnly document-type stack needed for the like overhaul. Validated: lint/tsc/build/build:devnet green; topology battery 31/31 against AtEKZmw9...; full devnet e2e 22 passed locally. Known pre-existing failure (unrelated): e2e/write/sensitive-content.spec.ts from #318 fails identically on dev.2 and dev.5, on testnet and devnet - the sensitive write never broadcasts. Co-Authored-By: Claude Fable 5 <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: Pro Plus 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 |
|
🕓 Ready for review — 2 ahead in queue (commit f132808) |
Deploying yappr with
|
| Latest commit: |
f132808
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://08f7501d.yappr.pages.dev |
| Branch Preview URL: | https://chore-devnet-dev5-reprovisio.yappr.pages.dev |
Deploying yappr-v2 with
|
| Latest commit: |
f132808
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c8222680.yappr-v2.pages.dev |
| Branch Preview URL: | https://chore-devnet-dev5-reprovisio.yappr-v2.pages.dev |
2 participants
Why
Moutai was re-genesised and upgraded to platform 4.2.0-dev.5 (protocol 14 current), killing every contract and identity the
/devnetdeployment pointed at. Separately, npm published@dashevo/evo-sdk@4.2.0-dev.5carrying the protocol v14 JS bindings (dashpay/platform#4450:documents.ranked()/having(), refersTo metadata) and the full indexOnly document-type stack — both prerequisites for the like overhaul (PLAN_LIKE_OVERHAUL.md).One PR because neither half deploys alone: the old env points at dead contracts, and the devnet CI job needs both.
What
@dashevo/evo-sdk→ 4.2.0-dev.5 (exact pin)..devnet-locks.local). No faucet round;E2E_IDENTITY_IDS, the maker, and the token authority are unchanged.hash(owner, nonce)and the nonce sequence replayed, so the old ids reattached to different contracts..env.devnetre-cut:AtEKZmw9vVniz89VtuLRQXT4Yjrpxd4MRjRfKugExenD4CD14N3rZbdRYtRvnyjYJfnteTeJpt8vLGcib6T5MRiB9Mrjgs33…is now keyExchange, not social).gitignore: cover the one-shot.devnet-lock-*.keyfiles.Verification
build/build:devnetgreen; zero new lint warnings.AtEKZmw9…on the upgraded chain.e2e/write/sensitive-content.spec.ts(feat: author-flagged NSFW posts with viewer-controlled gating #318) fails identically on dev.2 and dev.5, on testnet and devnet (where the contract has thesensitiveproperty) — the sensitive write never broadcasts (compose dialog never closes). Needs its own investigation.Note for the ipfs-mediaUrl branch
AtEKZmw9…was registered from the staging-tip contract JSON (pattern^https?://.+$). Thet3code/privacy-image-loading-controlsbranch's relaxed^(https?|ipfs)://.+$pattern still needs its own fresh registration + env flip when it merges (memory updated accordingly).🤖 Generated with Claude Code