DLT Gateway Crash Recovery Mechanism
draft-belchior-gateway-recovery-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Rafael Belchior , Miguel Correia , Andre Augusto , Thomas Hardjono | ||
| Last updated | 2022-11-21 (Latest revision 2022-05-20) | ||
| Replaced by | draft-belchior-satp-gateway-recovery, draft-belchior-satp-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 Open Digital Asset Protocol (ODAP), called ODAP-2PC. The goal is to assure gateways running ODAP to be able to recover from crashes, and thus preserve the consistency of an asset across ledgers (i.e., double spend does not occur). This draft includes the description of the messaging and logging flow necessary for the correct functioning of ODAP-2PC.
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.)