Title: Assist recovering funds: Pockets created with non-standard public key format (no 02/03/04 prefix)
I’ve a Bitcoin deal with (19CLgD8MqfWzE3BzzUGjyXKM4EP72XgYJ8) containing ~0.064 BTC that was created utilizing a non-standard public key format. I can cryptographically show possession however cannot create a sound transaction because of the format subject.
Technical particulars:
- Public key (uncooked bytes, no prefix): 1f6483705a513b4d81fca6369b6bfca80c9c103eb57dbda575b94b8127727aba8c0019d4f08d49187ead5294d641f35a419e14c8783bb1436ae06f4969c93108
- Deal with: 19CLgD8MqfWzE3BzzUGjyXKM4EP72XgYJ8
The pockets was created utilizing this Python script:
from ecdsa import SigningKey, SECP256k1
public_key = SigningKey.from_string(bytes.fromhex(private_key_hex), curve=SECP256k1).get_verifying_key()
public_key_bytes = public_key.to_string() # Used uncooked bytes with out customary Bitcoin prefix
I can generate the right deal with (verified on blockchain), however cannot create legitimate transactions as a result of:
The general public key lacks the usual 02/03 (compressed) or 04 (uncompressed) prefix
Makes an attempt to import to straightforward wallets fail
Uncooked transaction creation fails with "mandatory-script-verify-flag-failed (Public secret's neither compressed or uncompressed)"
I've tried:
Changing to WIF format (would not keep right public key format)
Utilizing older Bitcoin Core variations
Creating uncooked transactions sustaining unique format
Numerous public key format conversions
Is there any strategy to create a sound transaction that trendy nodes will settle for utilizing this non-standard public key format?