Hi Gavin / Luke,
BIP-13 again... I started to implement a bitfield based parsing of the version
byte using the description I got from Luke, but I then discovered that it does
not hold:
Network class:
00xx - main network
01xx - reserved
10xx - reserved
11xx - test network
However, the definitions en base58.h are:
PUBKEY_ADDRESS = 0, ()
SCRIPT_ADDRESS = 5, (0101)
PUBKEY_ADDRESS_TEST = 111, (0110) !!!
SCRIPT_ADDRESS_TEST = 196, (11000100) !!!
[as a side note litecoin is 48 (0011) and namecoin is 52 (00110100)]
On Wednesday, February 22, 2012 11:29:59 AM Michael Grønager wrote:
SCRIPT_ADDRESS_TEST = 196, (11000100) !!!
11xx - test network
xx00 - bitcoin
010y - p2sh
This fits...
PUBKEY_ADDRESS_TEST = 111, (0110) !!!
What Gavin said.
Just posted this on the wiki BIP-13 discussion - should I make it into a BIP of
its own ?
---
The version portion of the address has so far been labeled network id, and
indicates from which network and which chain the address can be used for. I
think that this change from network id to version
RE:
base58-encode: [one-byte network ID][20-byte hash][one-byte address
class][3-byte checksum]
How will the code distinguish between the old scheme:
[one-byte-version][20-byte-hash][4-byte-checksum]
and the new?
1 in 256 old addresses will have a first-byte-of-checksum that matches the
new
5 matches
Mail list logo
