summaryrefslogtreecommitdiff
path: root/02/68247fb739d8e8231d827dcf7687c8ca6d10e9
blob: b040bb745c514ab0171768b22a481c8a04b39c69 (plain)
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
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
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 0E17E12FE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 19 Feb 2018 05:16:02 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from homiemail-a1.g.dreamhost.com (homie.mail.dreamhost.com
	[208.97.132.208])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 725CBE4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 19 Feb 2018 05:16:01 +0000 (UTC)
Received: from homiemail-a1.g.dreamhost.com (localhost [127.0.0.1])
	by homiemail-a1.g.dreamhost.com (Postfix) with ESMTP id 05FAC34806C;
	Sun, 18 Feb 2018 21:16:01 -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=WThWBKimFDeIuwH9K
	gAX1e+pBKo=; b=ZtCHkZeUAWPQgN0GJnB695P18fqsjmcKKEn+WpEIXjb45Bcno
	9SzNi0MloJmcSPlOdf+twJnHeOsqOBIp0n9H9Bn/+yKT11MdTlCOzAJuaX5//MMf
	q3nVO8JM4CQAkkFkVw2Wty4fHd0PETMUnqe+s+nAfE/TBfsiCNc1lq23ZU=
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-a1.g.dreamhost.com (Postfix) with ESMTPSA id 83C37348062; 
	Sun, 18 Feb 2018 21:16:00 -0800 (PST)
Content-Type: multipart/signed;
	boundary="Apple-Mail=_505D80AF-E6D2-4F53-A01B-4D1539F4B64E";
	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: <ebe9b337-e646-4d0f-b52e-d1b5d2f753f5@email.android.com>
Date: Mon, 19 Feb 2018 00:15:59 -0500
X-Mao-Original-Outgoing-Id: 540710159.0785871-90e8179c80f44f6de09078ed06ba0151
Message-Id: <28E7F3BA-3D0E-4FF2-9143-FD79A0A029F5@taoeffect.com>
References: <ebe9b337-e646-4d0f-b52e-d1b5d2f753f5@email.android.com>
To: Ryan J Martin <rjmarti2@millersville.edu>
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, HTML_MESSAGE,
	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: Mon, 19 Feb 2018 05:33:14 +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: Mon, 19 Feb 2018 05:16:02 -0000


--Apple-Mail=_505D80AF-E6D2-4F53-A01B-4D1539F4B64E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_CDAD6EA8-5E4B-44DE-9489-FD5104334091"


--Apple-Mail=_CDAD6EA8-5E4B-44DE-9489-FD5104334091
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Real quick (I've received some off-list replies and do plan to respond =
to those), want to be clear: this thread is not meant to be interpreted =
as a proposal to modify Bitcoin (it is not a BIP), it is just, exactly =
as the subject says, some thoughts I had that I hadn't seen expressed =
elsewhere, that I felt like sharing, in case they are at all =
useful/interesting to anyone.

Cheers,
Greg

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

> On Feb 19, 2018, at 12:10 AM, Ryan J Martin <rjmarti2@millersville.edu =
<mailto:rjmarti2@millersville.edu>> wrote:
>=20
> To be frank, this kind of thing would be better off attempted as a =
fork to a new coin. Changing the max number of coins, the block reward, =
the difficulty algo, mining policy and protocol is going to be a =
non-starter. Also, what are the proposed quantifiavle benefits from =
removing timestamps? How would this be done at the protocol level? Are =
these other changes related to removing timestamps/rationale for other =
supply changes?
>=20
> Regards,
> Ryan J. Martin
>=20


--Apple-Mail=_CDAD6EA8-5E4B-44DE-9489-FD5104334091
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><meta http-equiv=3D"Content-Type" content=3D"text/html=
 charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Real quick (I've received some off-list replies and do plan =
to respond to those), want to be clear: this thread is not meant to be =
interpreted as a proposal to modify Bitcoin (it is not a BIP), it is =
just, exactly as the subject says, some thoughts I had that I hadn't =
seen expressed elsewhere, that I felt like sharing, in case they are at =
all useful/interesting to anyone.<div class=3D""><br class=3D""></div><div=
 class=3D"">Cheers,</div><div class=3D"">Greg<br class=3D""><div =
class=3D"">
<span style=3D"color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; font-variant-ligatures: normal; =
font-variant-position: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal; orphans: 2; widows: 2;" class=3D""><br =
class=3D"Apple-interchange-newline">--</span><br style=3D"color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D""><span style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">Please do not email me anything that you are not =
comfortable also sharing</span><span style=3D"color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
font-variant-ligatures: normal; font-variant-position: normal; =
font-variant-numeric: normal; font-variant-alternates: normal; =
font-variant-east-asian: normal; line-height: normal; orphans: 2; =
widows: 2;" class=3D"">&nbsp;with the NSA.</span>
</div>
<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Feb 19, 2018, at 12:10 AM, Ryan J Martin &lt;<a =
href=3D"mailto:rjmarti2@millersville.edu" =
class=3D"">rjmarti2@millersville.edu</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D"">

<div class=3D"">
<div dir=3D"auto" class=3D"">
<div class=3D"">To be frank, this kind of thing would be better off =
attempted as a fork to a new coin. Changing the max number of coins, the =
block reward, the difficulty algo, mining policy and protocol is going =
to be a non-starter. Also, what are the proposed quantifiavle
 benefits from removing timestamps? How would this be done at the =
protocol level? Are these other changes related to removing =
timestamps/rationale for other supply changes?</div>
<div dir=3D"auto" class=3D""><br class=3D"">
</div>
<div dir=3D"auto" class=3D"">Regards,</div>
<div dir=3D"auto" class=3D"">Ryan J. Martin<br class=3D"">
<div class=3D"gmail_extra" dir=3D"auto"><br class=3D"">
</div>
</div></div></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_CDAD6EA8-5E4B-44DE-9489-FD5104334091--

--Apple-Mail=_505D80AF-E6D2-4F53-A01B-4D1539F4B64E
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+kJUkcFAlqKXY8ACgkQ7GcgK+kJ
UkeAoQ/+LVkuEbJy2h60/KTZhbLR/mM2T78EbRXBfVr1D6iNosOmuPKc3B5teOTx
ehSKGebvXXUQg8W4qASLxMohsBCuFh11JEvoPhKlpGUcxcpd18fFuLyvmeBj/2HX
vL0u073tcE/QNQGSTqkEFvnu0g28huGsvhA8zoeEPH5euhzrgTPoZkqe1hiZEks1
1PV3VR0rrXRChJ2pRnGVCNFn9oIqwWBkNjPyKya0mZqcuRuDeCeQ1/5El+qgM15Q
gBva3k9P7sEcVVYF6Uzc9MxrqcnIaoNiugah1I55XMHVnrxUBwjRCY2vjZld0Pe2
bNXT2O8scFk5ZnPR6gyx9v5ACnpMgbWCjWd8JCHllSsSr6JAR3Ydq03RUGD64QaR
JGyrU44MHYbA0jD6RsjTG7StReHVu6+Jlp31nCPBkgsvGylmNu2/1fpIzNrkNsRi
2usdLmCvsIczGqy1SxQqkovqm6LO0BboTAbkzok6Woarl+c6z1iYTOwnec7cAt9R
NfFIvwUpmhTX3I7zyKGCbj7coDs8qblyz9s+J2AuFViSHc0n4SCuk+1RuwM56lAJ
O/fzodBIsTwe7ZZDqqeinwtecO4Jv8Xa+aCULegpc/F13+34iGv+K8C0PQcC1MBr
GAErOQtdhzVzJJDao7w5YU4lD9aKm9achFkzq6kAPPk1q6foH/c=
=fTV4
-----END PGP SIGNATURE-----

--Apple-Mail=_505D80AF-E6D2-4F53-A01B-4D1539F4B64E--