Page 1 of 1

name_firstupdate cannot be mined if name_new is not already.

Posted: Wed Nov 30, 2011 2:45 pm
by picchio
I have this error in log file:
name_firstupdate cannot be mined if name_new is not already in chain and unexpired

I remember an error in command line like

./namecoind name_new forgottentext

I see in listtransactions:
{
"account" : "",
"address" : "name_new: 601e21*****",
"category" : "receive",
"amount" : 0.01000000,
"confirmations" : 5498,
"txid" : "b2911****",
"time" : 1320070513
},
{
"account" : "",
"address" : "name_new: 601e21****",
"category" : "send",
"amount" : -0.01000000,
"fee" : 0.00000000,
"confirmations" : 5498,
"txid" : "b2911****",
"time" : 1320070513
},
But in balance I have -0.01 NMC

Can I mine with merged mining or is not possible to do this?

Regards
Picchio

Re: name_firstupdate cannot be mined if name_new is not alre

Posted: Wed Dec 07, 2011 8:52 pm
by nodemaster
picchio wrote:I have this error in log file:
name_firstupdate cannot be mined if name_new is not already in chain and unexpired
You should at least wait 12 blocks after doing a name_new before doing a name_firstupdate
picchio wrote: Can I mine with merged mining or is not possible to do this?
It doesn't matter if you are merged mining or not. Furthermore there is no need for YOU to mine your name_* operation. Your namecoind just puts it onto the p2p network. All connected namecoind will add them to their block. The first who find the resulting block will do the first confirmation of your transaction.