Title: Block generated but generation fee not redeemed
Post by: yomi on April 18, 2011, 11:29:23 PM
I was just having a look into my debug.log file when I found what it seems like a generated block: BitcoinMiner:
proof-of-work found
hash: 0000000000004225d5316fa17bd9cd12c405a796c16bfe59327c6f65e748c5c7
target: 000000000000b5ac000000000000000000000000000000000000000000000000
CBlock(hash=0000000000004225d531, ver=1, hashPrevBlock=00000000000043e6cf34, hashMerkleRoot=6ba844b126, nTime=1303156535, nBits=1b00b5ac, nNonce=3917021259, vtx=20)
CTransaction(hash=47bc44f881, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 04acb5001b010b)
CTxOut(nValue=50.08000000, scriptPubKey=04585b1b402cbc105f5a82ca022c93)
<<<<transaction data snipped>>>>
CTransaction(hash=dc0bc807b3, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(34623a4817, 0), scriptSig=304402206c90841f3405a7c1)
CTxOut(nValue=0.76000000, scriptPubKey=OP_DUP OP_HASH160 66804ace4055)
CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 b0caa9e7d2a0)
CTransaction(hash=fcbcabac9f, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(cee9ed21b8, 0), scriptSig=30460221008b3a65450f9b6d)
CTxOut(nValue=0.70000000, scriptPubKey=OP_DUP OP_HASH160 96c35b727f6e)
CTxOut(nValue=0.05000000, scriptPubKey=OP_DUP OP_HASH160 42a3da3bbecd)
vMerkleTree: 47bc44f881 f6a2a0a2ba ec8479e1ab 7c43e1cf75 a80c404703 8357961bc1 cff1453104 7bb5b16dd5 38393961c1 3c6c1ffbae a0c760ce74 779451433f 047647e415 a29e5277e5 441e61fbda 99f3bec85d a886a15fac cd4be90f7a dc0bc807b3 fcbcabac9f 44762b8c48 235d393621 4dba46ffd8 939bca5c5c 589d6adfa3 46a0d4384f 855d4527f5 8850ac1c90 53c6951424 991de7c094 3b7b4773a7 5b2f9efc1b 1dc6383da2 d3e570e71b d837abe7cf 7176a93fc6 432aee8108 ab947f48c7 0f5506c42b d2b07996c1 6ba844b126
04/18/11 19:55 generated 50.08
keypool keep 4
AddToWallet 47bc44f881 new
SetBestChain: new best=0000000000004225d531 height=119022 work=4016359213689394764
ProcessBlock: ACCEPTED
However it seems the 50.08 have not appeared in the client balance yet: {
"version" : 32002,
"balance" : 0.00000000,
"blocks" : 119044,
"connections" : 23,
"proxy" : "",
"generate" : false,
"genproclimit" : -1,
"difficulty" : 92347.59095209,
"hashespersec" : 0,
"testnet" : false,
"keypoololdest" : 1300848900,
"paytxfee" : 0.00000000,
"errors" : ""
}When I check the transaction 47bc44f881 in blockexplorer I see that in the transaction Input is "Not yet redeemed" (http://blockexplorer.com/t/3ifsT3nVix (http://blockexplorer.com/t/3ifsT3nVix)) Anything this newbie is missing? Thanks!
Title: Re: Block generated but generation fee not redeemed
Post by: xf2_org on April 18, 2011, 11:50:07 PM
You must wait 120 blocks, before it "matures."
Title: Re: Block generated but generation fee not redeemed
Post by: BitterTea on April 18, 2011, 11:53:43 PM
Immature generation transactions currently do not show up in JSON-RPC queries. There is a patch to fix this, and it will probably make its way to the official client in the next few releases.
Title: Re: Block generated but generation fee not redeemed
Post by: yomi on April 19, 2011, 12:15:53 AM
Thank you for your answers.
I found some posts relevant to this, I am posting them for reference:
https://www.bitcoin.org/smf/index.php?topic=6.0 (https://www.bitcoin.org/smf/index.php?topic=6.0)
http://newlibertystandard.wetpaint.com/thread/3482241/how+much+blocks+I+need+to+generate+1+bitcoin%3F (http://newlibertystandard.wetpaint.com/thread/3482241/how+much+blocks+I+need+to+generate+1+bitcoin%3F)
Maybe it would be useful to add this info about maturity to the FAQ?
|