1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Return-Path: <gmkarl@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 0EB20C0032
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2022 01:21:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id ED362416F7
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2022 01:21:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.157
X-Spam-Level:
X-Spam-Status: No, score=0.157 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
MALFORMED_FREEMAIL=1.235, MISSING_HEADERS=1.021,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=no autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 3Yy7EqgAZDGM
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2022 01:21:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com
[IPv6:2607:f8b0:4864:20::1131])
by smtp4.osuosl.org (Postfix) with ESMTPS id 371384151E
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2022 01:21:32 +0000 (UTC)
Received: by mail-yw1-x1131.google.com with SMTP id
00721157ae682-30c2f288f13so46796077b3.7
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Jun 2022 18:21:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:in-reply-to:references:from:date:message-id:subject:cc;
bh=KJxlF6LUXzJhguWoNEmEhyztM59kTnVD82uM393vAFg=;
b=E6hK+00mCUQLp64VDKeLY/pQDz0siBaoSupcwjZvxyiSxEU9YkkGpjpx2sSt++x+E8
5CfVKM8btjaxvRIzc31UUyiG1qLdlqeqGAyhL8NRHMCF7v3Djz862YNdzYTGDKfRJc0h
rlHNcaRH/rybc+3wDTiaa/VHfSlRv4q+oiYTGjbDsCqy8+U1ms3Q2nbH932BChrk/QIu
hYYMYy1lNOv1ISLroBMxY0n77mIZK27eL6xYY1qXNjTJBlwwKeVEcdN0IzyNogEtkB/0
hXZyorn/Gy/6DhO5xjKOcTMI49S3AETpA1XTELNZv/01NIYZoffiuVRs0e39rQEkneWK
4QyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:cc;
bh=KJxlF6LUXzJhguWoNEmEhyztM59kTnVD82uM393vAFg=;
b=gXm/KOGInFv1xi26G0jOKmLA0IL3cxSxJuTcW62Gj6g263Qalq4HMmcMbd7z+y1otZ
q6CYGQfAv+rYnzualH+R1beA7cbJp6LshrqLa9a9H+y/RQtHwmYENC1tS9+RWbrWQ/9r
AqSUepCG1m6qlghF9UMwgLihN7h+HD7oai1VADgXIAGgirHPMYWbr27Vglk6tZtaBAhb
KytaZxQYk7PmwG6P4OyOkllmprPf7h0bi64lQ8212j4Ik9Ub5wnySvOGpT9RnxJS9Eh7
0SBosMpLzxyMLyA3/3HG4f2pM1HZC8saEeidU79RLncZoK1Xm5ENeW4Tg7r1jF62SLJ1
uItg==
X-Gm-Message-State: AJIora+wX95rHy8+e7iTt4pfRLoyHPBr0oLtPXlnAhWiO071luXxKP4B
PFRjBggbgjetrhk1oi8tA6nP/723xfux6pF4mOcGWmXt3W0=
X-Google-Smtp-Source: AGRyM1vhyq3MF8oO/kXQKL+cPXQXOBMff3jlW4rPynCz2Odp/qT4fUuuhZmkoM7MVsJCOLevZP+TcUpsFRDINRCTjIA=
X-Received: by 2002:a81:91c3:0:b0:30c:cdd5:8fb8 with SMTP id
i186-20020a8191c3000000b0030ccdd58fb8mr8744260ywg.205.1655256090503; Tue, 14
Jun 2022 18:21:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a05:7000:dd05:0:0:0:0 with HTTP; Tue, 14 Jun 2022 18:21:29
-0700 (PDT)
In-Reply-To: <CALL-=e787U7BnBKdscQrEg51T4uycPwrFa3FdPuHs5UfPxuZKw@mail.gmail.com>
References: <CAD5xwhgGgq30C7GniNh1_DobPe+P4NTJySUkDiBZBj=OjzO5KA@mail.gmail.com>
<YmqFRlDIkfbyVIZ2@petertodd.org>
<CAD5xwhhB+8n+9pWiSCtx3DAPnSwV_7xHnXZ14mEj9H93eWUNEw@mail.gmail.com>
<YqhtDoN784GG4Cx8@petertodd.org>
<CALL-=e6ucj0RxM6=Lyrytb3MzQA2pOMwQqM_Gr9RDg3+5Lbudw@mail.gmail.com>
<CALL-=e4=t7YMxDsBrDvR0Bkhagn+x2XnzZMYuoA4C=VXp=R2KA@mail.gmail.com>
<dy-RmZZGZlQCDyQ_YVeIBIgX4uDW4cfeVpcX5eyugsYoPNZqqjMKs3qoOX_ZidcCBU_3UTytRJMl08TbWQZ363T_E_WQVx_eYJWLzZWUyE8=@protonmail.com>
<CALL-=e4xA_SVfZp=nLgWRRPon3-6Ke0TE2J0qQrNFGQd7FOsqA@mail.gmail.com>
<YqiqjPternXI1AZ6@petertodd.org>
<CALL-=e4=p9oQvAxm-dWTNwPOYb5D2kwdLjCtePpCnwNnL9bNVQ@mail.gmail.com>
<YqjwfUcgEMNpGV1U@camus>
<CALL-=e787U7BnBKdscQrEg51T4uycPwrFa3FdPuHs5UfPxuZKw@mail.gmail.com>
From: "Undiscussed Horrific Abuse, One Victim of Many" <gmkarl@gmail.com>
Date: Tue, 14 Jun 2022 21:21:29 -0400
Message-ID: <CALL-=e5uj9oiitvL_WYeSEPW4n5hKrGp-h6TjPAKqE+36kT=TA@mail.gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailman-Approved-At: Wed, 15 Jun 2022 08:06:32 +0000
Subject: Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its
transactions
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2022 01:21:33 -0000
> I do reiterate that it is blindingly easy to pin a public hash to the
> bitcoin blockchain that asserts the earliest publication of a document
> or collection of documents, and that this is desperately needed, to
> protect the accuracy of history when it is not safe.
The concern raised here relates to scaling, and here we disagree on
the proper direction of Bitcoin. To me it seems clear that Bitcoin was
designed to scale better than it has. It honestly looks like
developers are arbitrarily avoiding storing much data on chain, with
quickly shoehorned solutions like the lightning protocol. Bitcoin
simply got big too fast. I believe it was intended to handle large
data smoothly: not with single gigabyte blocks that every user must
store, but with simplistically designed and well-backed decentralised
propagation and storage of data. I see that not having happened due to
mostly political issues, and that's unfortunate, but other chains have
made strides here.
I don't think satoshi was familiar with how people behave when they
have a lot of money.
|
