Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of taplink.co
	designates 50.117.27.232 as permitted sender)
	client-ip=50.117.27.232; envelope-from=jeremy@taplink.co;
	helo=mail.taplink.co; 
Content-Type: multipart/alternative; boundary=----------TfzeJ1ywNlHQ804g1rR64T
To: "Peter Todd" <pete@petertodd.org>, "Gavin Andresen"
	<gavinandresen@gmail.com>
References: <20131024143043.GA12658@savin>
	<CANEZrP100Lg_1LcFMKx1yWrGTSFb5GZmLmXNbZjPGaiEgOeuwA@mail.gmail.com>
	<20131024144358.GA17142@savin>
	<CANEZrP1TfM+wYbGjUk3+8JJZs6cKZXdb57xGMc=hDr9dQjMMZA@mail.gmail.com>
	<20131024145447.GA19949@savin>
	<CABsx9T0T0v=HnRRr6BLKNQOFMBJWrhF4G4SOCJ9DidGJBB8Eow@mail.gmail.com>
Date: Fri, 25 Oct 2013 00:51:22 -0700
MIME-Version: 1.0
From: "Jeremy Spilman" <jeremy@taplink.co>
Organization: TapLink
Message-ID: <op.w5h2rwhcyldrnw@laptop-air>
In-Reply-To: <CABsx9T0T0v=HnRRr6BLKNQOFMBJWrhF4G4SOCJ9DidGJBB8Eow@mail.gmail.com>
User-Agent: Opera Mail/1.0 (Win32)
oclient: 192.168.168.135#jeremy@taplink.co#465
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Making fee estimation better
Precedence: list

------------TfzeJ1ywNlHQ804g1rR64T
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

Gavin, can you confirm the best place to  read  up on the discuss fee  
estimation changes for v0.9?

I think fee estimation at its core is about providing a data point, or  
even call it an API, which can be used however you see fit.

What parameters do I want to see in a 'fee estimation' API?

  - 30 minutes vs 24 hours processing time
  - Confidence Levels (50%/90%)

What properties does the result have?
   - Is it globally consistent?

Talking about fees.. I read this:  
https://gist.github.com/gavinandresen/2961409 and there is so much there I  
really liked.

Any pointers for reading more about the leading theories on transaction  
fees? For example, how well do they correlate with network security? Are  
we getting what we are paying for? :-)
------------TfzeJ1ywNlHQ804g1rR64T
Content-Type: multipart/related; boundary=----------TfzeJ1ywNlHQ800YvarAZa

------------TfzeJ1ywNlHQ800YvarAZa
Content-Type: text/html; charset=iso-8859-15
Content-ID: <op.1382687482107.ea63da665d6b14ac@192.168.168.135>
Content-Transfer-Encoding: Quoted-Printable

<!DOCTYPE html><html><head>
<style type=3D"text/css">body { font-family:'Times New Roman'; font-size=
:13px}</style>
</head>
<body><div>Gavin, can you confirm the best place to &nbsp;read &nbsp;up =
on the discuss fee estimation changes for v0.9?</div><div><br></div><div=
>I think fee estimation at its core is about providing a data point, or =
even call it an API, which can be used however you see fit.</div><div><b=
r></div><div>What parameters do I want to see in a 'fee estimation' API?=
</div><div><br></div><div>&nbsp;- 30 minutes vs 24 hours processing time=
</div><div>&nbsp;- Confidence Levels (50%/90%)</div><div><br></div><div>=
What properties does the result have?</div><div>&nbsp; - Is it globally =
consistent?</div><div><br></div><div>Talking about fees.. I read this:
<a href=3D"https://gist.github.com/gavinandresen/2961409">https://gist.g=
ithub.com/gavinandresen/2961409</a> and there is so much there I really =
liked.</div><div><br></div><div>Any pointers for reading more about the =
leading theories on transaction fees? For example, how well do they corr=
elate with network security? Are we getting what we are paying for? :-)<=
/div><div><br></div><br></body></html>
------------TfzeJ1ywNlHQ800YvarAZa--

------------TfzeJ1ywNlHQ804g1rR64T--