docs: quorum-key hardening research (design only) #22
No reviewers
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!22
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/quorum-key-hardening"
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?
Research and recommendation for removing the DNS / quorum-service dependency in proof verification. Refs #19.
Summary: evo-sdk trusts
quorums.<net>.networks.dash.org(/quorums,/previous,/masternodes) as its root of trust, with no chain verification, and refetches on a quorum-cache miss at read time. The DAPI mnlistdiff carries the same LLMQ_100_67 keys (24/24 matched on 2026-10-13). A loopback HTTPS quorum shim is feasible, but anything below SPV-level (ChainLock/checkpoint-anchored) verification is a downgrade. Recommendation: keep failing closed, optionally add disagreement telemetry, and ask upstream for a JS-constructible context and an SPV-verified context provider.Nothing implemented. Do not merge until reviewed.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.