Re: [Trans] Putting illegal stuff in an append only ledger

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Sat, 24 March 2018 02:50 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDE21276AF for <trans@ietfa.amsl.com>; Fri, 23 Mar 2018 19:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yp3TdKgM5Fi for <trans@ietfa.amsl.com>; Fri, 23 Mar 2018 19:50:30 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115D6127286 for <trans@ietf.org>; Fri, 23 Mar 2018 19:50:29 -0700 (PDT)
Received: from fifthhorseman.net (c-66-31-31-124.hsd1.ma.comcast.net [66.31.31.124]) by che.mayfirst.org (Postfix) with ESMTPSA id DAA53F9A5; Fri, 23 Mar 2018 22:50:27 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id 1650120DAF; Fri, 23 Mar 2018 20:40:21 +0000 (GMT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Tao Effect <contact@taoeffect.com>
Cc: Paul Wouters <paul@nohats.ca>, trans@ietf.org
In-Reply-To: <D6B17BF8-5DF3-4FEB-83B6-CC7383ADED7A@taoeffect.com>
References: <C7855D7B-E853-443F-9C7E-4C901216CDFB@nohats.ca> <A8C94DE7-537D-4455-97A6-65E54D537D0B@taoeffect.com> <87k1u5sqv2.fsf@fifthhorseman.net> <D6B17BF8-5DF3-4FEB-83B6-CC7383ADED7A@taoeffect.com>
Date: Fri, 23 Mar 2018 20:40:20 +0000
Message-ID: <87fu4qo79n.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/hJJU1LTF7gb9Nwu7JKKPT-1yujY>
Subject: Re: [Trans] Putting illegal stuff in an append only ledger
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2018 02:50:31 -0000

On Wed 2018-03-21 18:22:57 -0400, Tao Effect wrote:
> This is specific to Bitcoin and Bitcoin-like datastructures which
> simply do not allocate enough room for arbitrary data.

Thanks for clarifying this!  If i understand correctly, your argument
appears to depend on all three of the following assertions:

 a) the chunks of arbitrary data that can be injected in the
    datastructure in question are smaller than some specific size (let's
    call it X bytes).

 b) there is no standard mechanism used for the datastructure in
    question that aggregates multiple pieces of arbitrarily-injected
    data into any larger structure.

 c) there is no toxic data that is X bytes or smaller.

is that right?  I don't know the Bitcoin protocol that well.  What is
the value of X for the Bitcoin blockchain?

Is (a) some sort of general principle that we should try to include in
designs of any append-only globally-distributed datastructures?

how do we ensure that (b) remains the case?  how do we verify that (c)
is true in the jurisdictions that we care about?

   --dkg