Polyseed has a number of advantages over Monero’s standard seeds:
The wallet creation date is embedded in the mnemonic seed. This way you no longer have to worry about restoring your wallet from the correct restore height. It uses BIP-39 wordlists. These wordlists container shorter and more common words than Monero’s lists. Polyseeds seeds are quicker to write down and memorize.
Is it possible (in the near future) to provide a single AppImage file (or single binary file, or single executable file, etc) as a Github-release?
P.S. Your project reminded me of this HTML/Javascript Brainwallet (WarWallet's fork) turned into a single CLI executable file: https://github.com/moncho/warpwallet
Providing that option would be great for UX!
Last but not least, I'll write it again: your CLI BTC msg tool is awesome!
Congratulations and keep it evolving!
Cheers!
Post
Topic
BoardProject Development
Re: Sign and verify easily with BitcoinMessageTools
by
Financisto
on 18/03/2024, 05:13:21 UTC
No problem, I understand!
BTW as it's python based: a fork with CLI for use in Linux (Terminal) would be wonderful...
Re: Sign and verify easily with BitcoinMessageTools
by
Financisto
on 14/03/2024, 21:23:54 UTC
Is it possible (in the near future) to provide a single HTML file (for offline usage) as a Github-release (the way iancoleman does with his BIP39 project)?
Providing that option users might avoid those annoying dependencies installation procedures...
Is it possible (in the near future) to provide a single HTML file (ready to be downloaded as a single file) as a Github-release (the way iancoleman does with his BIP39 project)?
Providing that option users might avoid those annoying dependencies Installation procedures...
Just to let you know, ZPyWallet also has brainwallet generation capability, and even for extended private keys, but I haven't written the documentation for that yet.
Good to know that!
I'm gonna take a look at it.
BTW which type of brainwallet algorithm did you choose for that project?
Traditional SHA2 over (user typed) passphrase?
Or
Warp Wallet type (Key Derivation Function: Argon2id, scrypt, bcrypt, PBKDF2)?
There's a bit of a contradiction there. You wrote that you are revoking those addresses, but also that you are using those addresses. When you sign a message using one of those addresses, what are we supposed to do?
Simple: If you receive a signed message from those "revoked" addresses → ignore that message entirely and its sender!
That's the thing: a staked address is meant to prove you're the long-term account owner. Your account is over 10 years old, your staked address was only a few years old.
I never used them anyway. I mainly created and staked them for testing purposes.
Quote
Staking a new one is exactly what an account buyer/hacker would do, it means you can no longer prove you're the long-term owner.
Account buyers/hackers might buy/hack accounts but it's not usual for them to buy/hack bitcoin private keys...
Quote
You're going to be disappointed: there is no "standard" for signing messages from Segwit addresses. Electrum came up with something, but Bitcoin Core can't even do it.
Don't worry about it. Electrum will do just fine! Others will follow in the future...
Post
Topic
BoardProject Development
Re: ₿ LIST ₿ Compilation of (open-source) BRAINWALLET projects.
by
Financisto
on 13/02/2024, 06:03:25 UTC
₿ UPDATE ₿ February 2024 ₿
Changelog:
monero-wallet-generator project by moneromooo has been added.