rfm8qDyXWgbGxpmMSuY9SDmWLdmMgRsDxR

debug print
Debit: -50.02
Debit: -50.00
Debit: -50.02
Debit: -50.01
Debit: -300.03
Debit: -50.03
Transaction:
CTransaction(hash=273c0d99c7, ver=1, vin.size=6, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(20bdd89081, 0), scriptSig=3045022100e37c0025aef854)
   CTxIn(COutPoint(88e17fa511, 0), scriptSig=304402204ce8a816ef95248b)
   CTxIn(COutPoint(24c31d07af, 0), scriptSig=30450220159e1732288d839a)
   CTxIn(COutPoint(305ba6490e, 0), scriptSig=3046022100e864131dea9f2f)
   CTxIn(COutPoint(913d37f326, 0), scriptSig=30450221009efd4e87eef1fe)
   CTxIn(COutPoint(6bc4c1625d, 0), scriptSig=3045022067621e5a25b3465d)
   CTxOut(nValue=550.11000000, scriptPubKey=OP_DUP OP_HASH160 ac827171a9e5)
Inputs:
CTransaction(hash=20bdd89081, ver=1, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, -1), coinbase 0439f3001b0105)
   CTxOut(nValue=50.02000000, scriptPubKey=04123a18511590ce452512da795c65)
   2979 confirmations, IsMine=true
CTransaction(hash=88e17fa511, ver=1, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, -1), coinbase 04bdcb001b0164)
   CTxOut(nValue=50.00000000, scriptPubKey=0433a01b276566b0c204240e7971f2)
   1244 confirmations, IsMine=true
CTransaction(hash=24c31d07af, ver=1, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, -1), coinbase 04bdcb001b0116)
   CTxOut(nValue=50.02000000, scriptPubKey=04f5e35e524a4cd2a54c23151f4f77)
   1083 confirmations, IsMine=true
CTransaction(hash=305ba6490e, ver=1, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, -1), coinbase 0439f3001b017e)
   CTxOut(nValue=50.01000000, scriptPubKey=04dce39a423f5226a731265c7ac4fd)
   1818 confirmations, IsMine=true
CTransaction(hash=913d37f326, ver=1, vin.size=4, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(959236d510, 0), scriptSig=3044022026ad025871b52466)
   CTxIn(COutPoint(14c0710fc4, 0), scriptSig=304402201846dec2e568e386)
   CTxIn(COutPoint(b6dbb15b5b, 0), scriptSig=3046022100a1072d49190a52)
   CTxIn(COutPoint(b81aa56189, 0), scriptSig=3046022100f7966df37b596b)
   CTxOut(nValue=300.03000000, scriptPubKey=OP_DUP OP_HASH160 77d1c18b3d91)
   2427 confirmations, IsMine=true
CTransaction(hash=6bc4c1625d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
   CTxIn(COutPoint(0000000000, -1), coinbase 0439f3001b0123)
   CTxOut(nValue=50.03000000, scriptPubKey=044070f54a39b1379840e033624487)
   2173 confirmations, IsMine=true

caveden:

yea, the transaction does not appear in that list. and it has been days...

theGeck:

what does that rescan switch do? would it resend those tranasctions back out to the network?

I have a transaction that is stuck at zero confirmations. It has been like this for days (2-3). The transaction does not show up anywhere on blockexplorer or in the active list at bitcoincharts.

The app version is 3.19 on windows xp.

The current idea is to kill the block chain and let it download (no idea what else to do). Has anyone ran into this before?

Anyone seen this before?


Nothing specific was done to generate this. It just sat there idle (with full chain downloaded) and then this. After the error no more blocks are downloaded

Someone came in with a large amount of GPU power that day. I noticed the dent in my own GPU production as well.

Ok...so false alarm. Sorry to create forum spam.

The motherboard i switched to had screwed up time on it. I believe the effects of this are documented. NTP never updated until i set the time reasonably close to actual. I simply didn't notice it. So, it rejected all the blocks i created because they were from the future and wasn't taking any new blocks in from the network. I only noticed this because i was doing some calculations with block count and realized it hasn't changed.

I'm not sure how this is possible either. i am stunned. it was only a few hundred btc so not too bad, but still...

I shut down bitcoin client, shut down windows, all good and proper. Bizarre...

So, i swapped out my motherboard for a newer one. Rest of the setup stayed the same. I restart the machine, windows xp boots up, discovers the hardware, reconfigures, all is good. I start up bitcoin....all my coins are gone. Why did this happen?

The total amount of bitcoins will be 21 million. Lets say i hold in my wallet 5 million bitcoins. I proceed to lose my wallet. I understand that i lose my bitcoins and am now broke. However, does that mean that the total circulation of bitcoins is now 16million?

If so then, technically, the system 'leaks' bitcoins.
Maybe i'm misunderstanding how this all works. Can someone shed some light?

Hey all...Thanks for all the feedback

The ssh method is great. However, all the machines are windows machines so i'd have to do an install on all of them. Better than writing a proxy app for sure though...

I saw the entry from a few weeks ago about the -rpcallowip switch. I'll compile my own version if i have to. That said, i'd prefer to have an official release. Anyone have an idea when the next version would be posted?

As far as the MITM attack possibility, this only presents a problem if the network i'm exposing to is not trusted. Or is there some other effect i'm missing?

Hello,

I'm have a client that calls getinfo over the rpc interface. Everything works fine when host=localhost.
However, when trying to get bitcoin at another host i cannot.
I read the wiki and it says the interface only accepts requests from 127.0.0.1. Is this still the case? Is there a setting to override this?

If not, i'm probably going to have to write a 'proxy' app that i would deploy to each machine running bitcoin. Would prefer not to do this

Thanks,
Marko