QX Interoperability - v.0.7
  • 💡ABOUT
    • License
    • How to Give Attribution For Usage of QX Interoperability
  • 👬Industry Initiatives
    • ISO Interoperability Framework
    • EEA Crosschain Interoperability Specification Suite
    • IEEE Standards for Blockchain Interoperability
    • ICMA Bond Data Taxonomy
    • IETF Secure Asset Transfer Protocol
    • SODA MIT Crosschain Interop WG
    • Decentralized ID for Tokenization
    • Cross-chain Interoperability Alliance
    • SWIFT Coalition
    • BIS Projects
    • MAS Projects
    • Regulated Liability Network
      • UK Finance - Regulated Liability Network
      • US - Regulated Liability Network
    • Hyperledger Projects
    • EEA-OASIS L2 WG
    • RollColl WG
    • ITU Digital Currency Global Initiative
    • EIP-5164: Cross-Chain Execution
    • EIP-3220: Crosschain Identifier Specification
    • EIP-7281: Sovereign Bridged Token
    • ERC-7092: Financial Bonds
    • ERC-3643: Permissioned Tokens
    • ERC1400: Universal Token for Assets and Payments
    • ERC6960: Dual Layer Token
    • CASA CAIPs
    • COSMOS IBC
    • Polkadot XCM
    • IEEE Crosschain Workshop
  • 🏦Use Cases
    • Payments/Digital Asset Transactions
      • Enable transfers of digital payment tokens
      • Conduct Compliant Cross-VASP Digital Asset Transaction
      • Swap NFT for Tokenized Bank Deposits
      • Enable Intra-Group Payments with Tokenised Deposits
    • Wholesale CBDC (wCBDC)
      • Enable Settlement with Simultaneous Delivery versus Payment
      • Facilitate Cross-Border Payments with wCBDC
      • Enable FX transactions to facilitate cross-border payments
      • Settle Crypto Derivatives using wCBDC
      • Access Liquidity via wCBDC
      • Settle Interbank Payments with wCBDC
      • Settle Interbank Payments with wCBDC (Acquirer-Merchant Settlement)
      • Make Property Payments with Tokenized Deposits
      • Provide FX Liquidity using wCBDC
      • Enable Payment versus Payment (PvP)
      • Crosschain digital bonds trades
    • Decentralized Finance (DeFi)
      • Aggregate Yields across Blockchains for Corporate Treasuries
    • Retail CBDC (rCBDC)
      • Provide Targeted Government Transfers (Government Vouchers)
      • Streamline Home Equity Lending
      • Provide Corporate Vouchers and Rewards
      • Make Milestone-Based Property Purchase Payments
      • Enable Traceable and Targeted Donations
      • Consumer Prepayments to Corporations
      • Enable Asset Transactions
      • Enable Cross-Border Remittances
      • Government Payouts
      • Managing Learning Accounts
    • Private Markets/Asset Tokenization and Trading
      • Tokenize and Trade Private Equity Fund Shares
      • Distribute and Settle Private Corporate Debt Issuance
      • Trade Employee Stock Grants as Digital Securities
      • Enable Secondary Trading for Non-Listed Assets and Private Markets
      • Automated Discretionary Portfolio Management with Tokenized Assets
    • Trade & Commerce
      • Support Tokenized Electronic Bills of Lading for Global Trade
      • Commercial Vouchers
      • Online Commerce
      • Programmable Rewards
    • DAOs
  • 🛠️Solutions Providers
    • Swift
    • Mastercard
    • Fnality
    • Quant Network
    • Ownera
    • Fujitsu
    • Deutsche Bank/Standard Chartered Ventures
    • Kaleido
    • Onyx/JP Morgan
    • Canton Network
    • Universal Digital Payments Network Alliance
    • Li.Fi
    • Visa
    • Partior
    • CLSNet
    • Impel
    • Adhara
    • Datachain
    • Ant Group
    • CitiGroup
    • WeBank
    • IMF ?
    • BIS ?
    • Progmat ?
    • GroundX ?
  • 📓Requirements
    • Legal & Regulatory Layer
    • Governance and Policies Layer
      • Audit and Compliance sub-layer
      • Operations sub-layer
    • Application Layer
    • Integration and Middleware Layer
      • Oracle sub-layer
    • Semantic Layer
    • Syntactic Layer
    • Foundational Layer
      • Discovery sub-layer
      • Smart contract sub-layer
      • Function call sub-layer
      • Messaging sub-layer
      • Transaction sub-layer
      • Consensus sub-layer
      • Data transfer sub-layer
      • Security sub-layer
        • Identity and Authentication
        • Data Privacy
    • -
  • Protocol Providers
    • Chainlink
    • Axelar
    • Connext
    • Across
    • Toposware
    • IBC
    • Hyperlane
    • Sovereign Labs
    • Polymer Labs
    • Orb Labs
    • Zetachain
    • Sygma
    • deBridge
    • Wormhole
    • Routeur Protocol
    • Synapse
    • Wanchain
    • Gnosis
    • LayerZero
    • Comparison
  • Bridging Approaches
    • Bridges
    • Native Bridge
    • Third Party bridge
    • Multi-bridge
    • Oracle
    • Shared Sequencer
    • Mechanisms
      • Hash Locking
      • Notary Schemes
      • Proof Aggregation
    • zk-rollup ecosystems
    • Intent-centric
    • Function Calls
    • Relayers
      • Multisig
      • MPC
      • Light Client
      • ZKP Stark
      • ZKP Snark
      • Hybrid method
Powered by GitBook
On this page
  • Overview
  • Analysis
  • Reviewer

Was this helpful?

  1. Industry Initiatives

IETF Secure Asset Transfer Protocol

Industry Initiatives

Overview

Initiative Name

Secure Asset Transfer Protocol (satp)

Organization

Internet Engineering Task Force

Type

Standard

Description

The goal of the Secure Asset Transfer Protocol (SATP) working group is to develop a standard protocol that operates between two peer gateways for the purpose of transferring digital assets between an originator in the origin network to a beneficiary in a destination network. The protocol is agnostic with respect to the type of asset being transferred, and the type of networks.

Ecosystem

Agnostic

Public Participants

MIT

Quant Network

Blockdaemon

Aiven

IBM

Other confirmed confidential participants

Date Started

2020

Status

Draft - Under development

Link

The IETF Secure Asset Transfer Protocol (SATP) specification was initiated by IBM and Quant Network in 2020. It utilizes a burn-and-mint paradigm to move assets between origin and destination networks and ensures properties like atomicity, consistency, isolation and durability. The specification covers architectural aspects like APIs, flows, identifiers and resource descriptors. It also defines protocols for identity verification, transfer initiation, asset locking, and commitment finalization. Transfer resumption, errors, and security considerations are addressed.

It is important to note that the SATP is still in the development phase. Nevertheless, in its current state, SATP provides a concrete asset transfer protocol that can be implemented for production systems. It is intended to be blockchain-agnostic and focuses narrowly on the gateway-to-gateway transmission aspects. As such, it stands as a robust standard for how regulated digital asset transfers can be achieved securely using a coordinated burn-and-mint mechanism.

Organizations and projects interested in ensuring secure and standardized asset transfers across multiple DLTs should consider staying up to date on the IETF SATP's development and updates.

Analysis

Scope and Purpose

Target Audience

DLT developers, Researchers, Product Managers and technical stakeholders interested in secure asset transfers across multiple opaque distributed networks.

Coverage

Defines architecture, messaging flows, and cryptographic methods for atomic transfers of digital assets between distributed networks.

Technical Aspects

Architecture

Gateway-to-gateway protocol operating between two endpoints. Uses asset burn-and-mint paradigm.

Interoperability

Provides standardized APIs.

Security Measures

Cryptographic signatures, proofs, and hashes to ensure integrity and non-repudiation.

Adoption and Implementation

Vendor-agnostic Reference implementation

Current Adopters/Vendor Implementations

Is there a quant implementation?

Case Studies

None

Ease of Implementation

Governance and Update Mechanism

Oversight Body

Internet Engineering Task Force (IETF) - SATP WG

Update Mechanism

IETF update processes, which typically involve community feedback, working group discussions, and iterative draft versions.

Strengths and Weaknesses

Advantages

Challenges

Compatibility and Integration

Inter-standard Compatibility

Extensibility

Given its design, SATP is likely to be extensible to accommodate future changes or additions,

Community and Support

Community Engagement

Support Channels

IETF community forums, mailing lists, and working group meetings.

Future Roadmap

Next Step

Long-term Vision

Comparative Analysis

Comparative Analysis

Reviewer

We have contacted or we will contact the proposed reviewer.

Proposed reviewer: Dr Thomas Hardjono, CTO of Connection Science and Technical Director of the MIT Trust-Data Consortium at MIT

Review status: Not started.

PreviousICMA Bond Data TaxonomyNextSODA MIT Crosschain Interop WG

Last updated 1 year ago

Was this helpful?

SATP-Core (ODAP):

https://datatracker.ietf.org/wg/satp/about/ https://datatracker.ietf.org/doc/draft-ietf-satp-core/
https://github.com/hyperledger/cacti/tree/main/packages/cactus-plugin-odap-hermes
👬
Page cover image