Solution: LP-0002 - Private M-of-N Multisig#91
Open
jeefxM wants to merge 3 commits into
Open
Conversation
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
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.
Anonymous M-of-N multisig for the Logos Execution Zone: a treasury is controlled
by N members, and a proposal releases funds once M of them approve, with each
individual approval staying anonymous among the public member set. Built natively
for the LEZ privacy-preserving-transaction model and the RISC0 zkVM.
Submitted by: Davit Maisuradze (@jeefxM)
main)HjHCub28GrUNgd2QuJ2SPob7YmaUgDRCGXwbt2jt4UWnEach approval is a real RISC0 STARK (~174 s at
RISC0_DEV_MODE=0) proving in-guestMerkle membership in the frozen member set without revealing which member, with a
proposal-bound nullifier that prevents double votes. Membership is bound to
shielded accounts by derivation: each member's secret is their real HD-derived
shielded-account nullifier secret key. A full 2-of-3 lifecycle is live on testnet
(proposal
Hf84MVjY), andscripts/lp0002-demo.shreproduces the whole flow atRISC0_DEV_MODE=0against a local standalone sequencer.solutions/LP-0002.mdincludes a success-criteria checklist with honest marks;the full write-up (threshold scheme, nullifier design, LEZ account model with the
nonce and program_owner handling, security assumptions, known limitations, and
integration guide) is in the implementation repo at
docs/LP-0002-solution.md.