{"type":"rich","version":"1.0","author_name":"npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","author_url":"https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-23\n📝 Original message:On Wed, Apr 23, 2014 at 10:43 PM, Pavol Rusnak \u003cstick at gk2.sk\u003e wrote:\n\u003e On 04/23/2014 10:41 PM, Luke-Jr wrote:\n\u003e\u003e I don't see how. The user knows he has money in different subwallets. As long\n\u003e\u003e as he has a way to specify which subwallet he is accessing in single-subwallet\n\u003e\u003e clients, there shouldn't be a problem.\n\u003e\n\u003e Right. But these clients have no right to call themselves BIP64\n\u003e compatible then.\n\nWould you consider software which scans all accounts as specified by\nBIP64, but has no user interface option to distinguish them in any\nway, view them independently, and has no ability to keep the coins\napart... compatible with BIP64?\n\nAccording to the argument here mentioned earlier (\"all or nothing\"),\nit is, as it will not break interoperability with other BIP64\nsoftware. Still, it doesn't support the accounts feature, and perhaps\nthat's fine?\n\n-- \nPieter"}