<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:2014-04-09&#xA;📝 Original message:On Wed, Apr 9, 2014 at 8:42 AM, Brian Hoffman &lt;brianchoffman at gmail.com&gt; wrote:&#xA;&gt; How would this affect the user in terms of disk storage? They&#39;re going to&#xA;&gt; get hammered on space constraints aren&#39;t they? If it&#39;s not required how&#xA;&gt; likely are users to enable this?&#xA;&#xA;If Bitcoin core activates pruning a full node can be supported in—&#xA;say— 4GBytes or so. (That gives enough space to store the utxo about&#xA;350MB now, and a couple gigs for blocks to serve out).&#xA;&#xA;I&#39;d imagine getting information from SPV wallet developers how much&#xA;disk usage agility they think is required is part of what Wladimir is&#xA;looking for.</html></oembed>