error message: "Unknown transaction type found"

[dooglus]

Each time I run "bitcoind listaccounts", I see the following in the debug log.  Does it indicate corruption somewhere in my ~/.bitcoin/ files, or is this an issue for everyone?  I'm running "Bitcoin version v0.7.1-dirty-beta".

[New Thread 0x7fffd5ebb700 (LWP 4331)]
ThreadRPCServer method=listaccounts
CWalletTx::GetAmounts: Unknown transaction type found, txid 18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
CWalletTx::GetAmounts: Unknown transaction type found, txid 18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
CWalletTx::GetAmounts: Unknown transaction type found, txid 1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a
CWalletTx::GetAmounts: Unknown transaction type found, txid 1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a
CWalletTx::GetAmounts: Unknown transaction type found, txid 2188367459f8ba3777851a30c4dce125f3687b91f25a402bf4696ba4892e8e2f
CWalletTx::GetAmounts: Unknown transaction type found, txid 2188367459f8ba3777851a30c4dce125f3687b91f25a402bf4696ba4892e8e2f
CWalletTx::GetAmounts: Unknown transaction type found, txid 24c23c401284d5862605b33bee5af83b29ca0cbd2fb5d60777443c5641e86cac
CWalletTx::GetAmounts: Unknown transaction type found, txid 24c23c401284d5862605b33bee5af83b29ca0cbd2fb5d60777443c5641e86cac
CWalletTx::GetAmounts: Unknown transaction type found, txid 25f7f2666444a2c51bffa206d5ee0a9a6a60442821999438d5e7c4a8a2f58102
CWalletTx::GetAmounts: Unknown transaction type found, txid 2f6add0d30e0f1a2850ed8f4ee6ca52b5e761755f8fe370e927aa698ede232e6
CWalletTx::GetAmounts: Unknown transaction type found, txid 3c5d4c5c6688765dccc66f021bce0da93a08a00cf04433423cadd272bbf8e0a6
CWalletTx::GetAmounts: Unknown transaction type found, txid 3c5d4c5c6688765dccc66f021bce0da93a08a00cf04433423cadd272bbf8e0a6
CWalletTx::GetAmounts: Unknown transaction type found, txid 42a7de54bde559189abadc4840e5c302500ae3e24993a6ac56a5dc012165b360
CWalletTx::GetAmounts: Unknown transaction type found, txid 42a7de54bde559189abadc4840e5c302500ae3e24993a6ac56a5dc012165b360
CWalletTx::GetAmounts: Unknown transaction type found, txid 4fb458365c6812f95ec65da50efa15723c5a32d74d73b244b91e4227d51ef61f
CWalletTx::GetAmounts: Unknown transaction type found, txid 64224740aa76870cfd9cb106e61c67e64c0b43cced74aad5f8c7e288ed2411f4
CWalletTx::GetAmounts: Unknown transaction type found, txid 64224740aa76870cfd9cb106e61c67e64c0b43cced74aad5f8c7e288ed2411f4
CWalletTx::GetAmounts: Unknown transaction type found, txid 69c51c806677c746279864a9af0266c42535192f916db7d5435689fa0913acbe
CWalletTx::GetAmounts: Unknown transaction type found, txid 6b814f3818cb1e4e852e7c21939913ae9d953af87acbf0fcc0d2b81e4ee6a017
CWalletTx::GetAmounts: Unknown transaction type found, txid 6b814f3818cb1e4e852e7c21939913ae9d953af87acbf0fcc0d2b81e4ee6a017
CWalletTx::GetAmounts: Unknown transaction type found, txid 6e6ef002501b1799ce8efab455fb6cf8c9f8af4aa8ea2e4a2249d3515819af93
CWalletTx::GetAmounts: Unknown transaction type found, txid 7249219f6d5174c26a2a8fd99d13a3f77ac4a47605c60f7ff9c966cea0376c64
CWalletTx::GetAmounts: Unknown transaction type found, txid 843206a626bdec9cd4ef171af2827e4ff9865697e38043c8aabd4658c5242b63
CWalletTx::GetAmounts: Unknown transaction type found, txid ad2ab11753a96e2ca9e161de2766ed93ae6f1d26f819c53449e35569fe13c824
CWalletTx::GetAmounts: Unknown transaction type found, txid ad2ab11753a96e2ca9e161de2766ed93ae6f1d26f819c53449e35569fe13c824
CWalletTx::GetAmounts: Unknown transaction type found, txid cc4fd1deb600ac51638b4a1df7aeed89861d4ae7705609624ac53cb8afe3276c
CWalletTx::GetAmounts: Unknown transaction type found, txid cc4fd1deb600ac51638b4a1df7aeed89861d4ae7705609624ac53cb8afe3276c
CWalletTx::GetAmounts: Unknown transaction type found, txid d042fa40b28d301d2543aa49ed9e088e1368ddd37620b0b6bc308cf233da4484
CWalletTx::GetAmounts: Unknown transaction type found, txid d042fa40b28d301d2543aa49ed9e088e1368ddd37620b0b6bc308cf233da4484
CWalletTx::GetAmounts: Unknown transaction type found, txid d4def5831b9bccca45d7c66facbcd539c6f094624deecfd6815b997b1a188de3
CWalletTx::GetAmounts: Unknown transaction type found, txid e0d39c8cbbc3e08ce0135997286abdca031fda1268c96789d6b3f606ddd58353
CWalletTx::GetAmounts: Unknown transaction type found, txid e534173252648b31cae7c217889d1b6660c1330be975b7f43be096f8911dcdea
CWalletTx::GetAmounts: Unknown transaction type found, txid f5db4913e9267caa4749de372b0f806c96320ad64aaa3bb441aac48afbaf05a5
[Thread 0x7fffd5ebb700 (LWP 4331) exited]

Edit: I just tried the official 64 bit linux Bitcoin version v0.7.2-beta (2012-12-10 09:47:37 -0500) binary, and get the same messages:

ThreadRPCServer method=listaccounts
CWalletTx::GetAmounts: Unknown transaction type found, txid 18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
CWalletTx::GetAmounts: Unknown transaction type found, txid 18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
CWalletTx::GetAmounts: Unknown transaction type found, txid 1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a
[...]

[1714998785]

1714998785

[1714998785]

1714998785

[DannyHamilton]

I assume you are mining in a pool that directly shares the outputs of the coinbase transaction with the miners?

It looks that those txid are for coinbase transactions (which have no previous unspent transaction for the input):

http://blockchain.info/tx-index/3186812/18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
http://blockchain.info/tx-index/2677722/1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a

[CIYAM]

Interesting - at the top of both of those tx's the following appears on blockchain.info:

Unable to decode input address (followed by a small BTC amount)

and looking at the "Output Scripts" the script for the above reads as this:

Code:

OP_IFDUP OP_IF OP_2SWAP OP_VERIFY OP_2OVER OP_DEPTH 

Strange indeed.

There is another "unable to decode output" at the end of the list (with 0 BTC which perhaps makes more sense as being some sort of message to "identify" the mining pool?).

[dooglus]

I assume you are mining in a pool that directly shares the outputs of the coinbase transaction with the miners?

It looks that those txid are for coinbase transactions (which have no previous unspent transaction for the input):

http://blockchain.info/tx-index/3186812/18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
http://blockchain.info/tx-index/2677722/1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a

I'm not mining at all.  I did CPU mine at P2Pool for a couple of weeks when I first found out about it, so that could be it.

[kjj]

I assume you are mining in a pool that directly shares the outputs of the coinbase transaction with the miners?

It looks that those txid are for coinbase transactions (which have no previous unspent transaction for the input):

http://blockchain.info/tx-index/3186812/18a25ea05fc65beeb4d70da83bded52a0e616f15ee1cf85f9b924c84b98cd0bf
http://blockchain.info/tx-index/2677722/1970274786f4040e41ff46282f13c0bd47a38300c07ffb7bde59fc8dd95bcb4a

I'm not mining at all.  I did CPU mine at P2Pool for a couple of weeks when I first found out about it, so that could be it.

Basically, when listtransactions runs, it looks at every output of every transaction that you are involved in, even the outputs that are not yours.  This causes these messages to show up in your logs, because p2pool uses a bogus txout for internal pool tracking.

See here and here.

[Peter Todd]

Basically, when listtransactions runs, it looks at every output of every transaction that you are involved in, even the outputs that are not yours.  This causes these messages to show up in your logs, because p2pool uses a bogus txout for internal pool tracking.

That's pretty much it, although FWIW the particularly odd scriptPubKey posted above, "OP_IFDUP OP_IF OP_2SWAP OP_VERIFY OP_2OVER OP_DEPTH", was actually created by an old bug in P2Pool where one of the scriptPubKeys was being set to the data "script" rather than a proper serialized script. The "OP_IFDUP" etc. happens to be what that string decodes to in op-codes. The bug has been long since fixed, but the OP did mention they mined at p2pool some time ago.

[dooglus]

That's pretty much it, although FWIW the particularly odd scriptPubKey posted above, "OP_IFDUP OP_IF OP_2SWAP OP_VERIFY OP_2OVER OP_DEPTH", was actually created by an old bug in P2Pool where one of the scriptPubKeys was being set to the data "script" rather than a proper serialized script. The "OP_IFDUP" etc. happens to be what that string decodes to in op-codes. The bug has been long since fixed, but the OP did mention they mined at p2pool some time ago.

Thanks.  That's reassuring.

I keep switching between client versions 0.7.x and 0.8.x and thought maybe that had corrupted something.