RFP-005: Multisig and Coordination#113
Draft
fryorcraken wants to merge 1 commit into
Draft
Conversation
Add the Multisig and Coordination RFP and its ecosystem-behaviour appendix, and register RFP-005 in the README index. The appendix (facts and observations only, product angle) leads with a data inventory: the ten distinct data/metadata items a multisig involves, whether each could be private on LEZ, and what existing multisigs (Safe, Squads, ERC-4337, Bitcoin script, FROST) do with it. It then covers the LEE public/private account model, the quorum-privacy spectrum, coordination channels and what each leaks, roles/policies, composition, and hardware support. Sourced from the research-multisig-sovereign vault. The RFP hardens the existing public multisig sample app (logos-co/lez-multisig) into production, adds an end-to-end-encrypted per-multisig coordination room via the Logos chat module, and ends with three A/B/C decisions for review: privacy posture, coordination channel, and quorum-model baseline. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Adds RFP-005 — Multisig and Coordination and its ecosystem-behaviour appendix.
What's here
RFPs/RFP-005-multisig-and-coordination.md— the RFP (tier L). Hardens the existing public multisig sample app (logos-co/lez-multisig) into a production M-of-N program, adds an end-to-end-encrypted per-multisig coordination room via the Logos chat module (RD-chat), and ends with three A / B / C decisions for review.appendix/multisig-coordination-ecosystem.md— facts-and-observations appendix, product angle. Leads with a data inventory: the ten distinct data/metadata items a multisig involves, whether each could be private on LEZ, and what existing multisigs (Safe, Squads, ERC-4337, Bitcoin script, FROST) do with each. Sourced from the research-multisig-sovereign vault.README.md— RFP-005 registered in the index.Decisions for review (in the RFP)
Draft pending these three choices being settled:
(recommended)/ private-by-default).(recommended)/ approvals through the room / both).lez-multisig(recommended)/ threshold-sig / account-model-now-with-future-seam.Notes
LP-0002,SA-public-multisig(lez-multisig),RD-chat— matches theRFP-XXX-multisignode in flywheels (ecosystem [MILESTONE] RFP-003 M1 — Design, threat model, LEZ-primitive verification, SDK trait surface #121).🤖 Generated with Claude Code