Problem: If a successful name_new command is allowed to mature via ~12 block confirmations, the random number given with that name_new transaction is not subsequently recognized by name_firstupdate.
Workaround: run name_new a second time for the same name, and then run name_firstupdate *immediately* with the random number from the second name_new - this is successful.
Here is the relevant input and output to illustrate the problem, from my command history. I've edited out everything except the (real) transaction ID for the problematic name_new, in case more clues can be found in the blockchain.
Here I run a name_new for a domain that's not registered:
Code: Select all
namecoind.exe name_new domain
[
"c82990d0249f578c3e3fb149f9c94912eb4fac168f7251da4b82abce0a3fd38d",
"[random]"
]
Code: Select all
namecoind.exe name_firstupdate d/domain <random>
c82990d0249f578c3e3fb149f9c94912eb4fac168f7251da4b82abce0a3fd38d "{\"map\": {\"\": \"0.0.0.0\", \"subdomain\": \"0.0.0.0\"}}"
error: {"code":-1,"message":"previous tx used a different random value"}
Client versions reported to reproduce this issue:
- 6/18 Windows binary release from dot-bit wiki front page.
- Current vinced git source build (6/30/11) on Linux.