Michael
Michael
Thanks @junderw ! v1 worked for me. _I see v1 has functions `signSchnorr` and `verifySchnorr`. Will these not work? (edit: my mistake, those functions are in `bip32`, but not in...
> bip32 works with the latest tiny-secp256k1 @junderw does this include React Native / web based or are you talking Node?
PR here: https://github.com/Legrandin/pycryptodome/pull/593 Thanks!
Note: I thought about renaming the original functions (`Shamir.split` and `Shamir.combine`) to `Shamir.split_block` and `Shamir.combine_block` (as they support 16 byte blocks), and having the original functions support the greater key...
Hmm @MarkusH - trying to think it through, I don't think that's true. It basically changes from `2**256` to `2**128 x 2**128` so still preserved. To imply that it's `2**129`...
> If a 32 byte string is used as two 16 byte keys, each half can be attacked individually. @Varbin, can we prove this to be true? It's only true...
Created this question here to help resolve this: https://crypto.stackexchange.com/questions/98243/is-it-secure-to-do-shamir-key-split-on-a-key-in-blocks-and-recombine Looking forward to learning one way or the other. If we assume the split key method is bad, do you recommend...
Has this been solved since a year has passed?
Had same trouble as above when I was trying to figure out mapping from key (`z6Mkp...`) to publicKeyBase58 (`B12NY...`). @OR13 , I think an example showing the hex of the...