feat(config): replace dead devnet-paloma with devnet-moutai - #33
Conversation
devnet-paloma has been torn down — its insight, quorums and faucet hostnames no longer resolve — so the built-in devnet entry pointed at nothing. devnet-moutai replaces it in dash-network-configs. All 13 HP masternodes from devnet-moutai.inventory are listed: the quorum service's /masternodes endpoint reports every one ENABLED with a successful DAPI version check (dapi/drive 4.2.0-dev.2), so none need pruning. Trusted context stays on, since quorums.moutai.networks.dash.org is deployed and serves /quorums, /masternodes and /previous. faucetBaseUrl is deliberately omitted: moutai's faucet is the legacy PHP MultiFaucet with no /api/status, so wiring it would render a button that only ever 404s. Verified against live moutai with the pinned evo-sdk 3.1.0-dev.7: devnetTrusted connect succeeds, proof-verifying reads return real data (epoch 0, protocolVersion 14; totalCreditsInPlatform 4655099998500000), and the built UI on ?network=devnet-moutai reports "Network healthy", generates a deposit address, and polls insight.moutai.networks.dash.org plus moutai masternodes on :1443. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PR replaces the ChangesDevnet Moutai support
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to This PR replaces the dead built-in devnet with an opt-in Moutai configuration while leaving mainnet and testnet behavior unchanged. It is mergeable with explicit owner awareness that the selected external services lack documented ownership, endpoint-rotation, and rollback expectations; the impact is limited to users selecting this devnet. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
Why
devnet-palomahas been torn down —insight.paloma.networks.dash.org,quorums.paloma.networks.dash.organdfaucet.paloma.networks.dash.orgno longer resolve at all — so the bridge's only built-in devnet entry pointed at nothing.devnet-moutaiis its replacement indash-network-configs(added in410e0bb, most recently touched bycf9f67b).What
DEVNET_PALOMA→DEVNET_MOUTAI, registered asdevnet-moutai, so it appears in the Devnet dropdown and at?network=devnet-moutai.devnet-moutai.inventoryare listed, in inventory order. The quorum service's/masternodesendpoint reports every oneENABLEDwithversionCheck: success(dapi/drive4.2.0-dev.2), so unlike paloma none need pruning.useTrustedContext: trueretained:quorums.moutai.networks.dash.orgis deployed and serves/quorums,/masternodesand/previous, so the SDK's DNS-derived default works with no explicittrustedQuorumUrl.faucetBaseUrldeliberately omitted. moutai's faucet is the legacy PHP MultiFaucet (reCAPTCHA); it has no/api/statusand no JSON POST endpoint, so wiring it up would render an in-app faucet button that only ever fails withFailed to fetch faucet status: 404. Users fund the displayed deposit address by hand from that page instead.'devnet-paloma'string inislock.test.ts(an arbitrary "devnet without RPC" name) follows along. Thesml-paloma-snapshot.binfixture insml.test.tsis left alone — it's captured historical CBOR test data.Testnet remains the default at the bare root URL; mainnet and testnet users are unaffected.
Verification
Against live moutai, using the
@dashevo/evo-sdkversion this repo already pins (3.1.0-dev.7) — worth confirming, since moutai runs protocol 14:EvoSDK.devnetTrusted('moutai')connects.epoch.current→{index: 0, protocolVersion: 14, firstCoreBlockHeight: 40501};system.totalCreditsInPlatform→4655099998500000.system.status()→core_chain_locked_height: 41352, matching Insight's tip exactly.Against the production build at
?network=devnet-moutai:DEVNET-MOUTAI; health indicator reads Network healthy.devnet-moutaias active; bare/still lands onTESTNET.yj4d6t…) with QR and mnemonic, no console errors.insight.moutai.networks.dash.org/insight-api/status?q=getInfo,insight.moutai.networks.dash.org/insight-api/addr/<addr>/utxo, andPlatform/getStatusagainst68.67.122.252:1443/68.67.122.207:1443. No faucet requests.tsc --noEmitclean; all 214 tests pass;npm run buildplus the build-artifact smoke check pass.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Bug Fixes