You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we can do deterministic wallets bip39 style from a seed and HD derivation like other things for EC keys.
That is no problem.
It would be nice to do it for non-EC keys as well, but the part with the xpub deriving addresses without the need of the private key is EC-only magic. But we don't really need that, we could do derivable non-EC keys with using the seed to feed into a deterministic PRNG and then have that used as the SecureRandom to generate other types of keys.
There are problems that probably make this a bad idea:
If the key generation does any sort of floating point or per-platform/environment optimization it could generate different addresses on different machines/platforms/environments.
If the key generation algorithm changes in any ways, we will almost certainly generate different keys.
This isn't the sort of thing we can screw around on. Probably a bad idea.
The text was updated successfully, but these errors were encountered:
@tynes I understand completely. I really enjoy seed based deterministic wallets and use them almost exclusively in other coins.
I could make EC only wallets that support deterministic generation but then how people save a wallet depends on what time of wallet it is and I concerned about that sort of confusion.
So we can do deterministic wallets bip39 style from a seed and HD derivation like other things for EC keys.
That is no problem.
It would be nice to do it for non-EC keys as well, but the part with the xpub deriving addresses without the need of the private key is EC-only magic. But we don't really need that, we could do derivable non-EC keys with using the seed to feed into a deterministic PRNG and then have that used as the SecureRandom to generate other types of keys.
There are problems that probably make this a bad idea:
This isn't the sort of thing we can screw around on. Probably a bad idea.
The text was updated successfully, but these errors were encountered: