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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
Return-Path: <contact@taoeffect.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 21AF51187
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Feb 2018 21:58:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from homiemail-a4.g.dreamhost.com (homie.mail.dreamhost.com
[208.97.132.208])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 90270FE
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Feb 2018 21:58:12 +0000 (UTC)
Received: from homiemail-a4.g.dreamhost.com (localhost [127.0.0.1])
by homiemail-a4.g.dreamhost.com (Postfix) with ESMTP id 0486951C088;
Wed, 21 Feb 2018 13:58:12 -0800 (PST)
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=Yghn8qy83hGW0NNpU
CZoEIeZgS0=; b=bVb8O1+1gVmDwvwjRb+NyCH4PiE85UKVZS8wsl4SvN3OFBpF+
K8itERNkQ7w91/pKmbs0C8uVXZGB9aYaJUNVTeXJ6AfXIYXLdAOau8Id/THPBleD
+aCvmbUxjgF5M6ZOReXhXUlghnOf2RnVPLpk3QAerhDJHnCz2ex5DznqpQ=
Received: from [10.0.0.144] (unknown [98.204.186.115])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: contact@taoeffect.com)
by homiemail-a4.g.dreamhost.com (Postfix) with ESMTPSA id B8A9951C063;
Wed, 21 Feb 2018 13:58:11 -0800 (PST)
Content-Type: multipart/signed;
boundary="Apple-Mail=_F3627CB4-FDC1-4C41-9AEA-2AC3A9AE40B5";
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: <PSXP216MB0181312DCCA46A1F9A276D799DC80@PSXP216MB0181.KORP216.PROD.OUTLOOK.COM>
Date: Wed, 21 Feb 2018 16:58:10 -0500
X-Mao-Original-Outgoing-Id: 540943090.341135-55307d5b5f278855f291d5862410c2ee
Message-Id: <ED5513F8-9BC3-4FC5-9E32-3F41B862CA64@taoeffect.com>
References: <0899818B-4A48-4A88-8624-B0B6F9536734@taoeffect.com>
<PSXP216MB0181312DCCA46A1F9A276D799DC80@PSXP216MB0181.KORP216.PROD.OUTLOOK.COM>
To: Damian Williamson <willtech@live.com.au>
X-Mailer: Apple Mail (2.3273)
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 22 Feb 2018 04:29:29 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Some thoughts on removing timestamps in PoW
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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, 21 Feb 2018 21:58:13 -0000
--Apple-Mail=_F3627CB4-FDC1-4C41-9AEA-2AC3A9AE40B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> What you are suggesting, unless I am mistaken, is that new full nodes =
should have no way of knowing if an output is spent or even if it =
exists. Since large sections of the blockchain will potentially be =
skipped, the full node will not have complete knowledge of utxo's just =
for starters.
So, this might not have been clear, but by "if we are given the liberty =
of modifying the protocol as we wish" I meant that I was discussing a =
protocol where these sorts of concerns are not an issue because we are =
not limited by the constraints of Bitcoin's current design.
There have been plenty of proposals across the web for how to design a =
blockchain where what you're referring to is not an issue because of =
merkle commitments, etc., and some blockchains already do this (e.g. I =
believe Ethereum does this via parity).
Cheers,
Greg
--
Please do not email me anything that you are not comfortable also =
sharing with the NSA.
> On Feb 19, 2018, at 4:04 AM, Damian Williamson <willtech@live.com.au> =
wrote:
>=20
> >1. Introducing state checkpoints into the chain itself could make it =
possible for full nodes to skip verification of large sections of =
historical data when booting up.
>=20
> What you are suggesting, unless I am mistaken, is that new full nodes =
should have no way of knowing if an output is spent or even if it =
exists. Since large sections of the blockchain will potentially be =
skipped, the full node will not have complete knowledge of utxo's just =
for starters.
>=20
> Regards,
> Damian Williamson
--Apple-Mail=_F3627CB4-FDC1-4C41-9AEA-2AC3A9AE40B5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgYtgnomHliYDCUth7GcgK+kJUkcFAlqN63IACgkQ7GcgK+kJ
UkcG6Q//RWIVMNFwHoL4t0lgbonGnR66+QRXiDSkDBylLhQdk2ao5GMn8fXrBWaE
y4ZhUrbmiKucwvhwk/EebBjzOrtsLtjhWVS1EBS6ukCZwFRG/QMnfD4pNwfizGos
jQci1QVeVddeuX5Xa1rr1W9XCm/2vfmpwnhx/NYxCyamh/hxlXaw6JZG5I1iQpLM
rSBLvb8/gzmUCyCoeAKzNFdApxBKbFAjG+fKqesfmLJQ6v344Iu53ZJ79IlJMsNW
unq7WNyUkSc2c7svQjVSc5cegU5eup0sQ4B2byIYsi7m/uYFZNLS0SbkTySplTHG
76admgZWvVQYnyHJgCV52kYtuc9pkiTgjfeZucHdlC4jFHTZ53r7+rPD/F+ZxbQc
KL/e2eXeTV8gYFZIhmjpHDUc0hMCRWELy6DYMTLLaid5LdYc4ckoOP7sJHr0MO7H
BP2ta1VHzABLk+KqSjVPhzUBbq7c3/IExwZbRnCgjnHmPcPCBZBW4PXr5rlIwuyU
mF5V9DtTA3ihdyQOZQKGcms6kS7Uvmmp0edvs6oLzYWW6c5AQVr0nYaegpPBV3mD
IjMU5QaJFYzVGTfZaPwv6d8IYy56vJ64+Zxi6+VCGY+fRKMTpyJfRaTkNvwduxIV
DxT1pBye+Vwhw5TOZkf5YLNTTEvY543PewIjm2PgntDq1zuFqjo=
=/B/h
-----END PGP SIGNATURE-----
--Apple-Mail=_F3627CB4-FDC1-4C41-9AEA-2AC3A9AE40B5--
|
