Author

Topic: z (Read 1859 times)

sr. member
Activity: 340
Merit: 250
GO http://bitcointa.lk !!! My new nick: jurov
z
June 13, 2012, 12:33:36 PM
#11
I have the same problem, got errors trying to use testnet with current HEAD from https://github.com/bitcoin/bitcoin.git :
Quote
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)
full member
Activity: 195
Merit: 100
June 10, 2012, 01:42:17 AM
#10
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?
hero member
Activity: 772
Merit: 500
June 04, 2012, 04:21:23 PM
#9
I'm not sure where this bug is coming from, as the GUI client does:

Code:
int ClientModel::getNumBlocks() const
{
    return nBestHeight;
}

and

Code:
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
full member
Activity: 195
Merit: 100
June 04, 2012, 03:53:00 PM
#8
I also have the same problem =( I compiled latest bitcoin-qt from github to test the new translations.
legendary
Activity: 1652
Merit: 2301
Chief Scientist
June 04, 2012, 02:21:17 PM
#7
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...
legendary
Activity: 1652
Merit: 2301
Chief Scientist
June 04, 2012, 11:10:52 AM
#6
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.
hero member
Activity: 772
Merit: 500
June 04, 2012, 09:02:18 AM
#5
Gavin, is there any way, to send the old nodes on testnet an alert message to upgrade?

Dia
legendary
Activity: 1652
Merit: 2301
Chief Scientist
June 04, 2012, 08:16:19 AM
#4
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).
hero member
Activity: 772
Merit: 500
June 04, 2012, 04:19:11 AM
#3

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
Quote
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
legendary
Activity: 1120
Merit: 1160
June 03, 2012, 10:57:37 PM
#2
Testnet was recently reset; try upgrading your client.
vip
Activity: 72
Merit: 12
June 03, 2012, 04:17:42 PM
#1
z
Jump to: