Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: btc_enigma on June 02, 2016, 01:10:01 PM



Title: Testnet slow confirmation times
Post by: btc_enigma on June 02, 2016, 01:10:01 PM
Hi,

Is there a reason test blocks are arriving every 20 minutes ? Shouldn't we have a faster block arrival time on testnet to help testing. Previously we used to have blocks on testnet every 2-5 min

http://tbtc.blockr.io/



Title: Re: Testnet slow confirmation times
Post by: achow101 on June 02, 2016, 04:12:50 PM
Testnet mining power tends to vary a lot. Considering that testnet has forked, it is likely that there is not a lot of mining power on testnet to have fast blocks


Title: Re: Testnet slow confirmation times
Post by: btc_enigma on June 03, 2016, 03:39:48 AM
How do I move to testnet fork having faster confirmation times ? I am using 0.12.1

Also I am getting same warnings as here https://bitcointalk.org/index.php?topic=1471338.0


Title: Re: Testnet slow confirmation times
Post by: achow101 on June 03, 2016, 11:08:18 AM
How do I move to testnet fork having faster confirmation times ? I am using 0.12.1

Also I am getting same warnings as here https://bitcointalk.org/index.php?topic=1471338.0
You can't. As was said by Belcher in the thread you mentioned, there are two forks, the Bitcoin Core fork and Bitcoin Classic. I'm not sure if sure if any of them have faster confirmations. You should only use the Button Core fork because that is more representative of the mainnet state.


Title: Re: Testnet slow confirmation times
Post by: bitdumper on June 03, 2016, 11:21:19 AM
No one wants to throw thier miners in testnet mining because it has no profit. A few miners with very low hash power are active. So they cant solve the block in high difficulty and solve them after the difficulty drops. We need some generous people.


Title: Re: Testnet slow confirmation times
Post by: Gwapo on June 03, 2016, 11:36:29 AM
I think its working fine now. I have faced the similar problem 3 hours ago but not now.

Sometimes the network might get jammed due to some 'test' spam attacks. I'm wondering if thats the case here.