<p>It seems you can issue your <code>name_firstupdate</code> transaction whenever you're ready (in particular, right after doing the <code>name_new</code>).  It won't be included in a block until the <code>name_new</code> is mature (12 confirms) but should be picked up shortly after that happens.</p>

<p>I don't have any source for this other than recent experience, but my names are showing up when I do <code>name_list</code> so I take it that they are properly registered.</p>

<p>EDIT: I thought about it a little, and I suppose you should wait a little bit (at least until your <code>name_new</code> is included in a block).  The reason being that nobody can know what name you're trying to register until you do <code>name_firstupdate</code>, and so they can't steal it from you.  Sending both the <code>name_new</code> and the <code>name_firstupdate</code> is vulnerable because someone can quickly issue their own <code>name_new</code> for the same name, and depending on luck (or in the worst-case, their control of a significant hashrate) claim it before you can.</p>

<p>Someone more familiar with the intimate details of how requests for the same name are resolved can comment on whether this scenario is possible or not.</p>

CC BY-SA 3.0
2012-01-12T10:10:57.833Z
Then, how can I know if my name_new has been included in a block?
o0'.
CC BY-SA 3.0
2012-01-12T16:34:21.347Z
When you do `listtransactions` there's a field labeled `confirmations`; if that is non-zero then it has been included in that many blocks.

Alternatively you can check the block explorer at http://explorer.dot-bit.org/; look for your transaction to show up in the list at the bottom.
Sumudu Fernando
CC BY-SA 3.0
2012-01-11T01:16:39.197Z
2012-01-11T01:39:24.063Z
2012-01-11T01:39:24.063Z
Sumudu Fernando
<p>The FAQ very vaguely says "Wait at least 12 blocks", but it doesn't make much sense to me.</p>

<p>Unless I have totally misunderstood how this works, once the <code>name_new</code>d domain is in the chain, I should safely be able to proceed to the next step... so how can I know <em>exactly</em> if it is ready? Or am I missing something?</p>

<namecoin><domain-registering>
How can I know *exactly* when my name_new domain is ready for the name_firstupdate step?
o0'.
# How can I know *exactly* when my name_new domain is ready for the name_firstupdate step?

(Asked by: username_0 on 2012-01-04)

The FAQ very vaguely says "Wait at least 12 blocks", but it doesn't make much sense to me.

Unless I have totally misunderstood how this works, once the `name_new`d domain is in the chain, I should safely be able to proceed to the next step... so how can I know *exactly* if it is ready? Or am I missing something?

**Tags:** namecoin, domain-registering


---

## 1 answers

### Answer by username_1 on 2012-01-11. Score: 4 | Accepted answer

It seems you can issue your `name_firstupdate` transaction whenever you're ready (in particular, right after doing the `name_new`). It won't be included in a block until the `name_new` is mature (12 confirms) but should be picked up shortly after that happens.

I don't have any source for this other than recent experience, but my names are showing up when I do `name_list` so I take it that they are properly registered.

EDIT: I thought about it a little, and I suppose you should wait a little bit (at least until your `name_new` is included in a block). The reason being that nobody can know what name you're trying to register until you do `name_firstupdate`, and so they can't steal it from you. Sending both the `name_new` and the `name_firstupdate` is vulnerable because someone can quickly issue their own `name_new` for the same name, and depending on luck (or in the worst-case, their control of a significant hashrate) claim it before you can.

Someone more familiar with the intimate details of how requests for the same name are resolved can comment on whether this scenario is possible or not.

> **Comments:**
> **username_0**: Then, how can I know if my name_new has been included in a block?  
> **username_1**: When you do `listtransactions` there's a field labeled `confirmations`; if that is non-zero then it has been included in that many blocks.  Alternatively you can check the block explorer at http://explorer.dot-bit.org/; look for your transaction to show up in the list at the bottom.  

---

