znort987 (OP)
Early bitcoin miner
VIP
Member
 Offline
Activity: 72
Merit: 10
|
 |
June 03, 2012, 09:17:42 PM
Last edit: April 24, 2013, 08:08:44 PM by znort987 |
|
z
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Every time a block is mined, a certain amount of BTC (called the
subsidy) is created out of thin air and given to the miner. The
subsidy halves every four years and will reach 0 in about 130 years.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
Peter Todd
Legendary
Offline
Activity: 1120
Merit: 1149
|
|
June 04, 2012, 03:57:37 AM |
|
Testnet was recently reset; try upgrading your client.
|
|
|
|
|
Diapolo
|
|
June 04, 2012, 09:19:11 AM |
|
I'm running on testnet, and chain download gets stuck at ~53546 blocks remaining ...
Anyone knows why ?
Which is the last block you have? It seems my client is stuck, too and has 6897 blocks. Edit: I'm seeing a few of these 06/04/12 09:19:20 ERROR: CheckProofOfWork() : nBits below minimum work
06/04/12 09:19:20 ERROR: CheckBlock() : proof of work failed
06/04/12 09:19:20 ERROR: ProcessBlock() : CheckBlock FAILED Dia |
|
|
|
Gavin Andresen
Legendary
Offline
Activity: 1652
Merit: 2216
Chief Scientist
|
|
June 04, 2012, 01:16:19 PM |
|
I just got stuck-- looks like somebody is serving up the testnet2 blockchain to testnet3 nodes that connect to them (that's what is causing the 'nBits below minimum work' message).
Re-running to connect to a real testnet3 node is getting me the correct blockchain (with 6,905 blocks).
|
How often do you get the chance to work on a potentially world-changing project?
|
|
|
|
Diapolo
|
|
June 04, 2012, 02:02:18 PM |
|
Gavin, is there any way, to send the old nodes on testnet an alert message to upgrade?
Dia
|
|
|
|
Gavin Andresen
Legendary
Offline
Activity: 1652
Merit: 2216
Chief Scientist
|
|
June 04, 2012, 04:10:52 PM |
|
It quickly downloads the blockchain (about 6K blocks), then claims to be up to
date, and then, 30 seconds later claims to be 50K+ blocks behind.
Bitcoin-Qt ? Sounds like a bug in the "estimate how many blocks there are based on what your peers tell you" bug. |
How often do you get the chance to work on a potentially world-changing project?
|
|
|
Gavin Andresen
Legendary
Offline
Activity: 1652
Merit: 2216
Chief Scientist
|
|
June 04, 2012, 07:21:17 PM |
|
That may very well be, but I'm generally surprised
to see that a testnet "reset" has so many dependencies
left on the old chain.
Would it be possible to have bitcoin-qt refuse
all testnet packets from a peer that identifies
as being below a certain version ?
Yes... but having peers with a completely different block chain from you connect is a good way to shake out obscure bugs. Like Bitcoin-Qt's "how many blocks are in the valid chain" code getting fooled... |
How often do you get the chance to work on a potentially world-changing project?
|
|
|
|
burger
|
|
June 04, 2012, 08:53:00 PM |
|
I also have the same problem =( I compiled latest bitcoin-qt from github to test the new translations.
|
|
|
|
|
Diapolo
|
|
June 04, 2012, 09:21:23 PM
Last edit: June 04, 2012, 09:32:15 PM by Diapolo |
|
I'm not sure where this bug is coming from, as the GUI client does: int ClientModel::getNumBlocks() const
{
return nBestHeight;
} and int ClientModel::getNumBlocksOfPeers() const
{
return GetNumBlocksOfPeers();
} Edit: I checked the debug.log and not a single node was reporting a version in the version message, that indicates, it even knows about a testchain reset. Dia |
|
|
|
|
burger
|
|
June 10, 2012, 06:42:17 AM |
|
hmm... I downloaded the latest sources from git and now testnet3 works again... BTW I get testnet2 working as well with Bitcoin Wallet for android.
Was there a bug that collided these two networks?
|
|
|
|
|
rini17
|
|
June 13, 2012, 05:33:36 PM |
|
I have the same problem, got errors trying to use testnet with current HEAD from https://github.com/bitcoin/bitcoin.git : received block 000000033cc282bc1fa9
ERROR: CheckProofOfWork() : nBits below minimum work
CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
received block 000000037b21cac5d30f
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
disconnecting node 173.208.219.162
Disconnected 173.208.219.162 for misbehavior (score=100)
|
|
|
|
|
