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
|
Return-Path: <gubatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 81F0786
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 17:16:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com
[209.85.213.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 22C15EB
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 17:16:30 +0000 (UTC)
Received: by igbjg10 with SMTP id jg10so60832848igb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Aug 2015 10:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=E9t1sMlunN6+NEdjnDFY3WukLqpLfnXRigx0MhJT1Wc=;
b=EElekJYwvTMgOe1thETPeBA+IX3+STTRIAY4UX36pycHSLAFmrlaZ0HL+IeP/WXv8n
x15PHNWJeBbTH2/Eddu7PIzXaIZvh8B1TfANugOq+CfvK2ybh+wbf+lE/pHSzj1BgqqZ
6DlSZ81F3pgDCwFejNd3O0ZE8jT1qzHPSiSo9csacyY8uQPI6TEFZzB5m9R50ciW8MvC
Md//yJpPWxP21XV1LiACoToFhUw0ca2tmBIZbcjinNCzb68QM36Hf3BAHC1XalHK1wzV
ww0qAq/sT9s/zqh2w2UD/8HIaLpcdzz+rckTCH3ERvYV5tiEqBhhdVAr+82G4wsPTxNJ
6LHQ==
X-Received: by 10.50.109.233 with SMTP id hv9mr18533020igb.92.1439831789489;
Mon, 17 Aug 2015 10:16:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.122.144 with HTTP; Mon, 17 Aug 2015 10:16:10 -0700 (PDT)
In-Reply-To: <CADZB0_bgqngwyho4VSrozqz45ahakG6OvqpEHX+_gKMzG6YO2g@mail.gmail.com>
References: <CADr=VrRH2MkvRek5TNidLTuenWGupB07yysh7DgynUghkOyfaA@mail.gmail.com>
<CADZB0_bgqngwyho4VSrozqz45ahakG6OvqpEHX+_gKMzG6YO2g@mail.gmail.com>
From: Angel Leon <gubatron@gmail.com>
Date: Mon, 17 Aug 2015 13:16:10 -0400
Message-ID: <CADZB0_ZH4AiTC=oLgj+6F1X0erB_NhUy5X+CHh7eu7_3Q772ag@mail.gmail.com>
To: Ahmed Zsales <ahmedzsales18@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122e6bc596fc2051d84f669
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,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>
Subject: Re: [bitcoin-dev] BIP [104]: Replace Transaction Fees with Data,
Discussion Draft 0.2.9
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: Mon, 17 Aug 2015 17:16:30 -0000
--089e0122e6bc596fc2051d84f669
Content-Type: text/plain; charset=UTF-8
so you want us to, (i) at the moment of payment decide wether to pay a tx
fee, or to include some data about what the transaction is about...
(ii) and (iii) are out of the question as you'd be forcing people to not
have privacy, which is one of the main reasons people use bitcoin, just
paying like cash.
then the rest goes down hill.
1. You want to add more data to a transaction, which would fill blocks even
faster.
2. The data will be on the blockchain, why in hell would anybody pay the
miners for it when you can just mine it yourself, or pay XYZ online service
to give you the tools you mention, and why would XYZ company pay miners for
the revenues of such service?
because... you want to change the Bitcoin license from MIT to something
else?
I'm sorry. this is dead on arrival, very unrealistic. Perhaps this will
work for some other coin where people accept all these orwellianism from
the start.
If you think there's much debate about blocksize you've no idea how things
would get at the mention of moving away from MIT into some sort of
commercial license, that would indeed destroy Bitcoin from being adopted as
it would enter into many many conflicts that would render it unusable by
lots of organizations.
--089e0122e6bc596fc2051d84f669
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">so you want us to, (i) at the m=
oment of payment decide wether to pay a tx fee, or to include some data abo=
ut what the transaction is about...<br>(ii) and (iii) are out of the questi=
on as you'd be forcing people to not have privacy, which is one of the =
main reasons people use bitcoin, just paying like cash.<br><br>then the res=
t goes down hill.<br><br>1. You want to add more data to a transaction, whi=
ch would fill blocks even faster.</div><div class=3D"gmail_extra"><br>2. Th=
e data will be on the blockchain, why in hell would anybody pay the miners =
for it when you can just mine it yourself, or pay XYZ online service to giv=
e you the tools you mention, and why would XYZ company pay miners for the r=
evenues of such service?<br><br>because... you want to change the Bitcoin l=
icense from MIT to something else?=C2=A0<br><br>I'm sorry. this is dead=
on arrival, very unrealistic. Perhaps this will work for some other coin w=
here people accept all these orwellianism from the start.<br><br>If you thi=
nk there's much debate about blocksize you've no idea how things wo=
uld get at the mention of moving away from MIT into some sort of commercial=
license, that would indeed destroy Bitcoin from being adopted as it would =
enter into many many conflicts that would render it unusable by lots of org=
anizations.<br><br><br><br></div></div>
--089e0122e6bc596fc2051d84f669--
|
