<oembed><type>rich</type><version>1.0</version><author_name>npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47</author_name><author_url>https://nostr.ae/npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-09&#xA;📝 Original message:Le 09/04/2014 17:54, Gregory Maxwell a écrit :&#xA;&#xA;&gt; Sadly today Electrum requires more than a full node, it requires a&#xA;&gt; number of large additional indexes over what a full node has and&#xA;&gt; pruning is precluded. I don&#39;t think that increasing the resource&#xA;&gt; utilization of the node is a good way to go there for the purposes&#xA;&gt; expressed here. (not that electrum couldn&#39;t be used here, but not&#xA;&gt; unmodified without the resource usage increasing route)&#xA;&gt;&#xA;&#xA;Electrum uses two large indexes:&#xA;&#xA;     address -&gt; utxo&#xA;&#xA;(patricia tree, aka &#34;ultimate blockchain compression&#34;, see thread &#xA;started by Alan Reiner in the bitcointalk forum)&#xA;&#xA;     address -&gt; spent history&#xA;&#xA;The first index is not going to grow larger than what bitcoind already &#xA;needs to store, because bitcoind will always need to store utxos.&#xA;&#xA;The second index threatens to become large. However, Electrum servers do &#xA;not keep the full histories, they prune older entries. Without adapting &#xA;Electrum clients, it would even be possible to keep only one bit per &#xA;address (to know whether that address has been used or not), and that &#xA;information is only used to restore wallets from seed, not during normal &#xA;operations.&#xA;&#xA;If the first index (patricia tree) was implemented in bitcoind, that &#xA;would obviously be a big relief for electrum servers.&#xA;&#xA;&#xA;&#xA;&gt;&gt; and that it might be an easier way to support&#xA;&gt;&gt; SPV clients than creating a new API in bitcoind for it since Stratum&#xA;&gt;&gt; itself already relies on bitcoind to provide it&#39;s services.&#xA;&gt;&#xA;&gt; Bitcoin&#39;s own P2P protocol is already the API for a ordinary SPV&#xA;&gt; client. So I don&#39;t believe any new API would be require, except&#xA;&gt; perhaps for some process management stuff (which also isn&#39;t provided&#xA;&gt; for Electrum).&#xA;&gt;&#xA;&gt; ------------------------------------------------------------------------------&#xA;&gt; Put Bad Developers to Shame&#xA;&gt; Dominate Development with Jenkins Continuous Integration&#xA;&gt; Continuously Automate Build, Test &amp; Deployment&#xA;&gt; Start a new project now. Try Jenkins in the cloud.&#xA;&gt; http://p.sf.net/sfu/13600_Cloudbees&#xA;&gt; _______________________________________________&#xA;&gt; Bitcoin-development mailing list&#xA;&gt; Bitcoin-development at lists.sourceforge.net&#xA;&gt; https://lists.sourceforge.net/lists/listinfo/bitcoin-development&#xA;&gt;&#xA;&gt;</html></oembed>