summaryrefslogtreecommitdiff
path: root/04/eaebddc3c787e0a947c76cf516278010facd26
blob: 7ee50cb7b7a26cf3ffb33840b88c688cb76d6a53 (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
Return-Path: <tier.nolan@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B41F37AE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Aug 2015 11:03:38 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com
	[209.85.220.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AB3FB1A3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Aug 2015 11:03:37 +0000 (UTC)
Received: by qkch123 with SMTP id h123so23832071qkc.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 21 Aug 2015 04:03:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:cc
	:content-type; bh=V0WcEbXjuG6Ve5l0vlcxxzdDN1QBF0E6Kj6XEfMczY0=;
	b=MoYOZElT6ydLKYhQE/JX226F2O7ENDcd/iWoURQr12NM5F9OKHA2gSulPXVTZqLQxk
	0SWhS8aJRl+AmqrLwjnB2VmjLmS5IWSt1zDcmwyAxqxEGdfNh7i5cNmhD8mgtbhBywvt
	RXG5gvCmycvRIoKI56pt/cKPs+uQLlFOjzYCSlJdg/NvbJ9n8nzuONbk4HcI8zQCzAir
	Sq2O91QEaHqNy4NZKzd+x0PbL/q/Yik0zbZt+t6JO0igkjWi9bw+GA1D+2ZyPu6Yol/f
	ZCAE8GI9f/i4bViFj39Sz8le/ntE+R/W7ktQWgUNxp36Qe8KcXtZ9rXeJL79mVDCksqc
	mnIQ==
MIME-Version: 1.0
X-Received: by 10.55.15.15 with SMTP id z15mr16099981qkg.47.1440155016841;
	Fri, 21 Aug 2015 04:03:36 -0700 (PDT)
Received: by 10.140.31.181 with HTTP; Fri, 21 Aug 2015 04:03:36 -0700 (PDT)
In-Reply-To: <55D69986.3000307@riseup.net>
References: <CAE-z3OWvA99Z9+wZ0K3XdKGZAV_XkJWYydw+Bo7tr4Oa2jQEWw@mail.gmail.com>
	<55D69986.3000307@riseup.net>
Date: Fri, 21 Aug 2015 12:03:36 +0100
Message-ID: <CAE-z3OWMvphHzSr3qcjUC5XdWGFV-6yCcfFwTdOFnBvvxsiWVg@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11475dda337003051dd03804
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	MALFORMED_FREEMAIL, 
	MISSING_HEADERS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Economic majority vote by splitting coins
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: Fri, 21 Aug 2015 11:03:38 -0000

--001a11475dda337003051dd03804
Content-Type: text/plain; charset=UTF-8

On Fri, Aug 21, 2015 at 4:22 AM, odinn <odinn.cyberguerrilla@riseup.net>
wrote:

> That's interesting.  But in all honesty I don't see most users being
> able to pull off what you are describing.


The idea assumes that it is a BIP + soft fork.  This means that most
wallets would support/recognise the encumbered coins.

Even if only some wallets support it, you can still move your coins
around.  Only the people who are trading between XT and Core would need to
have wallets that support it.

If you consolidate x BTC-Core and x BTC-XT into a single output, then you
can convert it back to a normal output.


> If they are convinced that it is needed its

> use will grow but they won't realize how bad they will be misled until
> later, at which point it will be...
>
> .. Too Late
>

That is the point, this gives a sneak preview.  At minimum, it shows which
choice will give the highest BTC value.

--001a11475dda337003051dd03804
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Fri, Aug 21, 2015 at 4:22 AM, odinn <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:odinn.cyberguerrilla@riseup.net" target=3D"_blank">odinn.cyberguerrilla=
@riseup.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That&#39;s interesting.=C2=A0 But in all honesty I don&#39;t see most users=
 being<br>
able to pull off what you are describing.</blockquote><div><br></div><div>T=
he idea assumes that it is a BIP + soft fork.=C2=A0 This means that most wa=
llets would support/recognise the encumbered coins.<br></div><div><br></div=
><div>Even if only some wallets support it, you can still move your coins a=
round.=C2=A0 Only the people who are trading between XT and Core would need=
 to have wallets that support it.<br><br></div><div>If you consolidate x BT=
C-Core and x BTC-XT into a single output, then you can convert it back to a=
 normal output.<br></div><br><br>&gt; If they are convinced that it is need=
ed its<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
use will grow but they won&#39;t realize how bad they will be misled until<=
br>
later, at which point it will be...<br>
<br>
.. Too Late<br></blockquote><div><br></div><div>That is the point, this giv=
es a sneak preview.=C2=A0 At minimum, it shows which choice will give the h=
ighest BTC value.<br></div></div></div></div>

--001a11475dda337003051dd03804--