<oembed><type>rich</type><version>1.0</version><author_name>npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_name><author_url>https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-08-21&#xA;📝 Original message:On Fri, Aug 21, 2015 at 06:15:16PM -0400, Chris Pacia wrote:&#xA;&gt; On Aug 21, 2015 2:07 AM, &#34;Peter Todd via bitcoin-dev&#34; &lt;&#xA;&gt; bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; &#xA;&gt; &gt; Also, as I mentioned, just look at the popularity of wallets such as&#xA;&gt; &gt; Mycelium that are not adopting bloom filters, but going with SPV&#xA;&gt; &gt; verification of block headers w/ lookup servers.&#xA;&gt; &#xA;&gt; Related I recently had a conversation with a Mycelium employee who told me&#xA;&gt; they were considering moving to spv/bloom because of the server issues&#xA;&gt; Andreas mentioned.&#xA;&gt; &#xA;&gt; I don&#39;t know any more about their plans, but I wouldn&#39;t assume the above&#xA;&gt; statement to be correct.&#xA;&#xA;That&#39;d be a foolish design decision to move exclusively over; their&#xA;wallet was safe to use during the recent fork, unlike Android Wallet,&#xA;precisely because of their existing design.&#xA;&#xA;In any case, regardless of whether we&#39;re wrong about the popularity&#xA;issue, I&#39;ve yet to see any issues raised with implementing NODE_BLOOM&#xA;that will adversely affect such wallets - we&#39;ve certainly got no&#xA;shortage of node capacity to go around.&#xA;&#xA;-- &#xA;&#39;peter&#39;[:-1]@petertodd.org&#xA;00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d&#xA;-------------- next part --------------&#xA;A non-text attachment was scrubbed...&#xA;Name: signature.asc&#xA;Type: application/pgp-signature&#xA;Size: 650 bytes&#xA;Desc: Digital signature&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150821/fb815101/attachment.sig&gt;</html></oembed>