Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of coinlab.com
	designates 209.85.213.47 as permitted sender)
	client-ip=209.85.213.47; envelope-from=peter@coinlab.com;
	helo=mail-yw0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <201205291447.29823.luke@dashjr.org>
References: <CA+8xBpdBe4yR6xkCODL6JQ41Gyx9eWcGGGvcQVt7DCmaEnAhbg@mail.gmail.com>
	<CAMGNxUv3jX+bdEyF8p-y3i93yLySxyT=7Qy336dPw9vgDKG51w@mail.gmail.com>
	<5C824F0D-6025-4630-965B-E6C685588250@mac.com>
	<201205291447.29823.luke@dashjr.org>
From: Peter Vessenes <peter@coinlab.com>
Date: Tue, 29 May 2012 11:05:18 -0400
Message-ID: <CAMGNxUs9KBDE7T4YgX+NH3j=VURffLjOEih8nEODohUeyn1=Vw@mail.gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=047d7b2ee639e544ca04c12e2a26
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Punishing empty blocks?
Precedence: list

--047d7b2ee639e544ca04c12e2a26
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

OK, I have a few thoughts on this:

1) Germane to the original conversation, anything hard to implement will
not get implemented by miners.
2) Coinbase is hard-limited to 100 bytes; this has to include space for
voting as well as extra nonce, etc. So, I'm not sure that a full URL is a
good plan.
3) I'm a little fuzzy on the details of BIP governance; but I'm happy to
write one up and get my thoughts down, or someone who's more familiar could
do it, I suppose.

I propose the following spec:

periodically a miner may choose to publish a url through their coinbase as
follows:

1) They shall prepend \mi: to the url to designate it as a url for miner
info, and append a trailing \ to the url
2) The url given in the coinbase shall have http:// prepended to it before
processing.
3) The destination may be a redirect (to allow short URLs), or may deliver
content
4) The content-type returned by the final site post-redirect shall be
either (preferred text/json) or text/plain or text/html
4) The text of the document delivered shall be a JSON format dictionary,
and shall include at minimum the following fields: 'min_fee', 'pool_name',
and 'last_modified' Optional fields can be determined over time as
necessary by the mining community
5) The Service Level Agreement isn't binding, but miners who implement it
are expected to make a best efforts attempt to follow it.

So a valid coinbase could be:
/P2SH/\mi:goo.gl/mr2D\extra_nonce:2110

Generally a miner would occasionally publish the \mi:\ when they had
updated their SLA, or just every so often, but the canonical location would
be the final destination URL from the redirects.

Inre: Luke's complaint about JSON, it is the language of the web. There is
no easier format for both computers and humans to read, and in this case,
it includes extensibility, which is nice, since we have no idea how miners
will wish to divvy up their services; I think one would need to make a
strong case against JSON for a specific reason to not choose it by default.

Thoughts welcome!

Best,

Peter


On Tue, May 29, 2012 at 10:47 AM, Luke-Jr <luke@dashjr.org> wrote:

> On Tuesday, May 29, 2012 8:52:49 AM Michael Gr=F8nager wrote:
> > The format of the sla.php page should then be specified too - but it
> could
> > be a json-rpc call returning a json object like (as result): {
> >     sla_version: "0.1",
> >     accept_no_fee_tx: false,
> >     min_fee: 50000,
> >     big_tx_fee: 10000, // extra fee pr kb
> > }
> > I guess miners could work out a more suitable set of fees...
>
> Please not JSON, and not hard-coded logic. Bitcoin already has a secure
> scripting system - perhaps we can decide on an initial stack format and
> run a
> script retrieved from the URI?
>
>


--=20
Peter J. Vessenes
CEO, CoinLab
M: 206.595.9839
Skype: vessenes
Google+ <https://plus.google.com/112885659993091300749>

--047d7b2ee639e544ca04c12e2a26
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

OK, I have a few thoughts on this:<div><br></div><div>1) Germane to the ori=
ginal conversation, anything hard to implement will not get implemented by =
miners.</div><div>2) Coinbase is hard-limited to 100 bytes; this has to inc=
lude space for voting as well as extra nonce, etc. So, I&#39;m not sure tha=
t a full URL is a good plan.</div>

<div>3) I&#39;m a little fuzzy on the details of BIP governance; but I&#39;=
m happy to write one up and get my thoughts down, or someone who&#39;s more=
 familiar could do it, I suppose.</div><div><br></div><div>I propose the fo=
llowing spec:</div>

<div><br></div><div>periodically a miner may choose to publish a url throug=
h their coinbase as follows:=A0</div><div><br></div><div>1) They shall prep=
end \mi: to the url to designate it as a url for miner info, and append a t=
railing \ to the url</div>

<div>2) The url given in the coinbase shall have http:// prepended to it be=
fore processing.</div><div>3) The destination may be a redirect (to allow s=
hort URLs), or may deliver content</div><div>4) The content-type returned b=
y the final site post-redirect shall be either (preferred text/json) or tex=
t/plain or text/html</div>

<div>4) The text of the document delivered shall be a JSON format dictionar=
y, and shall include at minimum the following fields:=A0&#39;min_fee&#39;, =
&#39;pool_name&#39;, and &#39;last_modified&#39; Optional fields can be det=
ermined over time as necessary by the mining community</div>

<div>5) The Service Level Agreement isn&#39;t binding, but miners who imple=
ment it are expected to make a best efforts attempt to follow it.</div><div=
><br></div><div>So a valid coinbase could be:</div><div>/P2SH/\mi:<a href=
=3D"http://goo.gl/mr2D\extra_nonce:2110">goo.gl/mr2D\extra_nonce:2110</a></=
div>

<div><br></div><div>Generally a miner would occasionally publish the \mi:\ =
when they had updated their SLA, or just every so often, but the canonical =
location would be the final destination URL from the redirects.</div><div>

<br></div><div>Inre: Luke&#39;s complaint about JSON, it is the language of=
 the web. There is no easier format for both computers and humans to read, =
and in this case, it includes extensibility, which is nice, since we have n=
o idea how miners will wish to divvy up their services; I think one would n=
eed to make a strong case against JSON for a specific reason to not choose =
it by default.</div>

<div><br></div><div>Thoughts welcome!</div><div><br></div><div>Best,</div><=
div><br></div><div>Peter</div><div><br></div><div><br></div><div><br><div c=
lass=3D"gmail_quote">On Tue, May 29, 2012 at 10:47 AM, Luke-Jr <span dir=3D=
"ltr">&lt;<a href=3D"mailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.=
org</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tuesday, May 29, 2012 8=
:52:49 AM Michael Gr=F8nager wrote:<br>
&gt; The format of the sla.php page should then be specified too - but it c=
ould<br>
&gt; be a json-rpc call returning a json object like (as result): {<br>
&gt; =A0 =A0 sla_version: &quot;0.1&quot;,<br>
&gt; =A0 =A0 accept_no_fee_tx: false,<br>
&gt; =A0 =A0 min_fee: 50000,<br>
&gt; =A0 =A0 big_tx_fee: 10000, // extra fee pr kb<br>
&gt; }<br>
&gt; I guess miners could work out a more suitable set of fees...<br>
<br>
</div>Please not JSON, and not hard-coded logic. Bitcoin already has a secu=
re<br>
scripting system - perhaps we can decide on an initial stack format and run=
 a<br>
script retrieved from the URI?<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><table style=
=3D"font-family:Times"><tbody><tr><td><img src=3D"http://coinlab.com/images=
/coinlab-logo.png"></td><td valign=3D"bottom"><div style=3D"font-family:Rob=
otoLight,&#39;Lucida Grande&#39;,Helmet,Freesans,sans-serif;font-size:16px;=
line-height:20px">

Peter J. Vessenes<br>CEO, CoinLab<br>M: 206.595.9839<br>Skype: vessenes<br>=
<a href=3D"https://plus.google.com/112885659993091300749" target=3D"_blank"=
>Google+</a></div></td></tr></tbody></table><br>
</div>

--047d7b2ee639e544ca04c12e2a26--