Bitcoin Forum
May 09, 2024, 08:50:44 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Odd transaction at height 72785  (Read 7490 times)
lfm (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 104



View Profile
August 28, 2010, 09:27:13 AM
 #1

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.
1715287844
Hero Member
*
Offline Offline

Posts: 1715287844

View Profile Personal Message (Offline)

Ignore
1715287844
Reply with quote  #2

1715287844
Report to moderator
Every time a block is mined, a certain amount of BTC (called the subsidy) is created out of thin air and given to the miner. The subsidy halves every four years and will reach 0 in about 130 years.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715287844
Hero Member
*
Offline Offline

Posts: 1715287844

View Profile Personal Message (Offline)

Ignore
1715287844
Reply with quote  #2

1715287844
Report to moderator
FreeMoney
Legendary
*
Offline Offline

Activity: 1246
Merit: 1014


Strength in numbers


View Profile WWW
August 28, 2010, 09:37:02 AM
 #2

I don't see the problem with someone making a little pi.

Play Bitcoin Poker at sealswithclubs.eu. We're active and open to everyone.
theymos
Administrator
Legendary
*
Offline Offline

Activity: 5194
Merit: 12982


View Profile
August 28, 2010, 09:50:40 AM
Last edit: August 28, 2010, 10:01:26 AM by theymos
 #3

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)

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
jgarzik
Legendary
*
qt
Offline Offline

Activity: 1596
Merit: 1091


View Profile
August 28, 2010, 05:23:55 PM
 #4

Full block dump, in case anyone's curious: http://blk.bitcoinwatch.com/b?h=72785

Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own.
Visit bloq.com / metronome.io
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!