{"type":"rich","version":"1.0","author_name":"npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","author_url":"https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-04-23\n📝 Original message:On Wednesday, April 23, 2014 8:04:03 PM Pavol Rusnak wrote:\n\u003e On 04/23/2014 10:01 PM, Luke-Jr wrote:\n\u003e \u003e Yes, it should scan all possible (under the BIP-defined structure)\n\u003e \u003e branches regardless of which features it supports.\n\u003e \n\u003e So you suggest to scan for accounts, show balances but don't allow user\n\u003e to spend them? Does not seem right to me.\n\nScan all branches for UTXOs, then you have the balance for the wallet. Account \nbalances are metadata, so cannot be known from the seed alone. If you want to \nhave a way to restore accounts, you must define some more detailed wallet file \nformat (which could be built on top of this).\n\nOn Wednesday, April 23, 2014 8:04:35 PM you wrote:\n\u003e On 23.04.2014, at 22:02, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\u003e \u003e On Wednesday, April 23, 2014 8:01:16 PM Tamas Blummer wrote:\n\u003e \u003e\u003e The wallet has to know how it got the UTXO in order to be able to spend\n\u003e \u003e\u003e it.\n\u003e \u003e \n\u003e \u003e No it doesn't... Just the assigned scriptPubKey and secret(s) required to\n\u003e \u003e satisfy it.\n\u003e \n\u003e To know the secret it needs to know which key coordinate to use that is\n\u003e logically the same as knowing the address it used to receive it.\n\nSure, it *knows* what address was used to receive it. But at the point it's a \nUTXO, that address is no longer relevant.\n\nLuke"}