Conversation
This document outlines the requirements and expectations for a privacy-preserving bridge and cross-chain infrastructure, detailing functionality, security, usability, and team profile needed for development.
fryorcraken
requested changes
Mar 8, 2026
Collaborator
fryorcraken
left a comment
fryorcraken
left a comment
There was a problem hiding this comment.
A couple of things to fix before merge:
-
Wrong file path: The file is placed at
RFPs/RFPs/RFP-003-...(doubleRFPs/). Please move it toRFPs/RFP-003-bridges-cross-chain-infrastructure.md. -
README not updated: Please add RFP-003 to the summary table in
README.mdbetween theRFP_TABLE_START/RFP_TABLE_ENDmarkers.
Collaborator
|
Note: the license section in |
Collaborator
|
The title (and scope) is very broad. Before this RFP moves forward, we should discuss and decide what specific type(s) of bridges we want to see — e.g., Ethereum-only vs. multi-chain, lock-and-mint vs. burn-and-mint, trustless ZK light client vs. relayer-based, etc. |
|
Reading through this, It's presenting Logos as a "Privacy Preserving L1" we should be very clear here that the L1 is not the target for these atomic swaps. These atomic swaps are done against LEZ. It's a more complicated story but we should make it clear what the goal is: LEZ is where we have privacy preserving programmable money, the L1 is the settlement layer for Zones. |
4 tasks
fryorcraken
added a commit
that referenced
this pull request
May 22, 2026
Three RFPs removed; two lambda prizes added; remaining RFPs reframed around existing-project prior art. Removed RFPs: - RFP-022 (Bonded Atomic Swaps) - RFP-023 (Reputation-Based Atomic Swaps) - RFP-026 (Fee-Burn Atomic Swaps) These RFPs specified solutions to two open problems where the Logos team would rather not pre-judge the design. They were prescriptive about the mechanism (bonds, reputation primitives, fee-burns) when the more honest posture is to frame the problem and let solvers compete. New lambda prizes (staged in lambda-prizes/; to move to logos-co/lambda-prize when accepted): - LP-0018 (Anti-Spam Mechanism for Atomic Swaps): frames the taker-spam / free-option problem. References eigenwallet PR #675 as one example of reference prior art but does not prescribe the approach. Solvers may design bonds, fee-burns, reputation, deposits, slashing schemes, or any combination. Success criteria require non-custody preservation, incentive-compatibility argument, direction-coverage statement, and honest-refund handling. - LP-0019 (Off-Chain Verifiable Reputation for Atomic-Swap Makers): frames the off-chain attribution / verifiable-complaint problem. Lists naive view-key disclosure, FCMP++-grade zk proofs, multi-party attestation, and watchtower designs as candidates without prescribing the answer. Success criteria require sybil resistance, spam resistance, third-party verifiability without trusting the complainant, and complainant-side privacy. Reframed remaining RFPs around existing-project inspiration: - RFP-021: already cited Thorchain/Serai/Maya/Chainflip. Relationship section updated to point at LP-0018 and LP-0019 instead of the deleted RFP-022/023. - RFP-024: added "Inspired by existing prior art" paragraph naming Synthetix (CDP minting mechanic, SIP-302 Pools V3) and eigenwallet/ COMIT (peer-to-peer atomic-swap redemption). The novelty is the combination, not either half. Updated all cross-references to the deleted RFPs. - RFP-025: Option 2a now explicitly framed as inspired by Thorchain's bonded-validator model (operators post slashable stake against a defined performance contract); Option 2b explicitly framed as adopting sBTC's threshold-signer custody model with an oracle-priced peg layer. Both link to appendix-documented existing projects. - All references to RFP-022/023/026 replaced with pointers to LP-0018 or LP-0019 as appropriate. Appendix coverage check: every project named in the remaining RFPs (Thorchain, Serai, Maya, Chainflip, Wormhole, sBTC, Stacks, Synthetix, eigenwallet, COMIT, Farcaster, Haven, Liquality, AtomicDEX, Komodo, Secret Monero Bridge, Secret Network) is documented in at least one appendix (atomic-swaps-primer.md, cross-chain-trust-model-contrast.md, or synthetics-design-space.md). Decisions log (proposals-review/pr-57-decisions.md) appended with a "Bundle restructure 2026-05-22 (afternoon)" section summarising the shift. Deferred bond-system review findings (#3, #4, #5, #6, #7, #8, #12, #14) are no longer relevant since the bonded-atomic-swap design they applied to has been removed. Co-Authored-By: Claude Opus 4.7 (1M context) <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
3 participants
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.
This document outlines the requirements and expectations for a privacy-preserving bridge and cross-chain infrastructure, detailing functionality, security, usability, and team profile needed for development.