Trustchain protocol
draft-pouwelse-trustchain-01

Document Type Active Internet-Draft (individual)
Last updated 2018-06-05
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                         J. Pouwelse, Ed.
Internet-Draft                            Delft University of Technology
Intended status: Informational                              June 5, 2018
Expires: December 7, 2018

                          Trustchain protocol
                      draft-pouwelse-trustchain-01

Abstract

   Trustchain is a protocol for a networked datastructure, designed to
   act as a trust ledger.  This protocol acts as a decentralized
   alternative to platforms like eBay, Airbnb, and Uber.  It is
   specifically designed to record transactions among strangers without
   central control, support high transaction volumes, be application
   neutral, and avoid vendor lock-in.  The protocol defines recording
   transactions in an ordered list using an append-only datastructure, a
   new communication overlay, and a horizontally scalable consensus
   protocol based on checkpoint consensus, called CHECO.  Trustchain has
   resistance to traditional blockchain attacks, such as the 51 percent
   majority attack.  This is achieved by using a graph-based append-only
   datastructure combined with a personal blockchain for each
   participant with their own genesis block.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 7, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Pouwelse                Expires December 7, 2018                [Page 1]
Internet-Draft             Trustchain protocol                 June 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Purpose . . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     1.3.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Trustchain Stack: Engineering trust . . . . . . . . . . . . .   5
   3.  Trustchain Fabric: internal data structure  . . . . . . . . .   7
     3.1.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   7
     3.2.  TxBlock specification . . . . . . . . . . . . . . . . . .   9
     3.3.  Asynchronicity  . . . . . . . . . . . . . . . . . . . . .  10
     3.4.  CHECO: Consensus protocol and block format  . . . . . . .  11
   4.  IPv8: Overlay for identity, discovery and trust . . . . . . .  11
     4.1.  Identity establishment and discovery  . . . . . . . . . .  12
     4.2.  Attestations and trust  . . . . . . . . . . . . . . . . .  12
     4.3.  Peer-to-peer cryptographically signed messaging . . . . .  25
     4.4.  NAT traversal . . . . . . . . . . . . . . . . . . . . . .  25
   5.  Attack resistances  . . . . . . . . . . . . . . . . . . . . .  26
     5.1.  Sybil attacks . . . . . . . . . . . . . . . . . . . . . .  26
     5.2.  Double spending attack  . . . . . . . . . . . . . . . . .  26
     5.3.  Replay attack . . . . . . . . . . . . . . . . . . . . . .  27
     5.4.  Whitewashing attack . . . . . . . . . . . . . . . . . . .  27
     5.5.  Spam attack . . . . . . . . . . . . . . . . . . . . . . .  27
     5.6.  DDoS  . . . . . . . . . . . . . . . . . . . . . . . . . .  28
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  28
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  28
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  29
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  31

1.  Introduction

   For the past 10 years various distributed ledgers have been deployed
   and used.  This protocol aims to establish some form of trust using
   software.

   Creating trust between strangers is at the core of numerous
Show full document text