i would stretch the password, with pbkdf2 or argon2 with like 30k
rounds or something first, rather than "just hashing it". remember,
it's pretty easy to validate these seeds - not like you lock someone
out after 9 guesses!
On Wed, May 5, 2021 at 3:38 PM Tobias Kaupat via bitcoin-dev
wrote:
>
>
Hi Tobias.
The most recent release of Coldcard now offers "Seed XOR" to solve
similar problems. It allows any numbers of standard BIP-39
compatible seed phrases to be bitwise XOR'ed together to make a new seed.
Coldcard can split an existing seed into 2, 3 or 4 new phrases, or
you can take your e
Hi,
I'm writing to report a defect in Bitcoin Core bip125 logic with minor
security and operational implications for downstream projects. Though this
defect grieves Bitcoin Core nodes 0.12.0 and above, base layer safety isn't
impacted.
# Problem
Bip 125 specification describes the following sign
Hello Erik,
Thanks for your reply.
After a little research I came to the same conclusion. PDKDF2 makes sense,
since it is already used in BIP39.
I will update my code.
Regarding SeedXOR:
That's at least a similar solution, but than I have to store 2 phrases, I
really like to keep one part in my
Good morning ZmnSCPxj,
Thanks for your response. I agree there are few exceptions:
1.Unconfirmed output can be spent resulting in conflict with RBF
2.Race condition and mining pool may include old transaction with low fee
I am trying few things related to RBF and handling such exceptions, will s
