|
Simple yet excellent tool!
Any translation campaigns in mind?
This project may be useful and reach beyond horizons with translations to Arabic, Chinese, French, Russian, Spanish, &c...
|
|
|
|
|
22 & 33: financisto
Thanks!
|
|
|
|
It seems that your open-source project does some stuff with Monero. Are you thinking about adding Polyseed to its features? Source: https://github.com/tevador/polyseedPolyseed 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.
|
|
|
|
I am pleased to announce that the development of this service is now acquired by CPUchain project.
Thank you.
Hello there! I was about to consider writing about your project here: ⚡ LIST ⚡ FOSS BrainwalletsAre you its lead developer nowadays? Are you one of its maintainer? Have you left the project? |
|
|
|
Thanks for your reply! Your project is gonna join the list soon... In my opinion, brainwallet algorithms are too vulnerable to try to secure with any kind of KDF, since the input is often predictable. Generating a few (e.g. 9 or +) BIP39 random words + unique salt (e.g. checksum) should be interesting as an experiment. Fewer words to remember (less than standard 12) and not so easy to crack wallet (considering using the WarpWallet implementation or improved version). Not worthy risking all your savings but it's still an intriguing experiment. |
|
|
|
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 (WarpWallet's fork) turned into a single CLI executable file: https://github.com/moncho/warpwalletProviding that option would be great for UX! Last but not least: your CLI BTC msg tool is awesome! Congratulations and keep it evolving! Cheers! |
|
|
|
Is it possible (in the near future) to provide a single HTML file (for offline usage) as a Github-release (the way Ian Coleman does with his BIP39 project)? Providing that option users might avoid those annoying dependencies installation procedures... Sources: https://iancoleman.io/bip39/https://github.com/iancoleman/bip39/releases/latest/BTW your BTC msg tools is a great project: BitcoinMessage.Tools Congratulations for reaching those results so far... And keep up the effort! |
|
|
|
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 (p.s. You won't!) 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. 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... 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 (devs) will follow in the future... |
|
|
|
BTC SIGNED MSG #1-----BEGIN BITCOIN SIGNED MESSAGE-----
I am Financisto (forum member) @ bitcointalk.org
Henceforth I'll not be using this Bitcoin address anymore: 1J5FCnt9nBiUrTVmu7WR3GrH6Zd6egyDic
Henceforth I'll not be using this Bitcoin address anymore: 1QCDzCvQrkMv1z9QqGyNTp6Z2GHgNtQ4zE
Henceforth I'll not be using this PGP key anymore: FD691DC0675E311B821E149B347C00B148CA769D
Today is Sunday, February 11th, 2024 (UTC).
The sole purpose of this signed message is:
1) to revoke my Bitcoin addresses @ bitcointalk.org
2) to revoke my PGP key @ bitcointalk.org
3) to prove I'm the owner of those Bitcoin addresses.
This signed message is not subject for reuse in no other forum, community or place.
-----BEGIN SIGNATURE-----
1J5FCnt9nBiUrTVmu7WR3GrH6Zd6egyDic
HBz/sQ47+nxNU1b6eA/SQlNdK18PhzNzkT8e6t8IJMVTk4Cvf+8laYho1/IyBFEO9grn5Sd4gviPyKawHC05vCU=
-----END BITCOIN SIGNED MESSAGE-----
BTC SIGNED MSG #2-----BEGIN BITCOIN SIGNED MESSAGE-----
I am Financisto (forum member) @ bitcointalk.org
Henceforth I'll not be using this Bitcoin address anymore: 1J5FCnt9nBiUrTVmu7WR3GrH6Zd6egyDic
Henceforth I'll not be using this Bitcoin address anymore: 1QCDzCvQrkMv1z9QqGyNTp6Z2GHgNtQ4zE
Henceforth I'll not be using this PGP key anymore: FD691DC0675E311B821E149B347C00B148CA769D
Today is Sunday, February 11th, 2024 (UTC).
The sole purpose of this signed message is:
1) to revoke my Bitcoin addresses @ bitcointalk.org
2) to revoke my PGP key @ bitcointalk.org
3) to prove I'm the owner of those Bitcoin addresses.
This signed message is not subject for reuse in no other forum, community or place.
-----BEGIN SIGNATURE-----
1QCDzCvQrkMv1z9QqGyNTp6Z2GHgNtQ4zE
Gzpj33I8b4BwqhNIsJFyAZkp5qbspqbYR2QqsIZX8UGtsQdGVnfiz/A7e4rFXT6/+xAl+qk7O1UtMAEm7TwnSfA=
-----END BITCOIN SIGNED MESSAGE-----
Please quote and verify. Thanks in advance!
|
|
|
|
|
Show Posts
