SATP Gateway Crash Recovery Mechanism
draft-belchior-satp-gateway-recovery-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Rafael Belchior , Miguel Correia , Andre Augusto , Thomas Hardjono | ||
Last updated | 2024-01-07 (Latest revision 2023-07-06) | ||
Replaces | draft-belchior-gateway-recovery | ||
RFC stream | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo describes the crash recovery mechanism for the Secure Asset Transfer Protocol (SATP). The goal of this draft is to specify the message flow that implements a crash recovery mechanism. The mechanism assures that gateways running SATP are able to recover faults, enforcing ACID properties for asset transfers across ledgers (i.e., double spend does not occur).
Authors
Rafael Belchior
Miguel Correia
Andre Augusto
Thomas Hardjono
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)