<oembed><type>rich</type><version>1.0</version><author_name>npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_name><author_url>https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-03-11&#xA;📝 Original message:On Tue, Mar 11, 2014 at 10:13 AM, Jeff Garzik &lt;jgarzik at bitpay.com&gt; wrote:&#xA;&#xA;&gt; Sure, but I don&#39;t see wallets being able to _assume_ _remote_ parties&#xA;&gt; have an HD wallet for a long, long time.  Interoperability common&#xA;&gt; sense implies the environment will be heterogenous, perhaps forever,&#xA;&gt; invalidating assume-each-party-uses-HD logic.&#xA;&#xA;&#xA;If the remote party is one of the parties involved in a multisig, and&#xA;speaks the &#34;Lets set up a multisig wallet together / Lets spend from a&#xA;multisig&#34; protocols, then it should be perfectly reasonable to assume that&#xA;they&#39;re HD-capable.&#xA;&#xA;Remote parties paying into a multisig, or receiving funds from a multisig,&#xA;don&#39;t have to support it (that&#39;s what P2SH gives us).&#xA;&#xA;-- &#xA;--&#xA;Gavin Andresen&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140311/2aba3b81/attachment.html&gt;</html></oembed>