RFP-003: rescope to BTC/XMR/ZEC, unblock via LEZ primitive status#49
Open
fryorcraken wants to merge 6 commits into
Open
RFP-003: rescope to BTC/XMR/ZEC, unblock via LEZ primitive status#49fryorcraken wants to merge 6 commits into
fryorcraken wants to merge 6 commits into
Conversation
The "blocked pending LEZ timelock support" banner is no longer accurate — BlockValidityWindow and TimestampValidityWindow exist on logos-execution-zone main. Replace it with a "ready to start" status and add an LEZ Primitive Status section so applicants can reason about the LEZ side without first auditing the source: file-cited inventory of present primitives (BIP-340 Schnorr, WitnessSet 2-of-2, validity windows, clock program, SHA-256), the two design constraints (Schnorr verify lives at the witness/auth layer not as an in-guest syscall; no native n-of-m threshold), and two open questions applicants should confirm early (s-malleability after acceptance; validity-window enforcement timing). Tighten Bitcoin references with DLC-specs AdaptorSignature.md, Aumayr et al. 2021, and secp256kfun; fix the Fournier link. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "no native n-of-m threshold" constraint was overstated. WitnessSet validates every (sig, pubkey) pair independently, so a guest program can apply its own threshold policy over the validated signer set with no syscall needed. The actual constraint is narrower: a program cannot verify an *arbitrary* (message, sig, pubkey) triple — e.g. a stored signature from prior off-chain coordination. The swaps in this RFP do not hit that case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds LEZ–ZEC as the fourth supported pair, scoped to Zcash transparent (t1...) addresses via BIP-199-style HTLCs (with ECDSA adaptor sigs as an encouraged variant for cross-chain unlinkability). Zcash shielded (Sapling / Orchard) is explicitly out of scope: there is no production atomic-swap construction for shielded pools today, the cryptographic state of the art does not provide a drop-in design for RedJubjub / RedPallas with per-spend re-randomization, and treating shielded as a research deliverable rather than a delivery deliverable matches what every production Zcash swap (Zwap, Maya) actually does. The new appendix/zcash-atomic-swap-primitives.md captures the feasibility matrix, the re-randomization wrinkle for shielded adaptor sigs, and the trust-model distinction between atomic swaps and TSS-vault routing (Maya). Updates: Functionality req #5 (Zcash transparent), Usability reqs #1 and #11 (LEZ–ZEC SDK, zcashd/zebrad node setup), Supportability per-pair SDK and doc-packet items, Demos checklist, Recommended Team Profile, and Resources. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
4 tasks
4 tasks
Merge the adaptor-sig-update branch (PR #48) into this one and rescope the RFP: the Ethereum pair moves from core scope to a soft requirement, and Zcash transparent joins Bitcoin and Monero as the third core pair. Add appendix/btc-xmr-adaptor-swap-primitives.md so every cryptographic claim in the RFP (HTLC linkability, Taproot indistinguishability, the h4sh3d/COMIT key-share protocol, timelock ordering) is documented in a sourced ecosystem survey, matching the existing Zcash appendix. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fryorcraken
changed the title
3 tasks
ETH will reach LEZ via wrapping, which needs no swap counterparty; an Ethereum swap pair is now fully out of scope. eth-lez-atomic-swaps stays cited as prior art for the LEZ escrow structure only. Co-Authored-By: Claude Fable 5 <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.
Rescopes RFP-003 and unblocks it. This PR now supersedes #48 (closed), whose content is merged in here.
Scope change
From #48 (merged into this branch)
Appendices (every RFP claim is documented)
appendix/zcash-atomic-swap-primitives.md: transparent vs shielded feasibility, BIP-199 HTLC layout, shielded research gaps, Maya contrast, feasibility matrix.appendix/btc-xmr-adaptor-swap-primitives.md(new): sourced survey backing the Bitcoin and Monero claims (HTLC cross-chain linkability, Taproot key-path indistinguishability, h4sh3d/COMIT key-share protocol with cross-curve DLEQ, timelock ordering, production prior art).🤖 Generated with Claude Code