Open bxlkm opened 5 years ago
please give me addnode testnet address. ths!!!
also found this error with 0.17
You can use addnode
namecoin-cli addnode testnet.node.ip.address add
testnet.namecoin.org
31.45.121.24
45.33.65.68
51.68.251.200
Last one is mine :)
I`m not aware about dns-seeder for namecoin, it would be best option to run one.
I`m not aware about dns-seeder for namecoin, it would be best option to run one.
We do have multiple seeds for mainnet, and they seem to be working (just did a quick test). For testnet we have one (dnsseed.test.namecoin.webbtc.com), which seems to not work. I'm happy to add more if someone is willing to run testnet seeds.
@domob1812 you probably need point some peers that seeder can start with, we also need add it (seeder) to code.
@domob1812 you probably need point some peers that seeder can start with, we also need add it (seeder) to code.
Not sure what you mean - the seeders (for mainnet) are working fine, and are in the code: https://github.com/namecoin/namecoin-core/blob/69e327b36b89c64059ad529ea9867fd1577dbf35/src/chainparams.cpp#L156
For testnet, we do have a seeder in the code as well, but it seems to not be working. I cannot fix that, as I'm not the one running it. But if you or anyone else is willing to run a testnet seeder, I'm happy to add it in the code as well.
@domob1812 sorry, I was sure that this testnet seed is yours :)
For those who come here in hopes of getting up a testnet node, I've also set up one now that can be used as addnode
: 51.75.22.122
We really should set up a working seed for testnet, but I don't have any servers available for that myself at the moment.
This is my current addnode list for testnet:
addnode=testnet.namecoin.org addnode=31.45.121.24 addnode=45.33.65.68 addnode=51.68.251.200 addnode=38.133.141.29 addnode=51.75.22.122
FYI, the just released version 0.18.0 schedules a softfork (BIP16, CSV and segwit, see #239). On testnet, this will activate at block height 232,000, which is rather "soonish" (but it depends on mining activity, of course). So please everyone running testnet nodes update so that we can hopefully see all working well on testnet before the mainnet activation.
For those who come here in hopes of getting up a testnet node, I've also set up one now that can be used as
addnode
: 51.75.22.122We really should set up a working seed for testnet, but I don't have any servers available for that myself at the moment.
I've checked the chaininfo after a night ,it synced up to 23097 blocks~~
Testnet nodes currently connected to me:
139.180.143.165
45.33.65.68
94.23.252.190
31.45.104.147
51.75.22.122
47.244.156.37
23.129.64.160
47.244.58.44
51.68.251.200
(last is mine)
namecoin-cli --testnet getblockchaininfo
{
"chain": "test",
"blocks": 230297,
"headers": 230297,
"bestblockhash": "8089389d0bfc9b16075b872e689e7e6e7b6e99902a24262bd3dd3891d5ee 62e9",
"difficulty": 0.1475501740387343,
"mediantime": 1559375097,
"verificationprogress": 0.9994743377352909,
"initialblockdownload": false,
"chainwork": "000000000000000000000000000000000000000000000000ed17e1e267dee179 ",
This is my current addnode list for testnet:
addnode=testnet.namecoin.org addnode=31.45.121.24 addnode=45.33.65.68 addnode=51.68.251.200 addnode=38.133.141.29 addnode=51.75.22.122
Added all above, but
getblockchaininfo
{"result":{"chain":"test","blocks":233225,"headers":265905,
blocked in 233225 for a long time
Interesting, my own testnet node as well. Perhaps some nodes have not updated for segwit and are thus producing an invalid (longer) chain? I've not looked into that, though, so this is just a vague guess.
Resolved? New testnet seed was added.
Hi,
When I start a namecoin node with testnet=1, it seems it can't find a valid peer to sync. So is this testnet chain still valid? or if anyone could provide me a valid node, that will be great! VERSION: 0.16.3
2019-02-13 07:31:26 0 addresses found from DNS seeds
2019-02-13 07:31:26 dnsseed thread exit
2019-02-13 07:32:19 Adding fixed seed nodes as DNS doesn't seem to be available.
Thanks!