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
|
Return-Path: <bitcoin@upalc.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id F230ABDF
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Aug 2015 12:19:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com
[209.85.213.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 66AD6E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Aug 2015 12:19:30 +0000 (UTC)
Received: by igcse8 with SMTP id se8so38246325igc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 26 Aug 2015 05:19:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=3oWrE681WubhTFYL0d9zPAaDuQoSgQGoT9RtCrSqyf4=;
b=fN8026xaShtd3VrfjtcoLLBvUULCvW28qrem6kdIlZtVevXngMtfo9OPeEz1msxV5i
QIfpsZCjseyFwbHAArUQs5zHIdgtOCc72AcSUHT34b2F+JMCFDV0OXaSJkJG2v3995ui
8G3wKNOZSgGjdNqPBwnkUpl1bKNTBxSQq6ZYbg8WDQ0SgVKtWsvQmalTePEn1kstfnAc
uLzx8ilHulVz1ncDMPkKOHt2ee7eWHu3fvOX6JEkTDl4BVDCw2bzWhNRB5wZUiW3nagK
w3fkm8SCpw3y1+yugFxBvIN9/Yo/5C551xWuHotqeEXk3kZG8i15DF3UIsrxE+X9NkCB
qOMQ==
X-Gm-Message-State: ALoCoQm3eAEVOpxwfsI8Py1gJfMd5JDCAGGGIksivCk4bUO/qKvAJeobTAbMntcDT33Y3eAvyc6+
MIME-Version: 1.0
X-Received: by 10.50.79.130 with SMTP id j2mr9719239igx.80.1440591569862; Wed,
26 Aug 2015 05:19:29 -0700 (PDT)
Received: by 10.107.18.155 with HTTP; Wed, 26 Aug 2015 05:19:29 -0700 (PDT)
X-Originating-IP: [115.187.36.147]
In-Reply-To: <CAAO2FKHUL9wSNsSX-BgVfiPU++CjHAwYnFrgu5LGvdS8-hvaSQ@mail.gmail.com>
References: <CAED3CWipF8u5g3LUrqfyHxvEk4Lu+d12ZOJZnoBUw6iZZOg-ZQ@mail.gmail.com>
<CAFzgq-x9GBbqARyhMgfSPc=wYeBgzXy4VUQ0D76GC+TCAxWDuA@mail.gmail.com>
<20150825201643.GC11083@muck> <1489961.GhSFCGzPRJ@crushinator>
<20150825203744.GB3464@muck> <55DCDB98.80004@bitcartel.com>
<CAFzgq-zwkJ2QnnpFsf6X7L00k=+b4s--1POq_=T7j=v-+e1FTg@mail.gmail.com>
<20150826002958.GA10628@muck>
<CAAO2FKHUL9wSNsSX-BgVfiPU++CjHAwYnFrgu5LGvdS8-hvaSQ@mail.gmail.com>
Date: Wed, 26 Aug 2015 17:49:29 +0530
Message-ID: <CAED3CWikGkxFeVT4YYZH9oJxAPE+4kZ6rvZYuwaohqEFkbFfpg@mail.gmail.com>
From: Upal Chakraborty <bitcoin@upalc.com>
To: Hector Chu <hectorchu@gmail.com>
Content-Type: multipart/alternative; boundary=089e0112d074c9fb8f051e35dc13
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>, greg@xiph.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap
[BIP 1xx - Draft]
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 26 Aug 2015 12:19:31 -0000
--089e0112d074c9fb8f051e35dc13
Content-Type: text/plain; charset=UTF-8
Can we please keep this mail chain discussion specific to the proposed
draft -
https://github.com/UpalChakraborty/bips/blob/master/BIP-DynamicMaxBlockSize.mediawiki
?
I understand, voting process is an important subject of discussion. But,
that may be discussed in a separate mail chain.
On Wed, Aug 26, 2015 at 11:58 AM, Hector Chu via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 26 August 2015 at 01:29, Peter Todd via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > For instance, a very simple toy example that would work is just XORing
> your vote with SHA256(the entire blockchain)
>
> Uh, that would totally not work.
>
> I think my proposal of using CLTV to lock coins (votes) is better.
> Failing a soft-fork to implement that in time, counting votes from the
> UTXO set is also ok - the difference between that and CLTV is that it
> is not as strong an evidence of commitment.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--089e0112d074c9fb8f051e35dc13
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Can we please keep this mail chain discussion specific to =
the proposed draft -=C2=A0<a href=3D"https://github.com/UpalChakraborty/bip=
s/blob/master/BIP-DynamicMaxBlockSize.mediawiki">https://github.com/UpalCha=
kraborty/bips/blob/master/BIP-DynamicMaxBlockSize.mediawiki</a> ?<div><br><=
/div><div>I understand, voting process is an important subject of discussio=
n. But, that may be discussed in a separate mail chain.</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Aug 26, 2015 at 1=
1:58 AM, Hector Chu via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto=
:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists=
.linuxfoundation.org</a>></span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">On 26 August 2015 at 01:29, Peter Todd via bitcoin-dev<br>
<span class=3D""><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.or=
g">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br>
> For instance, a very simple toy example that would work is just XORing=
your vote with SHA256(the entire blockchain)<br>
<br>
</span>Uh, that would totally not work.<br>
<br>
I think my proposal of using CLTV to lock coins (votes) is better.<br>
Failing a soft-fork to implement that in time, counting votes from the<br>
UTXO set is also ok - the difference between that and CLTV is that it<br>
is not as strong an evidence of commitment.<br>
<div class=3D"HOEnZb"><div class=3D"h5">___________________________________=
____________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>
--089e0112d074c9fb8f051e35dc13--
|
