<oembed><type>rich</type><version>1.0</version><author_name>npub17kz55p7ysz4ftvq2xyr2zamc776cygwcm5fdz8ndj3jm5umm65xq4sr5tq</author_name><author_url>https://nostr.ae/npub17kz55p7ysz4ftvq2xyr2zamc776cygwcm5fdz8ndj3jm5umm65xq4sr5tq</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-27&#xA;📝 Original message:There is no ensured Quality of service, is there? If you &#34;bid&#34; higher, then&#xA;you don&#39;t know what you are going to get. Also because you have no way of&#xA;knowing what *others* are bidding. Only if you have auctions (increasing&#xA;increments) you can establish a feedback loop to settle demand and supply.&#xA;And the supply side doesn&#39;t adapt. Adapting supply would help resolve parts&#xA;of the capacity problem.&#xA;&#xA;On Sat, Jun 27, 2015 at 7:37 PM, Peter Todd &lt;pete at petertodd.org&gt; wrote:&#xA;&#xA;&gt; On Sat, Jun 27, 2015 at 07:26:00PM +0200, Benjamin wrote:&#xA;&gt; &gt; &#34;Thus we have a fixed capacity system where access is mediated by supply&#xA;&gt; &gt; and demand transaction fees.&#34;&#xA;&gt; &gt;&#xA;&gt; &gt; There is no supply and demand. That would mean users would be able to&#xA;&gt; adapt&#xA;&gt; &gt; fees and get different quality of service depending on current capacity.&#xA;&gt; &gt; For example if peak load is 10x average load, then at those times fees&#xA;&gt; &gt; would be higher and users would delay transactions to smooth out demand.&#xA;&gt;&#xA;&gt; That&#39;s exactly how Bitcoin works already. See my article on how&#xA;&gt; transaction fees work for more details:&#xA;&gt;&#xA;&gt; https://gist.github.com/petertodd/8e87c782bdf342ef18fb&#xA;&gt;&#xA;&gt; --&#xA;&gt; &#39;peter&#39;[:-1]@petertodd.org&#xA;&gt; 0000000000000000007fc13ce02072d9cb2a6d51fae41fefcde7b3b283803d24&#xA;&gt;&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150627/4f0abdd8/attachment.html&gt;</html></oembed>