summaryrefslogtreecommitdiff
path: root/e7/d3f9f45a13d3cb1c39f0fd5027b07098001661
blob: 1b40f39231e4f2e6bd96db8b07c45a833a511483 (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
Return-Path: <me@ricmoo.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DF95F8B4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 10 Jul 2015 16:09:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com
	[209.85.213.169])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1B045EE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 10 Jul 2015 16:09:47 +0000 (UTC)
Received: by igrv9 with SMTP id v9so16086184igr.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 10 Jul 2015 09:09:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ricmoo.com; s=google;
	h=from:content-type:subject:message-id:date:to:mime-version;
	bh=UNj5/vRFEMW+7IqxVq2HkTuE3zKthvaXb5gfJnpueR4=;
	b=Ew5/39ihm4mTWbUcOfZ1aAoHulVx4R76DVg0Y69C/piESYLZf5hUywI/KNAjwVPLdl
	0qCuI40wwJsafstOyTpAnQXIW7sZpFVxunbfDxUd/CQGZdSYyaP6L493EIEUIQMRYeUv
	khy0Gl7IM8js2qPkp7vR/DnOFOcU7aEGRm3J8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:from:content-type:subject:message-id:date:to
	:mime-version;
	bh=UNj5/vRFEMW+7IqxVq2HkTuE3zKthvaXb5gfJnpueR4=;
	b=eIjxx3kRLupTCH0Xc4IAcELZlhVVmGX5plUg6r1KFmRzE7xlr3MXYRBWV+AaG5da8B
	630jAkd3GGKs+u1JVGQnM0NS3uKvljAiMc4HnHdCa7WnHbdsaZrSukTz/eVusr+4+USx
	Phtxj/DF/BfOXj8VnLwAVjhRPjaCbFyyksifzWbNlF8IrzQtGqY7ugfdHjQy4R/jvXBS
	7cR2xnceecDx43ZmXuOrpaaP3mmErfycDKa/pbFR3wx+tubsfw2m7KBTfrSCm6hdnSuX
	8F3Ev3qV0PwTJv7oHhk2AvjK7bpNGcufoHxnKwtNp9gNunDigmRJoa4bOiKyIvs8Y5u0
	5HpQ==
X-Gm-Message-State: ALoCoQnL81lXM4c9H9dmisG6T3NsX5teVwiOplogvw5Gplx39rN41tSVqCgIFqqAcIpbDo9XMhTK
X-Received: by 10.107.18.10 with SMTP id a10mr6497175ioj.98.1436544587102;
	Fri, 10 Jul 2015 09:09:47 -0700 (PDT)
Received: from [192.168.2.79] (69-196-189-7.dsl.teksavvy.com. [69.196.189.7])
	by smtp.gmail.com with ESMTPSA id
	191sm3002300iof.18.2015.07.10.09.09.44
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 10 Jul 2015 09:09:45 -0700 (PDT)
From: Richard Moore <me@ricmoo.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DB4351EE-A1B0-4353-9640-142F6388066D"
Message-Id: <6D3AACE5-D6CD-4785-8A55-F6DF0B94D927@ricmoo.com>
Date: Fri, 10 Jul 2015 12:09:43 -0400
To: bitcoin-dev@lists.linuxfoundation.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
X-Mailer: Apple Mail (2.2102)
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,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
Subject: [bitcoin-dev] Why not Child-Pays-For-Parent?
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, 10 Jul 2015 16:09:49 -0000


--Apple-Mail=_DB4351EE-A1B0-4353-9640-142F6388066D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hey guys,

With all the recent congestion and discussion regarding FSS-RBF, I was =
wondering if there good reasons not to have CPFP as a default policy? Or =
is it?

I was also wondering, with CPFP, should the transaction fee be based on =
total transactions size, or the sum of each transaction=E2=80=99s =
required fee? For example, a third transaction C whose unconfirmed utxo =
from transaction B has an unconfirmed utxo in transaction A (all of =
A=E2=80=99s inputs are confirmed), with each A, B and C being ~300bytes, =
should C=E2=80=99s transaction fee be 0.0001 btc for the ~1kb it is =
about to commit to the blockchain, or 0.0003 btc for the 3 transactions =
it is going to commit.

I tried to test it out a few days ago, sending 0.0008 btc without any =
fee, then that utxo into another transaction w/ 0.0001 btc. It still =
hasn=E2=80=99t confirmed, which could be any of: a) CPFP doesn=E2=80=99t =
have enough hash power, b) the amounts are too small, c) the coins are =
too new, d) the fee should have actually been 0.0002 btc, e) the =
congestion is just too great; or some combination.

Just curious as whatnot=E2=80=A6

Thanks,
RicMoo

=
.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=
=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA>

Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes.com <mailto:ricmoo@geneticmistakes.com>
www: http://GeneticMistakes.com <http://geneticmistakes.com/>

--Apple-Mail=_DB4351EE-A1B0-4353-9640-142F6388066D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Hey guys,</div><div class=3D""><br =
class=3D""></div><div class=3D"">With all the recent congestion and =
discussion regarding FSS-RBF, I was wondering if there good reasons not =
to have CPFP as a default policy? Or is it?</div><div class=3D""><br =
class=3D""></div><div class=3D"">I was also wondering, with CPFP, should =
the transaction fee be based on total transactions size, or the sum of =
each transaction=E2=80=99s required fee? For example, a third =
transaction C whose unconfirmed utxo from transaction B has an =
unconfirmed utxo in transaction A (all of A=E2=80=99s inputs are =
confirmed), with each A, B and C being ~300bytes, should C=E2=80=99s =
transaction fee be 0.0001 btc for the ~1kb it is about to commit to the =
blockchain, or 0.0003 btc for the 3 transactions it is going to =
commit.</div><div class=3D""><br class=3D""></div><div class=3D"">I =
tried to test it out a few days ago, sending 0.0008 btc without any fee, =
then that utxo into another transaction w/ 0.0001 btc. It still hasn=E2=80=
=99t confirmed, which could be any of: a) CPFP doesn=E2=80=99t have =
enough hash power, b) the amounts are too small, c) the coins are too =
new, d) the fee should have actually been 0.0002 btc, e) the congestion =
is just too great; or some combination.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Just curious as whatnot=E2=80=A6</div><di=
v class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">RicMoo</div><div class=3D""><br class=3D""></div><div =
apple-content-edited=3D"true" class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  =
">.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=
=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8&gt;&lt;(((=C2=BA&gt;<br =
class=3D""><br class=3D"">Richard Moore ~ Founder<br class=3D"">Genetic =
Mistakes Software inc.<br class=3D"">phone: (778) 882-6125<br =
class=3D"">email:&nbsp;<a href=3D"mailto:ricmoo@geneticmistakes.com" =
class=3D"">ricmoo@geneticmistakes.com</a><br class=3D"">www:&nbsp;<a =
href=3D"http://GeneticMistakes.com/" =
class=3D"">http://GeneticMistakes.com</a></span>
</div>
<br class=3D""></body></html>=

--Apple-Mail=_DB4351EE-A1B0-4353-9640-142F6388066D--