These RFCs capture abstractions, models, protocols and data formats for facilitating cross-ledger communication and transactions.
If you are new to Weaver (or to blockchain interoperability), we recommend starting with the protocol overview document.
If you wish to see Weaver in action, test it, or apply it to your own application, you can switch to the Getting Started Tutorial.
Instead, if you wish to find out more details about the Weaver design and wish to contribute to the code base, you can explore these RFCs, beginning with the models. Protocol engineers will find in RFC: 01-009 a useful overview of the relay model, and may then progress on to reading one of the existing protocols' design and implementation; e.g., the data sharing protocol in RFC: 02-001. If you are interested in adding support for a new ledger technology, see the existing driver implementations and existing interoperability module implementations. Where relevant we use ABNF for formal syntax definitions.
Precise definitions of terms you may encounter in these RFCs can be found in the terminology page.
The RFC numbering convention is: <type>:<id>
. The list of types (<type>
) is as follows:
<type> |
Document Type/Category |
---|---|
01 | Concepts and Models |
02 | Protocols and Mechanisms |
03 | Data Structures and Formats |
RFC # | Title | Category | Status |
---|---|---|---|
01-001 | Views | Model | Proposed |
01-002 | Cryptographic Proofs | Model | Proposed |
01-003 | Verifiable Observation of State | Model | Draft |
01-004 | Events | Model | Draft |
01-005 | Cross-Ledger Operations | Model | Draft |
01-006 | Atomic Cross-Ledger Transactions | Model | Proposed |
01-007 | Security Domains | Model | Proposed |
01-008 | End-to-End Confidentiality | Model | Proposed |
01-009 | Relays | Model | Proposed |
01-010 | Interoperation Modules | Model | Proposed |
01-011 | Identity Management | Model | Proposed |
01-012 | Identity Registry | Model | Proposed |
01-013 | Identity Agent | Model | Proposed |
01-014 | Identity Trust Anchor Agent | Model | Retired |
01-015 | Network Identity Updates | Model | Proposed |
02-001 | Data Sharing | Protocol | Proposed |
02-002 | Data Sharing in Fabric | Protocol | Proposed |
02-003 | Data Sharing in Corda | Protocol | Proposed |
02-004 | Asset Exchange through HTLC | Protocol | Proposed |
02-005 | Asset Exchange in Fabric | Protocol | Proposed |
02-006 | Asset Exchange in Corda | Protocol | Proposed |
02-007 | Asset Exchange in Besu | Protocol | Draft |
02-008 | Asset Transfer | Protocol | Proposed |
02-009 | Asset Transfer in Fabric | Protocol | Proposed |
02-010 | Asset Transfer in Corda | Protocol | Proposed |
02-011 | Identity and Config Sharing | Protocol | Superseded |
02-012 | Cross-Domain Identity Management | Protocol | Proposed |
02-013 | Security Domain Discovery | Protocol | Draft |
02-014 | Cross-Domain Negotiation | Protocol | Draft |
02-015 | Transaction Invocation | Protocol | Draft |
02-016 | Event Bus | Protocol | Draft |
02-017 | Security Domain Identity Validation | Protocol | Proposed |
02-018 | Cross-Domain Membership Syncing | Protocol | Proposed |
03-001 | View Address | Format | Proposed |
03-002 | Generic View | Format | Proposed |
03-003 | Fabric View | Format | Proposed |
03-004 | Corda View | Format | Proposed |
03-005 | Besu View | Format | Draft |
03-006 | Ethereum View | Format | Draft |
03-007 | View Request | Format | Proposed |
03-008 | Access Control Policy | Format | Proposed |
03-009 | Proof Verification Policy | Format | Proposed |
03-010 | Verification Policy DSL | Format | Draft |
03-011 | Membership | Format | Proposed |
03-012 | Network Identities | Format | Proposed |
03-013 | Asset Exchange Units | Format | Proposed |
03-014 | Asset Transfer Units | Format | Proposed |
03-015 | Relay Messages | Format | Proposed |
03-016 | Fabric Interop Chaincode API | Format | Proposed |
03-017 | Interoperation CorDapp API | Format | Proposed |
03-018 | Besu Interop Contract API | Format | Proposed |
03-019 | Application SDK | Format | Proposed |
03-020 | DID Method for DLT Networks | Format | Proposed |
NOTE: The following is only a tentative process pending further discussion.
- Draft
- Proposed
- Active
- Superseded
- Retired
- Abandoned