Something might be wrong in vanitygen, the following (namecoin) combinations don't work:
Na, Nb, Nc, Nd, Ne, Nf, Ng, Nh, Ni, Nj, Nk, Nm, Nn, No, Np, Nq, Nr, Ns, Nt, Nu, Nv, Nw, Nx, Ny, Nz, NL, NM, NN, NP, NQ, NR, NS, NT, NU, NV, NW, NX, NY, NZ
but the rest do - this is probably a bug in vanitygen, i'll report it
Is there any update on this bug? Vanitygen won't generate addresses that start with the combinations listed above.
I don't know that it's a bug, more likely that there are no possible values of raw binary Namecoin addresses that will convert into a Base58 address that starts with these characters. The underlying data of a Namecoin address must start with a network ID of 00110100 (binary) + hash. This means that the range of inputs to the Base58 converter can only go from 0011010000000000... to 0011010011111111...
You can search or explore the
namecoin block explorer and likely see that there are no examples of these "nonworking" addresses, a less lazy person than me could actually do the math and describe the possible Base58 address ranges.
Apparently these
are valid namecoin addresses, but with a leading byte of 53 (
see here). Furthermore, there are a bunch of second characters that require the leading byte to be 54.
The wiki page shows that namecoin addresses that start with N can have a leading byte of 52, 53, or 54. Does anyone know the math to figure out which one to use? Is it actually valid to have a namecoin address with a leading byte other than 52?
EDIT: No, it's not valid:
$ namecoind validateaddress NPhauxDmxGJfKSAJmAnZBLH9mhrKY5BALv
{
"isvalid" : false
}
Does that apply to any address with a leading byte not equal to 52?
