Asset Profile Definitions for DLT Interoperability
draft-sardon-blockchain-interop-asset-profile-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Aetienne Sardon , Thomas Hardjono , Benedikt Schuppli | ||
| Last updated | 2021-07-03 (Latest revision 2020-12-30) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
In order for virtual assets to be traded or exchanged within online transactions, the parties involved in the transaction must have share a common definition of what constitute the virtual asset. Parties transacting on a DLT system must have the unambiguous means to refer to a common definition of an virtual asset, independent of the implementation of the virtual asset in question. This specification defines a JSON representation of a number of common information fields within asset profiles.
Authors
Aetienne Sardon
Thomas Hardjono
Benedikt Schuppli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)