Open unsystemizer opened 9 years ago
Are you on client v0.3.80 or on Namecoin Core?
I issued the command manually but I got a few more in that state.
NameGUI can not know about external ´name_new´ operations. If you do an external ´name_firstupdate´ it should be able to read it's data (at least once it is in a block, may also depend on the client type).
You can take a look at %appdata%/nameGUI/nameNewDb.txt
you can take a look at the data nameGUI is aware of. For each name the last entry matters.
Value: (postponed:)
,Address: ---
,Status: pending_new(220)
andExpires in:
(empty).Pending operations on name ...
But even though the current number of blocks jumped by 2, I can still see that the pending value is 220 - it just seems permanently stuck in that state. Maybe that's how it is on the Namecoin Core level.
I didn't close Namecoin Core before NameGUI, but maybe I did close the both before 12 blocks expired (but even in that case, what would have to be pressed in NameGUI to indicate
first_update
?)I issued the command manually but I got a few more in that state.