Author

Topic: Development question about (address, p2pkh, p2sh, hd_secret, Segwit) (Read 429 times)

staff
Activity: 3458
Merit: 6793
Just writing some code
Addresses use the Base58 Check Encoding: https://en.bitcoin.it/wiki/Base58Check_encoding. Part of this is a version byte that is prepended to the hash160 of the public key. That version byte is what determines the first character of an address, and is what is used to differentiate various address types.
newbie
Activity: 6
Merit: 0
I am developing a framework for development of Altcoin in Go.

see https://github.com/coin-network

I have been able to understand the basics of the elliptical curve to generate the public and private key and convert it to Bitcoin address format.

But I do not quite understand that it should be variable to set up a new unique address for an Altcoin.

My address.go program now has the following terminal output.

$ go run address.go
Code:
Private Key
104930057806725380329673246667213883341199392498193999899949555094217870343340

 Public Key
30281493937534716029482202294378086430575585216909050331938533692170322122530
73645510590725429585871939537348802644260091059911504300012495206619630132784

 New Address
115gcWR5oHFsShhxnPBnsT7J6nJahuBvPe

But the idea is to know what parameters I should send to my program, to generate different addresses or groups of public and private keys.

Here I saw something ... and they mention the BIPs 32, 38, 39, 44, ...
https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings

I can not understand that it is version_p2pkh, version_p2sh, version_hd_secret, Segwit, or referred to with a "multiple keypair chains, derived from a single root" Huh

My native language is Spanish, and it is not easy for me to understand BIPs in English.
Jump to: