Topic: Hash accepted. No Bitcoin. (Read 7856 times)

Bitcoin raises its priority and sends a bunch of identical data. This might seem suspicious to antivirus software. Try generating on the testnet and see if you get the same problem.

My node didn't receive the block, either.

Interesting.  When I first started the new version of poclbm.exe there were maybe 15% "invalid or stale" messages for the first couple of minutes.  Now I am getting consistent "accepted" messages with no errors.  Also, I noticed that all of the submissions marked as "invalid or stale" had been submitted by me a couple of messages back.  So I conclude these are the "stale" ones and the "invalid" ones may be due to overclocked and malfunctioning GPU as you say.  Mabye when poclbm.exe starts up it takes a few seconds to call certain routines, during which time duplicate hashes are sent to the mining pool.  I am not a programmer.  Perhaps the author of the program could weigh in on these theories.

I got rid dof the "invalid or stale" messages by slightly downclocking my GPUs.

Thank you for pointing this out.  There are two distinct problems, unrelated, and you have solved the problem of the "invalid or stale" blocks with your latest release.  I realize you are the author and thank you for that as well.

Yeah, I actually did realize that on some level.  The paranoia just kicked in because I'm sitting here saying "What are the odds that this would fail just when I find a block?"  As to the latter part about generating "invalid or stale" blocks, I see that this is because it appears that I actually do either generate duplicate blocks or, more likely, resubmit them to the pool and they are rejected.  This is apparently a known issue and there is a new poclbm as of 1/4, which I have now downloaded and appears to have largely solved that problem, though I still get some "invalid or stale" messages.


Doubtful, unless my computer tries to communicate with some new IP address when it has found a block and the firewall blocks that new IP.  Is that the case?  Or is some new program triggered when a block is found that an antivirus would block it?  Hate to go another round for a few days, generate another winning block only to find that I once again have a communications failure of some sort and cannot claim the reward.  hanks.

Hash accepted means only that the block was accepted by your client as a valid solution. Next, it's broadcast to your peers, they broadcast it to theirs and so on. For some reason this broadcast didn't reach my node. This means it didn't reach other parts of the network too. Does someone see this particular hash in debug.log?

I definitely recommend opening your port 8333 to ensure better connectivity. This would also make someone cornering you out of the network harder. (I am not saying someone cornered you actually, it's difficult even with the port closed).

As for the pool - don't mix up problems. There was a major change recently and you should update poclbm to latest version.

This sounds like a firewall/antivirus blocking Bitcoin.

All of the other messages are normal.

Submitting a block you've generated would be pointless, they'd credit the coins to you since they wouldn't have the private key to your address

Incidentally, now reconnecting to the mining pool at bitcoin.cz practically all of my messages come back "invalid or stale".  Hate to seem paranoid, but could this be some "man in the middle attack" over IRC?  Could somebody be submitting my generated blocks to bitcoin.cz or have otherwise seized my 50 bitcoins by taking my generated block and submitting it themselves to the server?  Strange for successful block generations resulting in no reward and rejections from the mining pool server.

My network is pretty reliable.  In fact I was on my internet phone when I found the block, so the internet did not drop out.  Below is some additional info from the log.  I could let the 50 bitcoins go and not worry about it, but I have successfully generated bitcoins for a mining pool and generated a real block for the pool.  I decided to do this on my own and after a few days (more than the average time to get a block, I finally get one and something fails in the fraction of a second I get it.)  Strange.  Should I reinstall the program, or poclbm?  What is the ProcessBlock ACCEPTED message?  And then Flushing Wallet.dat?  Could someone on IRC disconnect me between the time the block was accepted at the server and the time I received confirmation?

1/6/2011 06:47 generated 50.00
keypool keep 2
AddToWallet ca8473cab6  new
MainFrameRepaint
SetBestChain: new best=0000000000039d487513  height=101264  work=533984385095310048
ProcessBlock: ACCEPTED
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
sending: inv (37 bytes)
DelayedRepaint
1/6/2011 06:47:08 Flushing wallet.dat
Flushed wallet.dat 120ms
keypool reserve 7
socket recv error 10053
disconnecting node

What I do is the following thing :
grep debug.log for the "generated" string from time to time

If some positive result comes out then i grep for "hash:" and check the hash against BBE, if it finds a block in BBE using my hash it means it made it into the blockchain, at that point I usually pet my cat with a satisfied smile on my face.

That block definitely failed to get into the chain for some reason.

Perhaps your network died for a while? Look at the logs between that section and the next SetBestChain message.

Hopefully I have no private keys in this log.  But here is the message and what follows after the hash in question:

BitcoinMiner:
proof-of-work found 
  hash: 0000000000039d4875136980d0530e739c9e0130cb2232802398c9a9567da334 
target: 00000000000404cb000000000000000000000000000000000000000000000000
CBlock(hash=0000000000039d487513, ver=1, hashPrevBlock=0000000000019592499d, hashMerkleRoot=77f14e4e72, nTime=1294296412, nBits=1b0404cb, nNonce=2805677112, vtx=7)
  CTransaction(hash=ca8473cab6, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 04cb04041b0144)
    CTxOut(nValue=50.00000000, scriptPubKey=048a9d2b4587e67450dd05fd53a754)
  CTransaction(hash=121f59470c, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(5a1a13c5da, 0), scriptSig=304402207f7fdb1dbb997d8d)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 0ecfb38199e1)
    CTxOut(nValue=330.60000000, scriptPubKey=OP_DUP OP_HASH160 673282ff376e)
  CTransaction(hash=d6138ac345, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(db6507c730, 0), scriptSig=3045022031d24dac31ab827d)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 2c0fc1281675)
    CTxOut(nValue=101.01000000, scriptPubKey=OP_DUP OP_HASH160 03aed3be01da)
  CTransaction(hash=867bd97731, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(71921aabcd, 1), scriptSig=3045022100a810227e08cdc5)
    CTxOut(nValue=4.15000000, scriptPubKey=OP_DUP OP_HASH160 6000794d415e)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 d4ad0d9df193)
  CTransaction(hash=a69f0fc99f, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(867bd97731, 0), scriptSig=30460221008c6f36cfd31df7)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 1f7995b575cb)
    CTxOut(nValue=4.10000000, scriptPubKey=OP_DUP OP_HASH160 99989a67caa8)
  CTransaction(hash=e11662207c, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(a69f0fc99f, 1), scriptSig=304402201b2280e5b771d3d7)
    CTxOut(nValue=4.05000000, scriptPubKey=OP_DUP OP_HASH160 d488c87d2a5f)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 22c90093e682)
  CTransaction(hash=b8b3603bb0, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(e11662207c, 0), scriptSig=3045022049b5c9d859e92bc8)
    CTxOut(nValue=4.00000000, scriptPubKey=OP_DUP OP_HASH160 dc3eeff5cdaa)
    CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 836ab0e197bf)
  vMerkleTree: ca8473cab6 121f59470c d6138ac345 867bd97731 a69f0fc99f e11662207c b8b3603bb0 6e42d24eed 86f01b907b 73425c01d7 0a0a969414 0b3f0586f0 75d1dd69d8 77f14e4e72
1/6/2011 06:47 generated 50.00
keypool keep 2
AddToWallet ca8473cab6  new
MainFrameRepaint
SetBestChain: new best=0000000000039d487513  height=101264  work=533984385095310048

If 00039d48 is part of the block hash, then the block didn't make it into the block chain, as a block with that hash doesn't exist. New blocks show up on BBE within 5 minutes, and they show up in your Bitcoin client after 1 additional block has been generated. Are you looking at the "all transactions" tab in the Bitcoin GUI? If you're using bitcoind, the block won't appear in your balance for 120 blocks.

Anything relevant in debug.log? Any "REORGANIZE" messages?

Thank you.  Bitcoin block explorer indicates the current block is 101270.  My client has been running for days and indicates the same block number.  I can accept that there may be no indication in the Bitcoin program yet, but checking blockexplorer.com and seeing that the time has come an gone for my apparent generation leads me to believe there is something wrong.  Does it take time to show up there?  After I solve a hash, I was under the impression that it was submitted immediately and somehow the next hash was predicated on mine.  I will re-read the FAQ but something feels wrong here.

Check your hash on bitcoin block explorer, and check whether 120 blocks have passed.
Generations have to mature 120 blocks before being available in the client, check the FAQ for more info.

After days at over 500mhash/s one of my two dos windows finally says "05/01/2011 22:47, 00039d48, accepted"
Thought this meant I finally made 50 Bitcoins.  However, it my Bitcoins program nothing came through at my current address of 1NCVXUZAgECmHu85PKHxuj5CEMumvZUT8C.
Went to blockexplorer.com and do not see anything generated at or around the corresponding UTC, which would be 06/01/2011 06:47.
What gives?  Did I not generate anything?