I have a question for the Namecoin developers team (if anyone else knows the answer => feel free to post, though I would ask one of the developers to confirm):
The description of the name registration process is rather vague in the official namecoin wiki (https://wiki.namecoin.org/index.php?tit ... it_Domains). Some of the information in vinceds post needs some explaining too imho (https://github.com/vinced/namecoin/blob/master/FAQ.md).
A name_new operation of the name "d/example" (used for examplary purposes. I know it has already been registered) broadcasts the encrypted version of the name for security reasons.
The next step is to perform a name_firstupdate operation. Now that's where the questioning starts:
Why do I have to wait for 12 Blocks? Vinced writes the following:
In order to better understand the process flow, I would like to ask for clarification of the outcome of the following Scenario:There is a mandatory 12 block wait that gives you enough time to broadcast your name with first_update, reducing the chance that someone will get in a first_update ahead of you.
1) Block 0: Bob performs name_new for the name "d/bob"
2) Block 6: Alice decides to acquire the name "d/bob" too and performs a name_new operation too.
3) Block 12: Since the Namecoin wiki says to wait for 12 Blocks, Bob has not yet performed a name_firstupdate. By this time, his first transaction has at least 12 confirmations. Unfortunately, Bob forgets about Namecoin and does NOT perform name_firstupdate on time.
4) Block 18: Now 12 Blocks have passed since Alice called the name_new operation, i.e. her first transaction has been confirmed 12 times. Alice now calls name_firstupdate. WHAT HAPPENS?
5) Block 20 : Bob remembers about his Namecoin name and performs a name_firstupdate too. WHAT HAPPENS?
Who will "win" the race and receive the name?
Now, there have been explanations in various papers on what happens if multiple nodes happen to broadcast a name registration for the same block => decided by "luck". But does this still apply to the situation, when one of the users forgets to perform a name_firstupdate on
Thanks in Advance,