]> Seoul National Univ.

fun@snu.ac.kr

Daejeon Univ.

yonggeun.hong@gmail.com

MIT

hardjono@mit.edu

Applications and Real-Time Secure Asset Transfer Protocol Gateway Digital asset network Asset transfer This memo provides guidelines to developers of gateway systems, digital asset networks and client applications for the Secure Asset Transfer Protocol (SATP). Multiple gateways can represent the same digital asset network following the SATP standards, which necessitate basic implementation guidelines as outlined in this document. It also serves as an introduction to the SATP processing workflow for those new to the SATP standards. The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Secure Asset Transfer Protocol mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction This document proposes implementation guidance from the perspective of developers of peer gateways and digital asset networks. The Secure Asset Transfer Protocol (SATP) facilitates communication between peer gateways and other entities such as digital asset networks and client applications. A digital asset network can be connected to multiple peer gateways to enable asset transfers while ensuring interoperability. To ensure consistency across multiple peer gateways, appropriate guidelines are necessary. Peer gateways must implement a secure asset transfer mechanism that meets essential requirements related to atomicity, consistency, isolation, and durability (ACID). Security and privacy are also critical requirements. Therefore, this document involves several considerations beyond the SATP interface. The existing SATP core documents (, ) provides most of the key implementation guidelines, but this document offers a more elaborated description of each phase within peer gateways and digital asset networks.

| GW1 | <------> | GW2 | | Network | | NW1 | | | | | | NW2 | | | | | | | | | | | | | | | | | +---------+ +---------+ +---------+ +---------+ Figure 1. Scope of the SATP implementation ]]>

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Security Considerations TBA

IANA Considerations There are no IANA considerations related to this document.

In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Acknowledgments TBA