-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem with p key #23
Comments
What kind of segwit address is it? The script doesn't work with all kinds of segwit addresses, only the P2SH-P2WPKH ones. |
the adress starts with 3, so I assumed is P2SH. |
The script does not support multisig at the moment. Need further details to find out why it fails. |
are u planning to add support for multisig? |
Do you know if it's multisig or segwit? How was the address created? What is the public address? |
Hi, I didn't see your questions before! |
Same issue for me. Can't claim from multisig wallet |
Same problem |
Multisig is not supported at the moment. Might consider adding it in the future. |
The scrypt doesn't recognize the key type when I introduce the p key.
Traceback (most recent call last):
File "C:\bitcoin_fork_claimer\claimer.py", line 1101, in
get_txid(coin, args)
File "C:\bitcoin_fork_claimer\claimer.py", line 346, in get_txid
restofprogram(coin, args)
File "C:\bitcoin_fork_claimer\claimer.py", line 961, in restofprogram
keytype, privkey, pubkey, sourceh160, compressed = identify_keytype(args.wifkey, args.srcaddr)
File "C:\bitcoin_fork_claimer\claimer.py", line 313, in identify_keytype
raise Exception("Unable to identify key type!")
Exception: Unable to identify key type!
it is a segwit adress, starts with 3, and the pkey starts wit L.
Any idea about what is hapenning?
The text was updated successfully, but these errors were encountered: