Namecoin Forum

what if it's ICANN itself that wants to take Namecoin over?

Please do not update 3000 domains at once. We are having network stability problems due to a massive number of transactions being made to consolidate a lot of 'spare change' to one address by an unknown party. Please spread these out over a week or two a few hundred a day - at most one every 3-5 mi...

It works, my coins are old enough. But I have to keep the daemon running a long time yet. Its like namecoin puts 30 or so name_updates per block... so this will take a few hours to finish. When did you start this? Did you try it once and then update the fee and try again? No, i only did this once, ...

It works, my coins are old enough.

But I have to keep the daemon running a long time yet.

Its like namecoin puts 30 or so name_updates per block... so this will take a few hours to finish.

Anyway, I will wait for a few hours, and if nothing happens, I will do the transaction loop again, with tx fee of 0,005 and also with more delay between the different name_updates (I will target 1 per sec)

This morning I am in the process of updating my 3000 domains. How should I best go about this, without causing any problems, for me or the network. I have a loop in a php file were I execute commandline all in a row. Is there an upper limit for this? SHould I spread the name_updates over a longer ti...

I hope I am not the one causing those problems.
Because I just did a 2000 name_update over a few minutes.
without tx fee. (I should have)

I have about 3000 domains I need to update at the moment.

How should I best go about this, without causing problems to the network?

Is a tx fee necessary?
Should I try and broadcast all 3000 name_updates at the same time? Or better spread it over some time?

If I am making a name_update , do I need to add a fee?
I mean, name_update doesn't cost me anything, right?

Just someone consolidating all his 10k and 100k addresses into a big one...

Probably for narcissistic reasons?

http://bitinfocharts.com/namecoin/addre ... HzS3Qg3nNz