I hit a private key that validated R while checking a signature for a whale. But I can't see the address when I try to dump a bip44 1000adddy. It validates R to the current signature, but I'm stuck. Can anyone help me figure this out? I know there's a margin of error, and lattice can be glitchy sometimes, but still... Thanks.
Help with Missing Transaction Data
7 replies 47 views
What software are you using for this? Are you sure it's legit? You might wanna check your private key with a site like bitaddress.org and see if it shows a balance.
Nah, it's not a scam. Just a tool I made myself. Had some issues with the public key logic, but I think it's fixed now. Still confused why it validates two signatures but messes up the public key translation. Just using Python with some advanced lattice methods.
Ugh, I wish I could share my values... Restarted everything and found old values from December. I verified two ECDSA signatures with their known nonce values. Both signatures matched the r values, so the k values are correct for private key recovery.
What do you do if there's a missing txn that prevents a valid current txn from being accepted? I made a txn and it checks out, but when I try to push it, I get a missing or spent txn warning. This should be the missing one. How do I adjust for it? Any help would be awesome.
Have you thought about asking the actual coder of your tool? Pretending you know what's up won't help if you can't see the issue. Good luck!
It wasn't a txn, just some messed-up result getting inserted. I stripped it down and now it's malformed. I can sign the RS, and it resolves to the pubkey, which is good. But I’m stuck on the rest. Anyone know a good builder for signature data? Maybe I should test with just one input?
Why not just ask OpenAI for some Python code? Also, if you generate signatures yourself, they might not work on the actual blockchain.