path: root/12/0057de6358b4e8e465e5056ff9e0e46283f177

Return-Path: <willtech@live.com.au>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 54DF4C12
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 24 Dec 2017 22:20:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from APC01-SG2-obe.outbound.protection.outlook.com
	(mail-oln040092253048.outbound.protection.outlook.com [40.92.253.48])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B723E403
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 24 Dec 2017 22:20:53 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1; 
	h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
	bh=3i1GxLWr2NIa2EL04tjCT4IpCVVBeFmIlSgD3PZNv9I=;
	b=uz+G7EZGV06Dwij04bBRXB1NMl6sVTj0P4yf4DaH/pNqq3W6t5JpbxIO37Fz0Mkv5rutLx2lGuSco1NxBqjQA5ttzITQtH8UzfIpKAPsdZVknvXyood90+GnuHcbCR+PM2IPQV589+ilj2QsSPALj8/KuE6SPztW+apsBJ3uwkxWgwGRQ8vzPd4yNJjoaFp+ejCq1LM6+wiIo90ZG08L1fHvB37OzxsVjUkQmPdGYHuzzTY3wb61XF6scUPLEnL8xd3w9jeSURSQ2XgvKOA7DkCH2LD1K2csWuqvSLC25+VrwojP17mc0UV4g3l0RhJbcGPjUwRorCv86tSje2sA9w==
Received: from SG2APC01FT056.eop-APC01.prod.protection.outlook.com
	(10.152.250.60) by SG2APC01HT100.eop-APC01.prod.protection.outlook.com
	(10.152.251.20) with Microsoft SMTP Server (version=TLS1_2,
	cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.302.6;
	Sun, 24 Dec 2017 22:20:51 +0000
Received: from PS2P216MB0179.KORP216.PROD.OUTLOOK.COM (10.152.250.51) by
	SG2APC01FT056.mail.protection.outlook.com (10.152.251.13) with
	Microsoft SMTP Server (version=TLS1_2,
	cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
	15.20.302.6 via Frontend Transport; Sun, 24 Dec 2017 22:20:50 +0000
Received: from PS2P216MB0179.KORP216.PROD.OUTLOOK.COM ([10.171.225.19]) by
	PS2P216MB0179.KORP216.PROD.OUTLOOK.COM ([10.171.225.19]) with mapi id
	15.20.0345.016; Sun, 24 Dec 2017 22:20:50 +0000
From: Damian Williamson <willtech@live.com.au>
To: Luke Dashjr <luke@dashjr.org>
Thread-Topic: [bitcoin-dev] BIP 177: UTPFOTIB - Use Transaction Priority For
	Ordering Transactions In Blocks
Thread-Index: AQHTfF9LLKeRKL7NBU+Lvna4nlU7zKNSFt0AgAD4daY=
Date: Sun, 24 Dec 2017 22:20:50 +0000
Message-ID: <PS2P216MB01796F03E182D783210DFF2B9D000@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>
References: <PS2P216MB0179FE1CAF04AB860A5F36719D000@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>,
	<201712240721.24971.luke@dashjr.org>
In-Reply-To: <201712240721.24971.luke@dashjr.org>
Accept-Language: en-AU, en-US
Content-Language: en-AU
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:BF65E41D3F2D315C371CCB04C6E1996325A67F5E72A157AF1F663CE7EFCCD1AE;
	UpperCasedChecksum:08E7176659C9C06776080AA24B74019F0F8687AC303FB6E34F26EC792B3E397C;
	SizeAsReceived:7213; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [AnN6URr9o11xqA91ZhLh8+RTaFMm3Jgi]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT100;
	6:dQXvF+XuVBXqLYrZnIJ0HN8Yei2lYvdDMlDZT2mhYG3fqnaErkwkIJX6yWuG6HYoRlJgQurvONldaSyHkJCYrL4lnIDsfaLghk2RXPfZZcJmYkhsbkOC4ZJngb5lelG/KfS1TYxfmxVkAvKc8zkjSAWurlAMbhzasK5XchhUEzvWnhbol6g1qtM/jt35u+Z3+nVr8l7tiTzRzXK3h466xonsRk3nLIb/lmJWoTCA+8ABCvyTBlrOE8dv4J2MzslJySFWQJ3PLbssyi1hKeCWOrMp3eHJzpV2apmSKoW1eFOsiR6OM24EZB69uGZ6WFnPga586P25x5PsVNDiZUb5Pc8u7H5w7QjZhlmruqqLIsI=;
	5:WdVu2Ho+HdJ8T9poLvCG7V14rKl5CSoWyYgDYhrhmrgHrq8+3hdG5Nsy7GgKlu/EiJ3NvvnwHfJv+gSunp0rTjIfwxZx5ldwR1tg/LNIasaVgTbTsL+dddxwlMIx4gdb4Q48IMmlhgpOsHeavWD2GzwoTthVJ6DBpvWx9NGFcEs=;
	24:C9fPyn2b1X1z6Xwnb/ZjwaM05vMJ4Sl8YOLliLadUZRE3NuCbJUmUtFoBr+PGdbp7FQnUZ5GcGbGtFW3To57CNeqwYmkyM40wV5DH+LiGUc=;
	7:M/bJrCMGacw7iKeW3SCWY6vAxxTM6zN07Pa6RoXBn2zvV+sPHHrMSRVxVaC4x/JTwypDFlV7TUGIlFUYroPo4p7V1x/zy8CaqZVy2qQ5yW38m/3mgTGKUlRUMWIYzyTnmLYAhjt9iMH5zT8BXJdRK4nEo1nb9JBhgKnmRVlSBneswec84pxRqql5FneQAXpqWFdPsEKfU4V8mzyna987DFn7H/Z3/6O2jQKa+SH5z+/a490UB0p+YbE1jc87YEUh
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0;
	RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045);
	SRVR:SG2APC01HT100; 
x-ms-traffictypediagnostic: SG2APC01HT100:
x-ms-office365-filtering-correlation-id: fc36570b-b2d0-4cab-dede-08d54b1c9714
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031);
	SRVR:SG2APC01HT100; BCL:0; PCL:0;
	RULEID:(100000803101)(100110400095); SRVR:SG2APC01HT100; 
x-forefront-prvs: 05315CBE52
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT;
	SFP:1901; SCL:1; SRVR:SG2APC01HT100;
	H:PS2P216MB0179.KORP216.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_PS2P216MB01796F03E182D783210DFF2B9D000PS2P216MB0179KORP_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fc36570b-b2d0-4cab-dede-08d54b1c9714
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Dec 2017 22:20:50.8219 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT100
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, HTML_MESSAGE, RCVD_IN_DNSWL_NONE,
	T_REMOTE_IMAGE 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: Sun, 24 Dec 2017 22:39:39 +0000
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 177: UTPFOTIB - Use Transaction Priority For
 Ordering Transactions In Blocks
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: Sun, 24 Dec 2017 22:20:55 -0000

--_000_PS2P216MB01796F03E182D783210DFF2B9D000PS2P216MB0179KORP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

My mistake, apologies all.


 - I honestly thought everyone just took the next available number and publ=
ished up their BIP's.


And, I see you have something of a master list.


As a suggestion, would it be worth considering linking to some of that info=
rmation in the list welcome email? Web search is not always your friend for=
 locating everything relevant.


Regards,

Damian Williamson

________________________________
From: Luke Dashjr <luke@dashjr.org>
Sent: Sunday, 24 December 2017 6:21:24 PM
To: Damian Williamson
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 177: UTPFOTIB - Use Transaction Priority For=
 Ordering Transactions In Blocks

BIP 177 is NOT assigned. Do not self-assign BIP numbers!

Please read BIP 2:

    https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki
[https://avatars0.githubusercontent.com/u/528860?s=3D400&v=3D4]<https://git=
hub.com/bitcoin/bips/blob/master/bip-0002.mediawiki>

bips/bip-0002.mediawiki at master =B7 bitcoin/bips =B7 GitHub<https://githu=
b.com/bitcoin/bips/blob/master/bip-0002.mediawiki>
github.com
Abstract. A Bitcoin Improvement Proposal (BIP) is a design document providi=
ng information to the Bitcoin community, or describing a new feature for Bi=
tcoin or its ...



Luke


On Sunday 24 December 2017 2:57:38 AM Damian Williamson via bitcoin-dev wro=
te:
> BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transactions In
> Blocks
>
>
> This BIP proposes to address the issue of transactional reliability in
> Bitcoin, where valid transactions may be stuck in the mempool for extende=
d
> periods.
>
>
> There are two key issues to be resolved:
>
>
>   1.  The current transaction bandwidth limit.
>   2.  The current ad-hoc methods of including transactions in blocks
> resulting in variable and confusing confirmation times for valid
> transactions, including transactions with a valid fee that may never
> confirm.
>
>
> It is important with any change to protect the value of fees as these wil=
l
> eventually be the only payment that miners receive. Rather than an auctio=
n
> model for limited bandwidth, the proposal results in a stable fee for
> priority service auction model.
>
>
> I will post the full proposal up on to my blog in the coming days and,
> re-review incorporating feedback that I have received on and off thread.
> It would not be true to suggest that all feedback received has been
> entirely positive although, most of it has been constructive.
>
>
> The previous threads for this BIP are available here:
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-December/sub=
je
> ct.html
>
>
> Regards,
>
> Damian Williamson

--_000_PS2P216MB01796F03E182D783210DFF2B9D000PS2P216MB0179KORP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size: 12pt; color: rgb(0, 0,=
 0); font-family: Calibri,Helvetica,sans-serif,&quot;EmojiFont&quot;,&quot;=
Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,NotoColorEmoji,&quot;Seg=
oe UI Symbol&quot;,&quot;Android Emoji&quot;,EmojiSymbols;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">My mistake, apologies all.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">&nbsp;- I honestly thought everyo=
ne just took the next available number and published up their BIP's.<br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">And, I see you have something of =
a master list.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">As a suggestion, would it be wort=
h considering linking to some of that information in the list welcome email=
? Web search is not always your friend for locating everything relevant.<br=
>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Regards,</p>
<p style=3D"margin-top:0;margin-bottom:0">Damian Williamson<br>
</p>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=
=3D"Calibri, sans-serif" color=3D"#000000"><b>From:</b> Luke Dashjr &lt;luk=
e@dashjr.org&gt;<br>
<b>Sent:</b> Sunday, 24 December 2017 6:21:24 PM<br>
<b>To:</b> Damian Williamson<br>
<b>Cc:</b> bitcoin-dev@lists.linuxfoundation.org<br>
<b>Subject:</b> Re: [bitcoin-dev] BIP 177: UTPFOTIB - Use Transaction Prior=
ity For Ordering Transactions In Blocks</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">BIP 177 is NOT assigned. Do not self-assign BIP nu=
mbers!<br>
<br>
Please read BIP 2:<br>
<br>
&nbsp;&nbsp;&nbsp; <a href=3D"https://github.com/bitcoin/bips/blob/master/b=
ip-0002.mediawiki" id=3D"LPlnk199482" previewremoved=3D"true">
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki</a>
<div id=3D"LPBorder_GT_15141539054680.8912396028017598" style=3D"margin-bot=
tom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_15141539053620.3937609874043665" style=3D"width: 9=
0%; background-color: rgb(255, 255, 255); position: relative; overflow: aut=
o; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1=
px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);=
" role=3D"presentation" cellspacing=3D"0">
<tbody>
<tr style=3D"border-spacing: 0px;" valign=3D"top">
<td id=3D"ImageCell_15141539054030.7786038054997373" style=3D"width: 250px;=
 position: relative; display: table-cell; padding-right: 20px;" colspan=3D"=
1">
<div id=3D"LPImageContainer_15141539054030.8026208121041042" style=3D"backg=
round-color: rgb(255, 255, 255); height: 128px; position: relative; margin:=
 auto; display: table; width: 128px;">
<a id=3D"LPImageAnchor_15141539054070.17383274856900854" style=3D"display: =
table-cell; text-align: center;" href=3D"https://github.com/bitcoin/bips/bl=
ob/master/bip-0002.mediawiki" target=3D"_blank"><img style=3D"display: inli=
ne-block; max-width: 250px; max-height: 250px; height: 128px; width: 128px;=
 border-width: 0px; vertical-align: bottom;" id=3D"LPThumbnailImageID_15141=
539054560.03602560223838969" width=3D"128" height=3D"128" src=3D"https://av=
atars0.githubusercontent.com/u/528860?s=3D400&amp;v=3D4"></a></div>
</td>
<td id=3D"TextCell_15141539054570.011331160021723963" style=3D"vertical-ali=
gn: top; position: relative; padding: 0px; display: table-cell;" colspan=3D=
"2">
<div id=3D"LPRemovePreviewContainer_15141539054570.32915195597786506"></div=
>
<div id=3D"LPExpandDescriptionContainer_15141539054570.049425410303045925">=
</div>
<div id=3D"LPTitle_15141539054570.9544129657029455" style=3D"top: 0px; colo=
r: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: &quot;=
wf_segoe-ui_light&quot;,&quot;Segoe UI Light&quot;,&quot;Segoe WP Light&quo=
t;,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,Arial,sans-serif; line-=
height: 21px;">
<a id=3D"LPUrlAnchor_15141539054590.2989105084593132" style=3D"text-decorat=
ion: none;" href=3D"https://github.com/bitcoin/bips/blob/master/bip-0002.me=
diawiki" target=3D"_blank">bips/bip-0002.mediawiki at master =B7 bitcoin/bi=
ps =B7 GitHub</a></div>
<div id=3D"LPMetadata_15141539054590.8288299873258512" style=3D"margin: 10p=
x 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: &quot=
;wf_segoe-ui_normal&quot;,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,=
Arial,sans-serif; font-size: 14px; line-height: 14px;">
github.com</div>
<div id=3D"LPDescription_15141539054600.6108515341861528" style=3D"display:=
 block; color: rgb(102, 102, 102); font-weight: 400; font-family: &quot;wf_=
segoe-ui_normal&quot;,&quot;Segoe UI&quot;,&quot;Segoe WP&quot;,Tahoma,Aria=
l,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overfl=
ow: hidden;" altdesc=3D"We intend BIPs to be the primary mechanisms for pro=
posing new features, for collecting community input on an issue, and for do=
cumenting the design decisions that have gone into Bitcoin. The BIP author =
is responsible for building consensus within the community and documenting =
dissenting opinions.&lt;br/&gt;&lt;br/&gt;The BIP process begins with a new=
 idea for Bitcoin. Each potential BIP must have a champion -- someone who w=
rites the BIP using the style and format described below, shepherds the dis=
cussions in the appropriate forums, and attempts to build community consens=
us around the idea.&lt;br/&gt;&lt;br/&gt;The Layer header (only for Standar=
ds Track BIPs) documents which layer of Bitcoin the BIP applies to. See BIP=
 123 for definitions of the various BIP layers. Activation of this BIP impl=
ies activation of BIP 123. =0A=
The Author header lists the names and email addresses of all the authors/ow=
ners of the BIP.">
Abstract. A Bitcoin Improvement Proposal (BIP) is a design document providi=
ng information to the Bitcoin community, or describing a new feature for Bi=
tcoin or its ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
Luke<br>
<br>
<br>
On Sunday 24 December 2017 2:57:38 AM Damian Williamson via bitcoin-dev wro=
te:<br>
&gt; BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transactions=
 In<br>
&gt; Blocks<br>
&gt; <br>
&gt; <br>
&gt; This BIP proposes to address the issue of transactional reliability in=
<br>
&gt; Bitcoin, where valid transactions may be stuck in the mempool for exte=
nded<br>
&gt; periods.<br>
&gt; <br>
&gt; <br>
&gt; There are two key issues to be resolved:<br>
&gt; <br>
&gt; <br>
&gt;&nbsp;&nbsp; 1.&nbsp; The current transaction bandwidth limit.<br>
&gt;&nbsp;&nbsp; 2.&nbsp; The current ad-hoc methods of including transacti=
ons in blocks<br>
&gt; resulting in variable and confusing confirmation times for valid<br>
&gt; transactions, including transactions with a valid fee that may never<b=
r>
&gt; confirm.<br>
&gt; <br>
&gt; <br>
&gt; It is important with any change to protect the value of fees as these =
will<br>
&gt; eventually be the only payment that miners receive. Rather than an auc=
tion<br>
&gt; model for limited bandwidth, the proposal results in a stable fee for<=
br>
&gt; priority service auction model.<br>
&gt; <br>
&gt; <br>
&gt; I will post the full proposal up on to my blog in the coming days and,=
<br>
&gt; re-review incorporating feedback that I have received on and off threa=
d.<br>
&gt; It would not be true to suggest that all feedback received has been<br=
>
&gt; entirely positive although, most of it has been constructive.<br>
&gt; <br>
&gt; <br>
&gt; The previous threads for this BIP are available here:<br>
&gt; <br>
&gt; <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/201=
7-December/subje" id=3D"LPlnk943321" previewremoved=3D"true">
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-December/subje=
</a><br>
&gt; ct.html<br>
&gt; <br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Damian Williamson<br>
</div>
</span></font></div>
</div>
</body>
</html>

--_000_PS2P216MB01796F03E182D783210DFF2B9D000PS2P216MB0179KORP_--