Pieter Wuille [ARCHIVE] on Nostr: 📅 Original date posted:2014-04-24 📝 Original message:On Thu, Apr 24, 2014 at ...
📅 Original date posted:2014-04-24
📝 Original message:On Thu, Apr 24, 2014 at 8:54 AM, Thomas Voegtlin <thomasv1 at gmx.de> wrote:
>> Why do clients need to use the features in BIP 64? If Electrum doesn't want to
>> use accounts, [...]
>
> To clarify:
> Electrum plans to have bip32 accounts; Multibit will not, afaik.
To clarify:
BIP64 has a much stricter definition for accounts than BIP32.
In BIP32, it is not well specified what accounts are used for. They
can be used for "subwallets", "receive accounts" (as in bitcoind's
account feature), "recurring payments", part of a chain used as
multisig addresses, ... determined individually for each index.
In BIP64, they are strictly used for subwallets, and can't be used by
anything else.
--
Pieter
📝 Original message:On Thu, Apr 24, 2014 at 8:54 AM, Thomas Voegtlin <thomasv1 at gmx.de> wrote:
>> Why do clients need to use the features in BIP 64? If Electrum doesn't want to
>> use accounts, [...]
>
> To clarify:
> Electrum plans to have bip32 accounts; Multibit will not, afaik.
To clarify:
BIP64 has a much stricter definition for accounts than BIP32.
In BIP32, it is not well specified what accounts are used for. They
can be used for "subwallets", "receive accounts" (as in bitcoind's
account feature), "recurring payments", part of a chain used as
multisig addresses, ... determined individually for each index.
In BIP64, they are strictly used for subwallets, and can't be used by
anything else.
--
Pieter