<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2017-04-07&#xA;📝 Original message:On Thu, Apr 6, 2017 at 10:12 PM, Tomas via bitcoin-dev&#xA;&lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt;As this&#xA;&gt; solution, reversing the costs of outputs and inputs, seems to have&#xA;&gt; excellent performance characteristics (as shown in the test results),&#xA;&gt; updates to the protocol addressing the UTXO growth, might not be worth&#xA;&gt; considering *protocol improvements*&#xA;&#xA;I&#39;m still lost on this-- AFAICT your proposals long term resource&#xA;requirements are directly proportional to the amount of unspent output&#xA;data, which grows over time at some fraction of the total transaction&#xA;volume (plus the rate of spending which is more or less a constant).&#xA;&#xA;Can you help out my understanding here?</html></oembed>