The RFCs capture abstractions, models, protocols and data formats for facilitating cross-ledger communication. For newcomers we recommend starting with the protocol overview document followed by the RFCs on models. Protocol engineers will find in RFC: 01-007 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 transfer protocol in RFC: 02-002. 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.
Through out the RFCs if you come across terminology that might be not well defined in the context it is used in, refer to terminology for precise definitions of these terms.
RFC # | Title | Category | Status |
---|---|---|---|
01-001 | Verifiable Observation of State | Model | Draft |
01-002 | Cryptographic Proofs | Model | Draft |
01-003 | Views | Model | Proposed |
02-004 | Events | Model | Draft |
01-005 | Fair Exchange | Model | Draft |
01-006 | Identity | Model | Draft |
01-007 | Relays | Model | Draft |
Security | Model | Draft | |
02-001 | Event Bus | Protocol | Draft |
02-002 | Data Transfer | Protocol | Draft |
02-003 | Asset Exchange - HTLC | Protocol | Draft |
Asset Transfer | Protocol | - | |
Discovery | Protocol | - | |
Protocol Negotiation | Protocol | - | |
03-001 | Address | Format | Proposed |
View - Definition | Format | Draft | |
View - Fabric | Format | Draft | |
View - Corda | Format | Draft | |
View - Ethereum | Format | Draft | |
Attachments | Format | - | |
Policy - Access Control | Format | Proposed | |
Policy - Proof Verification | Format | Proposed | |
Policy - Verification DSL | Format | Draft | |
Memberships | Format | Proposed |
NOTE: The following is only a tentative process pending further discussion.
- Draft
- Proposed
- Active
- Superseded
- Retired
- Abandoned