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

Tao Effect <contact@taoeffect.com> Wed, 21 March 2018 22:23 UTC

Return-Path: <contact@taoeffect.com>
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 7210E129C6C for <trans@ietfa.amsl.com>; Wed, 21 Mar 2018 15:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.353
X-Spam-Level:
X-Spam-Status: No, score=-1.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=taoeffect.com
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 DVrMxsFz5AUJ for <trans@ietfa.amsl.com>; Wed, 21 Mar 2018 15:23:00 -0700 (PDT)
Received: from homiemail-a9.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56C08129C6A for <trans@ietf.org>; Wed, 21 Mar 2018 15:23:00 -0700 (PDT)
Received: from homiemail-a9.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTP id CD20F5BE06F; Wed, 21 Mar 2018 15:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=taoeffect.com; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=taoeffect.com; bh=u5v2M08QDHS1XHSrq kE727pIV4k=; b=PvDshcRAKrJkDwk/aKCys7ppmpSPtciygUWaazVUVTBJUnv8n CybMZNPPQAkObP+oUliej2v4ISbHWk0cUR6nyv9bjXbmHmYC3lATTbPlSwBWkNl4 eMLUxu14YkvfAPHk6WsAP+nWhULKVFZPv8THa3NybAaJZcZg5DwUeuGuUY=
Received: from [192.168.42.64] (184-23-252-36.fiber.dynamic.sonic.net [184.23.252.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: contact@taoeffect.com) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTPSA id 78E815BE06B; Wed, 21 Mar 2018 15:22:59 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_FB6B9EC5-15FF-4834-B591-C0BCC8D87183"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Tao Effect <contact@taoeffect.com>
In-Reply-To: <87k1u5sqv2.fsf@fifthhorseman.net>
Date: Wed, 21 Mar 2018 18:22:57 -0400
Cc: Paul Wouters <paul@nohats.ca>, trans@ietf.org
X-Mao-Original-Outgoing-Id: 543363777.57776-8809b0931e15815af23e2853fe31cc23
Message-Id: <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>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/oEkbx6LEeb2Z9Zsflz3CMTea-CY>
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: Wed, 21 Mar 2018 22:23:02 -0000

> IIUC, the webforum comments that these links point to argue that because
> there is work required outside the blockchain to assemble the toxic
> data, the data in question doesn't *just* reside in the blockchain.  Is
> that right, or do you have another interpretation?

Yes, I (same person who wrote those comments), am arguing that there is a difference between an image, a video, etc., and scrambled bits of data that need _special instructions_ to *re-assemble* them into an image, video, etc., and that this should be self-evident.

> I don't see how it follows from this particular situation that there
> would be no way to put toxic data in the global append-only ledger that
> Bitcoin depends on.  Do you think that there is some principled reason
> why the blockchain can avoid ingestion of toxic data of any form,
> whether it's (depending on your jurisdiction) CP or "intellectual
> property" or blasphemy or hate speech or …?

I am arguing that /Bitcoin's/ blockchain is not designed to support such "toxic ingestion" of such content.

> Does your argument for why the bitcoin blockchain is defended against
> this hold for arbitrary global append-only datastructures, or is it
> specific to bitcoin?

This is specific to Bitcoin and Bitcoin-like datastructures which simply do not allocate enough room for arbitrary data.

That they can be hacked into getting tiny pieces of arbitrary data to be stored in separate chunks, requiring re-assembly through special knowledge (e.g. a special tool and precise knowledge of which transaction to pass through that special tool), does not mean that these datastructures are somehow the entity to point to as carriers of "toxic data".

If you were to argue that they are, then you can equally argue that the entire Internet is illegal because it can be used, with specialized tools and specialized knowledge, to transport toxic data.

- Greg

--
Please do not email me anything that you are not comfortable also sharing with the NSA.

> On Mar 21, 2018, at 5:46 AM, Daniel Kahn Gillmor <dkg@fifthhorseman.net <mailto:dkg@fifthhorseman.net>> wrote:
> 
> On Tue 2018-03-20 19:12:04 -0400, Tao Effect wrote:
>> I don't think it's a real problem, just another week, another social
>> attack on Bitcoin from those who are heavily invested in seeing
>> Bitcoin die.
>> 
>> The reason why it's not a legitimate issue are here:
>> 
>> https://lobste.rs/s/walhsk/child_abuse_imagery_found_within_bitcoin#c_xf6oor <https://lobste.rs/s/walhsk/child_abuse_imagery_found_within_bitcoin#c_xf6oor>
>> 
>> And here:
>> 
>> https://lobste.rs/s/walhsk/child_abuse_imagery_found_within_bitcoin#c_76hm8v
>> 
>> But that will not stop people from pretending it is.
> 
> IIUC, the webforum comments that these links point to argue that because
> there is work required outside the blockchain to assemble the toxic
> data, the data in question doesn't *just* reside in the blockchain.  Is
> that right, or do you have another interpretation?
> 
> I don't see how it follows from this particular situation that there
> would be no way to put toxic data in the global append-only ledger that
> Bitcoin depends on.  Do you think that there is some principled reason
> why the blockchain can avoid ingestion of toxic data of any form,
> whether it's (depending on your jurisdiction) CP or "intellectual
> property" or blasphemy or hate speech or …?
> 
> Does your argument for why the bitcoin blockchain is defended against
> this hold for arbitrary global append-only datastructures, or is it
> specific to bitcoin?
> 
> Regards,
> 
>          --dkg