testnet seems to be pretty useless ATM because it doesn't introduce new blocks with a reasonable intervals.
you want to test something and you have no idea how long you will need to wait for a new block.
Topic: TEST network, for experimental development and hacking (Read 27380 times)
restarting it worked, its away now 
ive had my client in testnet mode for some time and it says 14 connections but the initial 1000 blocks hasn't changed...
does it normally take ages at moment ??
does it normally take ages at moment ??
Code:
0 addresses found from DNS seeds
For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere.
There is no DNS seeding available for the testnet work. Current options are IRC connection or using static --addnodes.
Fantastic, that's what I was missing, thanks!
Code:
0 addresses found from DNS seeds
For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere.
There is no DNS seeding available for the testnet work. Current options are IRC connection or using static --addnodes.
The important part being:
connect() failed after select(): No route to host
So either your network is down, or something is blocking your connection to IRC.
I checked the log and the IRC connection fails even for the live connection. However, the key part actually seems to be this:
Code:
0 addresses found from DNS seeds
For the live connection, this list is not empty (it has 48 addresses). If I operate on the assumption that the live connection was NEVER able to connect to IRC, then it got that seed list from somewhere.
EDIT: Okay I didn't realize this thread was started a year ago... I thought Gavin was proposing a NEW test network, a third one on top of the production and test networks already there. Please ignore this message.
As someone interested in developing a new client soon, can you tell me what is the difference between this new network, and the previous test-network? I mean, I thought that's what the test network was for... right?
In other words, what are the use cases for the two networks?
-Eto
As someone interested in developing a new client soon, can you tell me what is the difference between this new network, and the previous test-network? I mean, I thought that's what the test network was for... right?
In other words, what are the use cases for the two networks?
-Eto
Hmm.. odd but testnet won't work for me:
results in the following log:
at which point bitcoind simply hangs and no blocks are ever downloaded.
The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost.
What is going on here?
Code:
./bitcoind -daemon -testnet -rpcuser=hungry -rpcpassword=forfood -rpcport=8332
results in the following log:
Code:
Bitcoin version 0.3.25-beta
Default data directory /home/randomuser/.bitcoin
Bound to port 18333
Loading addresses...
dbenv.open strLogDir=/home/randomuser/.bitcoin/testnet/database strErrorFile=/home/randomuser/.bitcoin/testnet/db.log
Loaded 0 addresses
addresses 28ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000007199508e34a9f height=0
block index 0ms
Loading wallet...
nFileVersion = 32500
fGenerateBitcoins = 0
nTransactionFee = 0
fMinimizeToTray = 0
fMinimizeOnClose = 0
fUseProxy = 0
addrProxy = 127.0.0.1:9050
wallet 44ms
Done loading
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 101
mapPubKeys.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
0 addresses found from DNS seeds
ThreadRPCServer started
sending: version (85 bytes)
pv4 eth0: MYSERVERIP
addrLocalHost = MYSERVERIP:18333
ThreadSocketHandler started
ThreadIRCSeed started
ThreadOpenConnections started
ThreadMessageHandler started
connect() failed after select(): No route to host
IRC connect failed
IRC waiting 71 seconds to reconnect
ThreadRPCServer method=getinfo
keypool reserve 2
keypool return 2
at which point bitcoind simply hangs and no blocks are ever downloaded.
The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost.
What is going on here?
The important part being:
connect() failed after select(): No route to host
So either your network is down, or something is blocking your connection to IRC.
Hmm.. odd but testnet won't work for me:
results in the following log:
at which point bitcoind simply hangs and no blocks are ever downloaded.
The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost.
What is going on here?
Code:
./bitcoind -daemon -testnet -rpcuser=hungry -rpcpassword=forfood -rpcport=8332
results in the following log:
Code:
Bitcoin version 0.3.25-beta
Default data directory /home/randomuser/.bitcoin
Bound to port 18333
Loading addresses...
dbenv.open strLogDir=/home/randomuser/.bitcoin/testnet/database strErrorFile=/home/randomuser/.bitcoin/testnet/db.log
Loaded 0 addresses
addresses 28ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000007199508e34a9f height=0
block index 0ms
Loading wallet...
nFileVersion = 32500
fGenerateBitcoins = 0
nTransactionFee = 0
fMinimizeToTray = 0
fMinimizeOnClose = 0
fUseProxy = 0
addrProxy = 127.0.0.1:9050
wallet 44ms
Done loading
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 101
mapPubKeys.size() = 102
mapWallet.size() = 0
mapAddressBook.size() = 1
0 addresses found from DNS seeds
ThreadRPCServer started
sending: version (85 bytes)
pv4 eth0: MYSERVERIP
addrLocalHost = MYSERVERIP:18333
ThreadSocketHandler started
ThreadIRCSeed started
ThreadOpenConnections started
ThreadMessageHandler started
connect() failed after select(): No route to host
IRC connect failed
IRC waiting 71 seconds to reconnect
ThreadRPCServer method=getinfo
keypool reserve 2
keypool return 2
at which point bitcoind simply hangs and no blocks are ever downloaded.
The sticky part appears to be the inability to connect to MYSERVERIP:18333. I've just replace MYSERVERIP there. No, that doesn't show up as 127.0.0.1 or localhost.
What is going on here?
So if I run bitcoind in testnet mode and it downloads the block chain, and then I switch to the live chain, what happens? What do I need to delete/reset/watch out for?
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
Bitcoin uses a different default location for the testnet blockchain and wallet, so you can switch between networks freely.
Awesome, thanks. Pool's all set up... testing now.
Only took one day. Not bad.
So if I run bitcoind in testnet mode and it downloads the block chain, and then I switch to the live chain, what happens? What do I need to delete/reset/watch out for?
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
Bitcoin uses a different default location for the testnet blockchain and wallet, so you can switch between networks freely.
What exactly are the use cases for the TEST network?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
"Yes". Its for testing.
Though, at the moment the testnet difficulty is high enough again that its less useful for any kind of testing that requires mining.
So if I run bitcoind in testnet mode and it downloads the block chain, and then I switch to the live chain, what happens? What do I need to delete/reset/watch out for?
And vice versa - what if I've already downloaded the live block chain and switch to testnet mode.
What exactly are the use cases for the TEST network?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
"Yes". Its for testing.
Though, at the moment the testnet difficulty is high enough again that its less useful for any kind of testing that requires mining.
What exactly are the use cases for the TEST network?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
Should I use it when setting up a new pool, for example, to make sure everything is running correctly? Or is it intended more for miners & ecommerce apps that will be consuming bitcoins?
I have to say testnet is getting hard to generate coins/blocks or something is wrong. I am hardly getting any blocks coming in so my transactions are not processing so i moved my miner that does 650Mhash/s onto the testnet network. This is saved setting that worked in the past and normally generate the coins in 3-15 min. So far it has been 40 min with no coins generated and only 1 other block coming in from the network. Looks like it will take me about 80 min to test a single transaction at the min.
Wish i could use testnet in a box but using multiple machines linux and win plus need to use custom build of the client on the backend.
Is this just because the difficulty on the testnet is getting too high? Couldn't it be set lower so more blocks come out and people can do tests faster?
Wish i could use testnet in a box but using multiple machines linux and win plus need to use custom build of the client on the backend.
Is this just because the difficulty on the testnet is getting too high? Couldn't it be set lower so more blocks come out and people can do tests faster?
Use this with modified configs:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/
I have to say testnet is getting hard to generate coins/blocks or something is wrong. I am hardly getting any blocks coming in so my transactions are not processing so i moved my miner that does 650Mhash/s onto the testnet network. This is saved setting that worked in the past and normally generate the coins in 3-15 min. So far it has been 40 min with no coins generated and only 1 other block coming in from the network. Looks like it will take me about 80 min to test a single transaction at the min.
Wish i could use testnet in a box but using multiple machines linux and win plus need to use custom build of the client on the backend.
Is this just because the difficulty on the testnet is getting too high? Couldn't it be set lower so more blocks come out and people can do tests faster?
Wish i could use testnet in a box but using multiple machines linux and win plus need to use custom build of the client on the backend.
Is this just because the difficulty on the testnet is getting too high? Couldn't it be set lower so more blocks come out and people can do tests faster?
cuqa if I had to guess, I would say you are accidentally mining on realnet instead of testnet. ;-)
hey, I wanna build a pool frontend and set up a server w/ pushpool which is running in testnet currently.
I mined all night and some hours today, summed up maybe 10 hours with 35 Mhash/s and I havent solved a single Block. Usually I should create 1 Block every 30 minutes so I start to think that I did something wrong.
What could be the problem? Everything seems to work fine except that I dont receive any Test Coins.
However, I havent switched any ports in server.json or bitcoin.conf ..
I mined all night and some hours today, summed up maybe 10 hours with 35 Mhash/s and I havent solved a single Block. Usually I should create 1 Block every 30 minutes so I start to think that I did something wrong.
What could be the problem? Everything seems to work fine except that I dont receive any Test Coins.
However, I havent switched any ports in server.json or bitcoin.conf ..
Super, thanks!
I always tried https://freebitcoins.appspot.com/test/ but the page is down. https://testnet.freebitcoins.appspot.com/ works!
Thanks!
Cheers,
Simon.
I always tried https://freebitcoins.appspot.com/test/ but the page is down. https://testnet.freebitcoins.appspot.com/ works!
Thanks!
Cheers,
Simon.
Testnet faucet is up and running if you need testnet coins:
https://testnet.freebitcoins.appspot.com/
Although I've mostly been using testnet-in-a-box for testing recently:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/
https://testnet.freebitcoins.appspot.com/
Although I've mostly been using testnet-in-a-box for testing recently:
https://sourceforge.net/projects/bitcoin/files/Bitcoin/testnet-in-a-box/
Jump to: