Secure Asset Transfer Protocol (SATP)
bofreq-hardjono-secure-asset-transfer-protocol-satp-01
Document | Type | Approved BOF request | |
---|---|---|---|
Title | Secure Asset Transfer Protocol (SATP) | ||
Last updated | 2022-09-29 | ||
State | Approved | ||
Editor | Thomas Hardjono | ||
Responsible leadership | |||
Send notices to | (None) |
Name: Secure Asset Transfer Protocol
Description
There is currently an interoperability problem in many digital asset networks, where assets in one network cannot be moved easily to another network. The problem is more acute in the case of private asset networks, where external entities have no visibility into the state of an asset in the private network.
One example is the private shipping logistics networks where the digital Bill of Lading as the value-bearing data-object is not accessible to external entities, such as trade finance networks, seeking to issue Letters of Credit based on the Bill of Lading. A second example is regulated digital representations of real-world private assets, such as property ownership certificates, and regulated government-issued digital currencies.
The goal of the Secure Asset Transfer Protocol (SATP) working group will be to develop a standard protocol which operates between two peer gateways for the purpose of transferring digital assets and data between an originator in the origin network to a beneficiary in destination network.
Required Details
-
Status: WG Forming
-
Responsible AD: Roman Danyliw / Paul Wouters (Security Area)
-
BOF proponents: Thomas Hardjono <hardjono@mit.edu>, Martin Hargreaves <martin.hargreaves@quant.network>, Venkatraman (Rama) Ramakrishna <vramakr2@in.ibm.com>, Ned Smith <ned.smith@intel.com>, Denis Avrilionis <denis@compell.io>
-
BOF chairs: TBD
-
Number of people expected to attend: 100
-
Length of session (1 or 2 hours): 2 hours
-
Conflicts (whole Areas and/or WGs)
- Chair Conflicts: Security Area working groups
- Technology Overlap: TBD
- Key Participant Conflict: RATS-WG; SAAG; SCITT-BOF
Information for IAB/IESG
To allow evaluation of your proposal, please include the following items:
There is currently no standard protocol to perform transfer of digital assets from one network to another. To begin addressing these challenges, SATP will employ the gateway paradigm as a means for digital assets to be moved from one network to another through a standardized asset transfer protocol implemented between peer gateways. The same gateway paradigm will be used for data sharing between two networks, when one or both are private networks.
The following is a list of currently known related open source projects:
Weaver: https://github.com/hyperledger-labs/weaver-dlt-interoperability
Cactus: https://github.com/hyperledger/cactus/tree/main/packages/cactus-plugin-odap-hermes
Compellio: https://github.com/compellio/tz-verifiable-data-registry/tree/testnet
Agenda
- Charter Discussion
- Other
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
-
SAT Mailing List: https://www.ietf.org/mailman/listinfo/sat
-
SAT Draft charter: https://bit.ly/3CIcYN1
-
Relevant drafts:
- SAT Use Cases:
- SAT Architecture
- Secure Asset Transfer Protocol
- Data Sharing Protocol
- TBD