Stub: follow the live on-chain evonode list for Platform reads #19
Labels
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rhelwig/DecentSite#19
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Around 2026-10-11 the mainnet seed hosts
seed-1/2/3.mainnet.networks.dash.orgstopped answering while Platform itself stayed up (hundreds of evonodes answering DAPI). The live Stub's Platform refresh was failing at the same time.The Stub's address handling is static:
quorums.<network>.networks.dash.org/masternodesonly once, at connect. The Stub connects once and runs for weeks, so it never picks up evonodes that were PoSe-banned or added later.DECENT_SITE_DASH_DAPI_ADDRESSESset,EvoSDK.withAddresseswas called withouttrusted, so the trusted-context proof verification was silently dropped.Fix (discovery order, DNS-free first)
Core/subscribeToMasternodeListagainsthttps://<ip>:<port>evonodes. The first message is the full list (CBORprotx diff). Candidates, in order: the saved last-known list, then the SDK's built-in seed IPs (evonode-bootstrap.ts, generated from wasm-sdk), thenDECENT_SITE_DASH_DISCOVERY_SEEDS. Up to 8 nodes are dialled, and a second node must agree (same block: identical evonode set; nearby block: ≥90% overlap). A lone answer is accepted only when no other node answered, and disagreeing answers are rejected. At least 3 usable evonodes are required.https://quorums.<network>.networks.dash.org/masternodes(needs DNS), only if every direct attempt fails.DECENT_SITE_DASH_DAPI_ADDRESSESpins the list (discovery off).DECENT_SITE_DASH_DISCOVERY=off/DECENT_SITE_DASH_DISCOVERY_DIRECT=offare the opt-outs.withAddresses).Quorum keys (remaining DNS dependency)
Trusted mode still fetches Platform quorum public keys from
quorums.<network>.networks.dash.orgat connect. Findings:newQuorums[].quorumPublicKey, including llmqType 4, the Platform quorums).WasmTrustedContext.prefetch*WithUrl(an HTTP quorum service).WasmContexthas no public constructor.Follow-ups
prefetchMainnetWithUrl, or upstream support for a custom context provider in evo-sdk.merkleRootMNListfrom the coinbase against the received list.Quorum-key research is in docs/QUORUM-KEY-HARDENING.md (PR #22). Recommendation: no DNS-free key fallback below SPV-level verification. Ask upstream for a JS-constructible / SPV-verified context provider.