<oembed><type>rich</type><version>1.0</version><author_name>npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</author_name><author_url>https://nostr.ae/npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2p</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 10:12 PM, slush &lt;slush at centrum.cz&gt; wrote:&#xA;&#xA;&gt; Maybe there&#39;re other ideas how to improve current situation without needs&#xA;&gt; of reworking the architecture.&#xA;&gt;&#xA;&#xA;Nothing I&#39;ve proposed here would require larger changes to the architecture&#xA;then were already planned. After SPV lands we are going to split off the&#xA;wallet, and that will need an interface to an bitcoind to allow &#39;running&#xA;with full node&#39;. If that can be generalized to be useful for other (SPV)&#xA;clients as well, that would be useful, hence I asked for input.&#xA;&#xA;It of course doesn&#39;t preclude also looking for other solutions.&#xA;&#xA;Wladimir&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140409/eb8737dd/attachment.html&gt;</html></oembed>