Show Posts
My answer was a general answer to a general question about the two forms of Bitcoin address and was not meant to be a technical paper or exact description of how to create Bitcoin addresses (that is what the wiki is for).
So, I started out with "Leaving out some small details:".
Thanks for filling in a few of the technical details.
So, I started out with "Leaving out some small details:".
Thanks for filling in a few of the technical details.
Ok, but anyway I don't understand "257 bit", this value is not correct at all. Or 512 bit and 256 bit, or 8+512 bit and 8+256 bit.
BTW, even with the additional details, the description is still incomplete because you left out the checksum in the hashing description.
No, the address in the blockchain's blocks (and in the UTXO data set) are stored exactly this way: ripemd160(sha256('02' or '03' + 'x'), 160 bit, no checksum, no base58 encode.
Example:
private key = 01
address = 91B24BF9F5288532960AC687ABB035127B1D28A5 (step 3, address for the blockchain)
address = 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm (checksum + base58) (step 9, address for human people)
Check with http://gobittest.appspot.com/Address or https://www.blockchain.com/it/btc/address/91B24BF9F5288532960AC687ABB035127B1D28A5
Now if we look at a tx that funds the address 91B24BF9F5288532960AC687ABB035127B1D28A5 / 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm :
https://www.blockchain.com/btc/tx/6797afc4d9b91fb9b283fedddec4e35b00d54063d73bb0d3e97f3537ed8fff3c?show_adv=true
output script: DUP HASH160 PUSHDATA(20)[91b24bf9f5288532960ac687abb035127b1d28a5] EQUALVERIFY CHECKSIG
The address in the "1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm" format is only for human people.
