Namecoin: name_firstupdate stays unconfirmed
-
- Posts: 1
- Joined: Sat Jan 18, 2014 10:10 am
- Contact:
Namecoin: name_firstupdate stays unconfirmed
Hello,
Yesterday I registered disk.bit
The name_firstupdate stays unconfirmed.
How is that possible? And how am I possible to correct it?
Some other domains went very well.
Thank you in advance!
Yesterday I registered disk.bit
The name_firstupdate stays unconfirmed.
How is that possible? And how am I possible to correct it?
Some other domains went very well.
Thank you in advance!
-
- Posts: 309
- Joined: Tue Jul 19, 2011 9:33 pm
Re: Namecoin: name_firstupdate stays unconfirmed
are you using namecoin-qt?erikerikerik wrote:Hello,
Yesterday I registered disk.bit
The name_firstupdate stays unconfirmed.
How is that possible? And how am I possible to correct it?
Some other domains went very well.
Thank you in advance!
also:
{
"name" : "d/disk",
"value" : "blank",
"txid" : "b5cab464e990af1b31ea10185fa9a47c2e9beb56d2fe81064f55cbad72ddadc3",
"address" : "N24z2xhDPPEeWvQZsuZ5VbiE7htLYDU83a",
"expires_in" : 35780
}
is already registered.. did you do it in the end? (tried restarting client?)
Re: Namecoin: name_firstupdate stays unconfirmed
I noticed this behaviour, too. It seems that if someone does a name operation and switches off his machine instantly, this name is in a limbo. If I try to take this name, the name_firstupdate gives me a
{"code":-1,"message":"there are pending operations on that name"}
After that, one of these can happen:
a) if he turns on his machine after a few hours, his operation eventually makes it to the blockchain and everything looks normal again.
b) if he doesn't switch on his PC within something like 22 hours, the expires_in field goes down to -100 or even -120 and I still get this error message. Then all of a sudden my name_firstupdate succeeds. However, this only works if I had restarted namecoind/Namecoin-QT in the meantime.
Is there something like a timeout on pending operations like these? If not, is it possible to block a name with this method forever?
{"code":-1,"message":"there are pending operations on that name"}
After that, one of these can happen:
a) if he turns on his machine after a few hours, his operation eventually makes it to the blockchain and everything looks normal again.
b) if he doesn't switch on his PC within something like 22 hours, the expires_in field goes down to -100 or even -120 and I still get this error message. Then all of a sudden my name_firstupdate succeeds. However, this only works if I had restarted namecoind/Namecoin-QT in the meantime.
Is there something like a timeout on pending operations like these? If not, is it possible to block a name with this method forever?
Re: Namecoin: name_firstupdate stays unconfirmed
Hey guys, I have the same or similar issue. A domain registered a while ago hasn't gotten past OP_NAME_FIRSTUPDATE and also says "there are pending operations on that name" for any edit attempts (http://explorer.dot-bit.org/n/123459).
I was using namecoin-qt and the computer had not been shutdown during the registration. I've also tried restarting several times.
Code: Select all
Date Op Block Transaction Value
24/11/13 08:49:11 OP_NAME_FIRSTUPDATE 147515 2580892
24/11/13 05:39:31 OP_NAME_NEW 147502 2580763 Hash : ab02a9087e6d3b21fcf7774c714a35cb7b9a2728
-
- Posts: 309
- Joined: Tue Jul 19, 2011 9:33 pm
Re: Namecoin: name_firstupdate stays unconfirmed
not sure..
but.. if nameindex is corrupt , it might try to let you register names which have already been taken.
If you have any stuck transactions in your transaction list, you can just delete them in console window..
deletetransaction <tx#>
but.. if nameindex is corrupt , it might try to let you register names which have already been taken.
If you have any stuck transactions in your transaction list, you can just delete them in console window..
deletetransaction <tx#>
Re: Namecoin: name_firstupdate stays unconfirmed
It's highly unlikely that the name was already registered because the transaction time in the block explorer corresponds to when I was registering it. I deleted the transaction, and the name currently comes up as unavailable for registration. I think it's stuck in some kind of limbo, but hopefully it will be available again after it expires. At least the faulty transaction no longer shows up in the wallet. Thanks.
-
- Posts: 309
- Joined: Tue Jul 19, 2011 9:33 pm
Re: Namecoin: name_firstupdate stays unconfirmed
i think i seen something liek this before.. maybe an old post by khal.. although cannot find it..
Re: Namecoin: name_firstupdate stays unconfirmed
Do you own the namecoin address of the name (N24z2xhDPPEeWvQZsuZ5VbiE7htLYDU83a) ?
To know it, use the command: validateaddress N24z2xhDPPEeWvQZsuZ5VbiE7htLYDU83a
If that's the case, you can restart namecoin with the param "-rescan".
If it is still not sufficient, you can rename nameindex.dat to nameindex.dat.old (to keep it as a backup) and restart (it'll be rebuilt on startup).
If you don't own it, be patient :p
From what I remember from the old case, some name_update tx where is ram and relayed to the network, and didn't allow other people to do name_update (the client check this). A simple restart of namecoin empty the ram and allow you to do a name_update, unless you receive the same bugged tx before.
Not sure if it is the same thing or not.
To know it, use the command: validateaddress N24z2xhDPPEeWvQZsuZ5VbiE7htLYDU83a
If that's the case, you can restart namecoin with the param "-rescan".
If it is still not sufficient, you can rename nameindex.dat to nameindex.dat.old (to keep it as a backup) and restart (it'll be rebuilt on startup).
If you don't own it, be patient :p
From what I remember from the old case, some name_update tx where is ram and relayed to the network, and didn't allow other people to do name_update (the client check this). A simple restart of namecoin empty the ram and allow you to do a name_update, unless you receive the same bugged tx before.
Not sure if it is the same thing or not.
NamecoinID: id/khal
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
GPG : 9CC5B92E965D69A9
NMC: N1KHAL5C1CRzy58NdJwp1tbLze3XrkFxx9
BTC: 1KHAL8bUjnkMRMg9yd2dNrYnJgZGH8Nj6T
Register Namecoin domains with BTC
My bitcoin Identity - Send messages to bitcoin users
Charity Ad - Make a good deed without paying a cent
Re: Namecoin: name_firstupdate stays unconfirmed
It says ismine=false for that address. Where do you see the address info for a name?
Also, how does the expiration work.. does it just release the name registration once the timer runs out? Can renewal be done before that? Are there any notifications?
Also, how does the expiration work.. does it just release the name registration once the timer runs out? Can renewal be done before that? Are there any notifications?
-
- Posts: 309
- Joined: Tue Jul 19, 2011 9:33 pm
Re: Namecoin: name_firstupdate stays unconfirmed
you can renew before it expirespsionin wrote:It says ismine=false for that address. Where do you see the address info for a name?
Also, how does the expiration work.. does it just release the name registration once the timer runs out? Can renewal be done before that? Are there any notifications?
to get the address of a name you can do:
name_show <name>
everytime you update/renew the name, the address changes