<oembed><type>rich</type><version>1.0</version><author_name>npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304</author_name><author_url>https://nostr.ae/npub1sa86gng3pvs3jgyt5majwcrhn8ck5qxgy9pjqxkh79u638cd7dys28y304</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-07-23&#xA;📝 Original message:Doesn&#39;t matter.&#xA;&#xA;It&#39;s not going to be perfect given the block time variance among other factors but it&#39;s far more workable than guessing whether or not your transaction is going to end up in a block at all.&#xA;&#xA;jp&#xA;&#xA;&#xA;&gt; On Jul 24, 2015, at 8:53 AM, Peter Todd &lt;pete at petertodd.org&gt; wrote:&#xA;&gt; &#xA;&gt; -----BEGIN PGP SIGNED MESSAGE-----&#xA;&gt; Hash: SHA256&#xA;&gt; &#xA;&gt; &#xA;&gt; &#xA;&gt;&gt; On 23 July 2015 20:49:20 GMT-04:00, Jean-Paul Kogelman via bitcoin-dev &lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;&gt; &#xA;&gt;&gt; And it&#39;s obvious how a size cap would interfere with such a QoS scheme.&#xA;&gt;&gt; Miners wouldn&#39;t be able to deliver the below guarantees if they have to&#xA;&gt;&gt; start excluding transactions.&#xA;&gt; &#xA;&gt; As mining is a random, poisson process, obviously giving guarantees without a majority of hashing power isn&#39;t possible.&#xA;&gt; &#xA;&gt; &#xA;&gt; -----BEGIN PGP SIGNATURE-----&#xA;&gt; &#xA;&gt; iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVsYyK&#xA;&gt; AAoJEMCF8hzn9Lnc47AH/28WlecQLb37CiJpcvXO9tC4zqYEodurtB9nBHTSJrug&#xA;&gt; VIEXZW53pSTdd3vv2qpGIlHxuYP8QmDSATztwQLuN6XWEszz7TO8MXBfLxKqZyGu&#xA;&gt; i83WqSGjMAfwqjl0xR1G7PJgt4+E+0vaAFZc98vLCgZnedbiXRVtTGjhofG1jjTc&#xA;&gt; DFMwMZHP0eqWTwtWwqUvnA7PTFHxdqoJruY/t1KceN+JDbBCJWMxBDswU64FXcVH&#xA;&gt; 0ecsk9nhLMyylBX/2v4HjCXyayocH8jQ+FpLSP0xxERyS+f1npFX9cxFMq24uXqn&#xA;&gt; PcnZfLfaSJ6gMbmhbYG5wYDKN3u732j7dLzSJnMW6jk=&#xA;&gt; =LY1+&#xA;&gt; -----END PGP SIGNATURE-----&#xA;&gt;</html></oembed>