<oembed><type>rich</type><version>1.0</version><author_name>npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_name><author_url>https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-04-23&#xA;📝 Original message:On Wednesday, April 23, 2014 7:49:38 PM Pavol Rusnak wrote:&#xA;&gt; On 04/23/2014 09:44 PM, Luke-Jr wrote:&#xA;&gt; &gt; Why do clients need to use the features in BIP 64? If Electrum doesn&#39;t&#xA;&gt; &gt; want to use accounts, then it can just use account 0 for everything.&#xA;&gt; &gt; Refund chains are&#xA;&gt; &#xA;&gt; As Andreas wrote earlier in this thread: &#34;There is no &#34;bare minimum&#34;.&#xA;&gt; Either you implement the &#34;BIP&#34; fully or not.&#34;&#xA;&gt; &#xA;&gt; What you suggest does not follow the principle of least surprise.&#xA;&gt; Suppose user imports his BIP64 compatible wallet into Electrum, which&#xA;&gt; claims it is BIP64 compatible, but actually implements just a subset of&#xA;&gt; the spec (sticking account index to 0). The user now sees just a&#xA;&gt; fraction of his coins and is puzzled.&#xA;&#xA;Any wallet should import all the coins just fine, it just wouldn&#39;t *use* any &#xA;account other than 0. Remember addresses are used to receive bitcoins; once &#xA;the UTXOs are in the wallet, they are no longer associated with the address or &#xA;any other details of how they were received.&#xA;&#xA;Luke</html></oembed>