Topic: Since the beginning.... (Read 660 times)
I don't get it. Does it really matter?
Any proficient coder will code everything in Satoshi, not BTC.
this guy gets it
.. EVERYONE coding bitcoin should be coding the future halving as 1250000000 not 12.5Do you think this decimal will throw some things off? decimal sometime trigger code bugs. Since we haven't seen this decimal before, there may be a line of code somewhere that is not ready for it. Could be the end of Bitcoin as we know it.
Any proficient coder will code everything in Satoshi, not BTC.Exactly, 12.5 is actually 1250000000 Sats if i am not mistaken, so there actually is no decimal. This is a non issue
Do you think this decimal will throw some things off? decimal sometime trigger code bugs. Since we haven't seen this decimal before, there may be a line of code somewhere that is not ready for it. Could be the end of Bitcoin as we know it.
No, nearly all programs handle Satoshi-based amounts, and additionally have been handling non-integer Bitcoin amounts in all kinds of transactions (a coinbase transaction is processed by a lot of the same code paths as standard transactions, with some changes to validating inputs), *and* actual Coinbase transactions have been non-integer since the beginning of time (due to transaction fees being tacked on). Definitely a non-issue except for some specialty programs that shouldn't be being used anyway if they have these sorts of bugs.
Why to think so as lots of bitcoin in decimal are easily getting transacted with decimal and i think those block reward with decimal will also go through this transactions.
OP is a fud troll, and none of the threads he starts needs to be take seriously. I like some of his comments and I can see he is knowledgeable on the subject, but unfortunately he is batting for the
wrong side.
.... Why do people waste their time doing this? In any way... just responding to highlight the reason for this thread, before we get long debates on the merits of .5 ... I was also one of
the people, who prepared for the Y2K problems, and in the end it turned out that the world still went on...regardless. Bitcoin will do the same.
wrong side.
.... Why do people waste their time doing this? In any way... just responding to highlight the reason for this thread, before we get long debates on the merits of .5 ... I was also one of the people, who prepared for the Y2K problems, and in the end it turned out that the world still went on...regardless. Bitcoin will do the same.
Any proficient coder will code everything in Satoshi, not BTC.
this guy gets it
.. EVERYONE coding bitcoin should be coding the future halving as 1250000000 not 12.5 
As soon as I saw the name and avatar I knew this would be some completely obscure FUD thread. You never disappoint (well not literally of course, you're a real downer). Anyways, I doubt there's an issue and if there is it's not like it can never be patched. Satoshi seems to have known what (s)he/they was/were doing.
Anyone who does not know the difference between a float point and an integer will not be capable of writing code.
I think Machine code can handle it, Y2K was a non event
Do you think this decimal will throw some things off? decimal sometime trigger code bugs. Since we haven't seen this decimal before, there may be a line of code somewhere that is not ready for it. Could be the end of Bitcoin as we know it.
Any proficient coder will code everything in Satoshi, not BTC. 
Never before has there been even one moment in 7 years and since the genesis block that the value which is the total available number of bitcoin - ended in: '.5' Starting in July, 50% of the time, the total available number of bitcoin will end in .5
Do you think this decimal will throw some things off? decimal sometime trigger code bugs. Since we haven't seen this decimal before, there may be a line of code somewhere that is not ready for it. Could be the end of Bitcoin as we know it.
Do you think this decimal will throw some things off? decimal sometime trigger code bugs. Since we haven't seen this decimal before, there may be a line of code somewhere that is not ready for it. Could be the end of Bitcoin as we know it.
Jump to: