Transaction Address and Type not showed in Bitcoin-qt #2675

Transaction Address and Type not showed in Bitcoin-qt

It's transaction 4e951a8251e70b0036852a786c862ed6aae5ecd3acb741b4a4823a2f0ddc376d

I've no idea why it is so. Maybe damaged blockchain data on HDD? But db.log is empty. I started it with -debug, here debug.log

I'm using Windows 8 with Bitcoin v0.8.1-beta

about transaction also doesn't show address

Status: 7475 confirmations
Date: 04.04.2013. 05:27
Debit: -0.00024 BTC
Debit: -0.00016 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00005055 BTC
Debit: -0.0001 BTC
Debit: -0.00000636 BTC
Debit: -0.00005 BTC
Debit: -0.01278688 BTC
Net amount: -0.01395379 BTC
Transaction ID: 4e951a8251e70b0036852a786c862ed6aae5ecd3acb741b4a4823a2f0ddc376d



Debug information

Debit: -0.00024 BTC
Debit: -0.00016 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00008 BTC
Debit: -0.00005055 BTC
Debit: -0.0001 BTC
Debit: -0.00000636 BTC
Debit: -0.00005 BTC
Debit: -0.01278688 BTC

Transaction:
CTransaction(hash=4e951a8251, ver=1, vin.size=19, vout.size=1, nLockTime=0)
CTxIn(COutPoint(7f51e53614, 170), scriptSig=3045022000f1a42b1b3443f5)
CTxIn(COutPoint(a1f5faaa2b, 11), scriptSig=3046022100a53624b246efc4)
CTxIn(COutPoint(b9f85b6306, 12), scriptSig=3044022060b1e437937a45a7)
CTxIn(COutPoint(8e91ae98c5, 2), scriptSig=3046022100ae116cacabbfe5)
CTxIn(COutPoint(b3bc094b85, 3), scriptSig=3044022008b6c475b6d148d1)
CTxIn(COutPoint(412c4e7ba6, 10), scriptSig=3046022100ecdc801f576326)
CTxIn(COutPoint(52c969b300, 9), scriptSig=30450220412efb3d53d402ef)
CTxIn(COutPoint(e3a34f771c, 9), scriptSig=3045022030890f79388b27a5)
CTxIn(COutPoint(17ec4e3d18, 15), scriptSig=30440220494f6a76196b9a86)
CTxIn(COutPoint(4122441323, 2), scriptSig=3045022057f3620c1550c1da)
CTxIn(COutPoint(256f3819ff, 8), scriptSig=304402206ee486e3379a80e2)
CTxIn(COutPoint(1c312e283c, 8), scriptSig=3046022100ef1a1bf46a13d4)
CTxIn(COutPoint(6e20454482, 6), scriptSig=3045022004deb779471faf08)
CTxIn(COutPoint(7ea97dfd45, 17), scriptSig=304402204b3b6c5aa2424787)
CTxIn(COutPoint(3ed5396961, 62), scriptSig=3046022100b496e7472ef37c)
CTxIn(COutPoint(4042646189, 239), scriptSig=3045022100cbe688b94ba2a7)
CTxIn(COutPoint(5aa598d711, 336), scriptSig=30460221008276035b9b0aae)
CTxIn(COutPoint(5ebda707bb, 175), scriptSig=3046022100ab154a12811bec)
CTxIn(COutPoint(ddfec4cfb9, 1), scriptSig=30440220228bc2036549172d)
CTxOut(nValue=0.01438379, scriptPubKey=OP_DUP OP_HASH160 9d3f4e238204)

Inputs:
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false
Amount=-0.00000001 BTC IsMine=false

it's same using newest test/bitcoin-0.8.2rc1-win32

It looks like it doesn't recognize neither of the inputs or outputs as belonging to you, so it has no idea what to do with the transaction.

What kind of transaction was it before things got corrupted?

It's only so for this transaction, others seem normal.

Actually I think I know why, maybe because I sent this transaction from blockchain.info and my bitcoin-qt wallet doesn't have some of private keys which was used, but it shows correctly it in red as spent only there's not all amount.

That indeed explains it, if you use your wallet in multiple locations or multiple clients, things such as this may happen. That's why we strongly recommend against it.

@laanwj Perhaps we should add some category for this type of transaction, so we at least show something and not just nothing?

Well, it's quite easy. There's inputs with some addresses known to be my and output which isn't. So basically to spend from those addresses I would have had their keys even if they aren't in my wallet currently. We can safely assume that even if there's single known address they all belong to user.

Ok, at least it's explained, nothing more to do here, closing the issue. @diapolo this is not something that happens with normal use of the software, so fixing this has no priority. I'm already happy that it's robust against this and that it doesn't trigger some assertion.

I wouldn't agree that it's not normal use. I didn't do anything with Bitcoin-qt, I just spent BTC from elsewhere including some other addresses. And it's quite confusing behavior in Bitcoin-qt part, but ok.

You should never use the same private keys that you use in bitcoin-qt somewhere else. This is not supported. Private keys are supposed to be private to one wallet only. You're of course free to ignore any advice and do otherwise, but what happens is your own risk.

Says who?

Why can't this be supported? On May 20, 2013 11:53 PM, "Wladimir J. van der Laan" < notifications@github.com> wrote:

You should never use the same private keys that you use in bitcoin-qt somewhere else. This is not supported. Private keys are supposed to be private to one wallet only. You're of course free to ignore any advice and do otherwise, but what happens is your own risk.

— Reply to this email directly or view it on GitHubhttps://github.com/bitcoin/bitcoin/issues/2675#issuecomment-18158419 .