Tuesday, March 24, 2026
HomeBitcoinnon-public key - From bitcoinj v0.2

non-public key – From bitcoinj v0.2

I’ve used bitcoinj v0.2
From wich I’ve a base64 string of 12 bytes 16 characters
and a base58 string of 34 characters that’s 25 bytes.
it has a xor check in that string so I’ve an identical 10 bytes from the base64 string
with an identical 16 bytes from that base58 string

However how do I exploit them?
Is that this aes-128? so the 16 bytes is a encrypted seed?
Or do I’ve to affix then togheter to get a 26 bytes uncooked non-public key
It is from the time earlier than WIF

Thanks to your reply however that’s approach to new, what I’ve discovered, and why it solely will be bitcoinj 0.2 and never newer or older, within the older model it wouldn’t have the xor examine of the two separate strings, and newer makes use of protobuf, so it’s java serialization model 5, my 25 bytes begin with this 05 what would later be used as P2SH, so sure my base58 string begins with a 3 when that wasn’t a factor but. And wif wasn’t. If I exploit a base58 decoder I get the identical 20 bytes payload, as once I use getaddressinfo with the identical 34 characters, the primary byte is 77 what in java could be TC_BLOCKDATA = (byte)0x77; in these 20 bytes it has a xor examine to match 16 bytes with the ten bytes from the 12 bytes and it matches, so my 12/10 bytes matches my 20/16 bytes the 20 bytes ends with 4e 49 what could possibly be NI native import and 01 what could possibly be compressed public key, so that is very particular with bitcoinj 0.2 and nothing else

perhaps this is sensible to anyone the 12 bytes begin with 0xec and the 20 bytes ends with 0x01 what could possibly be compressed public key however extra lifelike 01 (SC_WRITE_METHOD

as far as I figured it out now it is hmac-sha256 so it offers the uncooked non-public key, stil do not know if the 01 stands for compressed or not, will let

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments