Page 1 of 1

Testnet having issues

Posted: Sat Mar 18, 2017 10:20 pm
by DrHaribo
What's going on with the namecoin testnet?

Forked or locked up somehow?

http://testnet.explorer.namecoin.info/ has been stuck for 12 days

Re: Testnet having issues

Posted: Sun Mar 19, 2017 3:18 am
by biolizard89
DrHaribo wrote:What's going on with the namecoin testnet?

Forked or locked up somehow?

http://testnet.explorer.namecoin.info/ has been stuck for 12 days
Honestly not sure, I think a lot of testnet nodes are running old software that didn't follow a consensus fork at some point. We're planning to reset testnet sometime soon-ish. Is there a particular thing you need the testnet for?

Cheers.

Re: Testnet having issues

Posted: Sun Mar 19, 2017 4:51 pm
by DrHaribo
I test changes to my pool software on the testnet.

Right now my test node is stuck on block 198853:

Code: Select all

> namecoin-cli getblockcount
198853
> namecoin-cli getblocktemplate
error code: -10
error message:
Namecoin is downloading blocks...
>
I am connected to two nodes in China that are also on block 198853 and they are running "/Satoshi:0.12.0/: version 110012"
Most nodes I get connected to report version ": version 38000" and are stuck on block 181071, just like the testnet block explorer.

I mostly have a lot of "connection refused" in the log though. It seems there are very few namecoin testnet nodes.
Might be better to set up a private testnet. I do think a public testnet is useful though.

Re: Testnet having issues

Posted: Sun Mar 19, 2017 7:52 pm
by biolizard89
DrHaribo wrote:I test changes to my pool software on the testnet.

Right now my test node is stuck on block 198853:

Code: Select all

> namecoin-cli getblockcount
198853
> namecoin-cli getblocktemplate
error code: -10
error message:
Namecoin is downloading blocks...
>
I am connected to two nodes in China that are also on block 198853 and they are running "/Satoshi:0.12.0/: version 110012"
Most nodes I get connected to report version ": version 38000" and are stuck on block 181071, just like the testnet block explorer.

I mostly have a lot of "connection refused" in the log though. It seems there are very few namecoin testnet nodes.
Might be better to set up a private testnet. I do think a public testnet is useful though.
Yes, there are very few testnet nodes at the moment, and there are long periods where no testnet blocks are mined. I'd like to see more testnet nodes, but this isn't at the top of my priority list at the moment. A private testnet might be a good solution.

Re: Testnet having issues

Posted: Thu Mar 23, 2017 3:12 pm
by cannon-c
What can node operators do to help testnet? Enable testnet on my nodes?

Re: Testnet having issues

Posted: Fri Mar 24, 2017 1:00 am
by biolizard89
cannon-c wrote:What can node operators do to help testnet? Enable testnet on my nodes?
Honestly I'm not certain -- we're going to be resetting testnet anyway, so enabling testnet on your nodes won't be useful long-term. But sure, feel free to run a testnet node and post its IP+port somewhere in this forum.