Full block dump, in case anyone's curious: http://blk.bitcoinwatch.com/b?h=72785
Topic: Odd transaction at height 72785 (Read 7489 times)
You have to modify your client to make a higher-precision transaction like this, but the change isn't difficult. It's not a problem. I'd be surprised if this hasn't been done before.
Code:
CTransaction(hash=65c356, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(893335, 0), scriptSig=0x01B8C315FD58F0DFA0DEA2)
CTxOut(nValue=1.85850000, scriptPubKey=OP_DUP OP_HASH160 0x3181)
CTxOut(nValue=3.14150000, scriptPubKey=OP_DUP OP_HASH160 0xF99E)
I don't see the problem with someone making a little pi.
In block #72785 with timestamp 2010-08-07 04:53:03:
If the block genenerated 50 BTC is transaction #0 of block #72785 then transaction #3 is kinda odd. It takes an input of 5.00 BTC and splits it to two outputs of value 1.8585 BTC and 3.1415 BTC. I think it is the only transaction that is not an even number of bitcents. There is no fee associated.
Is there any serious consequences to this transaction?
Was it necessary to use a customized client to produce this transaction?
So far as I can figure it is harmless but I thought I might bring it up here anyway.
If the block genenerated 50 BTC is transaction #0 of block #72785 then transaction #3 is kinda odd. It takes an input of 5.00 BTC and splits it to two outputs of value 1.8585 BTC and 3.1415 BTC. I think it is the only transaction that is not an even number of bitcents. There is no fee associated.
Is there any serious consequences to this transaction?
Was it necessary to use a customized client to produce this transaction?
So far as I can figure it is harmless but I thought I might bring it up here anyway.
Jump to: