Pages:
Author

Topic: Bitcoin decimals. Is 1.00000000 Bitcoin the same as 1.000000000000 Bitcoin? (Read 485 times)

sr. member
Activity: 1587
Merit: 271
Enterapp Pre-Sale Live
While answering in another thread, this debate came up in my mind about Bitcoin and decimals.  Curious to know what the general user thinks.

Say inflation was so crazy 1 Satoshi became $1 and a Hard Fork took place through which we add more decimals to Bitcoin.  It currently has 8.  If we add 4 more decimals, is 1 Bitcoin still just as scarce or do you consider it artificial injection of supply?

-
Regards,
PrivacyG
How is it possible that Bitcoin will get additional decimals, when the limit has been determined up to 1 Bitcoin equals 100 million Satoshis. If mining has reached the maximum supply limit, which is 21 million Bitcoins, of course we can calculate the total market capitalization at a price of $ 1 for 1 Satoshi.
If I'm not mistaken in my calculations or the reading of the text is:  21.000.000 BTC x  100.000.000 SATS = $2.100.000.000.000.000 USD (Two quardrillion one hundred trillion dollars).
If there is an additional of decimals, it is certainly worth asking about the legitimacy of the Bitcoin.
Maybe it's different with Bitcoin which is developed in the form of tokens from certain blockchains with a decimal number of 18. For example HBTC and BTCB. Although the decimal number is 18, the legal limit for transactions has been set at 8 digits set in the contract code.
Maybe this is what I understand in terms of Bitcoin decimals. Bitcoin developed by Satoshi Nakamoto cannot be tampered with by anyone, either in terms of adding decimals or increasing the amount of supply.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L66
Quote
66        consensus.nSubsidyHalvingInterval = 210000;
What I meant is that there isn't a rule that limits the number of halvings to 32. Take that parameter, and go on validation.cpp#L1470. It says that if halvings are greater than 64, return 0. The halving that leaves us with 1 satoshi as subsidy is the 32nd. We can expand halvings without invalidating a rule.

if devs messed with the amount of units. to change the reward at unit level
Ever thought that a hard fork can occur and count after a specific block and not for the previous?
legendary
Activity: 4410
Merit: 4788
while waiting for the idiots to finally read some code and run some scenarios in regard to changing the units of measure to fit their fantasy of "more decimals".. and realise that it does change things..

EG again
a change of
bin:10010101000000101111100100000
hex:12A05F20
dec:312500000
but instead
bin: 100100011000010011100111001010100000000
hex: 48C2739500
dec: 312500000000

lets just address another thing they dont know/understand

it also breaks the halving cycles rule
Take a breath, calm down, sit and hear this: there is no halving cycle rule.
https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L66
Quote
66        consensus.nSubsidyHalvingInterval = 210000;

oh and by the way
https://github.com/bitcoin/bitcoin/blob/e9262ea32a6e1d364fb7974844fadc36f931f8c6/src/chainparams.cpp#L18
Quote
static CBlock CreateGenesisBlock(const char* pszTimestamp, const CScript& genesisOutputScript, uint32_t nTime, uint32_t nNonce, uint32_t nBits, int32_t nVersion, const CAmount& genesisReward)

the genesis block has 5000000000 as genesis reward as a real number thats hashed

if devs messed with the amount of units. to change the reward at unit level and thus changes the
"coin" from 100,000,000 to a larger number
https://github.com/bitcoin/bitcoin/blob/e9262ea32a6e1d364fb7974844fadc36f931f8c6/src/chainparams.cpp#L435
Quote
genesis = CreateGenesisBlock(1296688602, 2, 0x207fffff, 1, 50 * COIN);
  consensus.hashGenesisBlock = genesis.GetHash();
that would result in a different hash, and so the hashes wont match thus its no longer the bitcoin genesis hash seed

so do the math.. it might help you see where all the changes will affect alot of things and need to have more cludgy code to work around such things like fake count a reward of real immutable historic units 5000000000 in one count but call it 5000000000000 elsewhere but also 5000000000 in another spot just to prevent bugs as also valid in another fake count as the larger number to not bug out the other place .. in short miscount hard amounts to avoid bugs but then causing bugs by the miscounting
legendary
Activity: 4410
Merit: 4788
oeleo
you really need to try one day to apply math., logic. code and data..

your silly narrative always lacks this

so i set you the challenge too

go look at block data of say the 2009-2012 first 210k blocks

actually look at the coinbase value at data level
note:
bin:100101010000001011111001000000000
hex:12A05F200
dec:5000000000

now. try to change these so that you get your "extra decimals"
oh wait you cant. they are in a immutible blockchain..

now lets pretend at the 2024 halving code rules changed where the block reward was no longer
(GUI view) 3.1250000
but instead
(GUI view) 3.1250000000
which would result at data level of being
a change of
bin:10010101000000101111100100000
hex:12A05F20
dec:312500000
but instead
bin: 100100011000010011100111001010100000000
hex: 48C2739500
dec: 312500000000

and see the results when you play it forward of how many shareable units there and how it has diluted the 2009-2012 first 210k block value of 10.5m to being considered as 105,000 "new bitcoin" mined in 2009-2012

and then i want you to work out how many halvings are then occuring compared to the hard rules invented in 2009.

and then i want you to count up how many shareable units will be created in total,

..
yes im calling you out to apply some math, logic and understanding. to actually look outside your dream box of GUI displays of "it doesnt matter" and look at the real impact at code and data level of REAL data and shareable units and change of the infamous "21m supply"

goodluck

dont reply with ignorance arrogance, insults or just avoiding the concepts of the differences between

GUI: 50.00000000
bin:100101010000001011111001000000000
hex:12A05F200
dec:5000000000
vs
GUI: 50.00000000000
bin:1001000110000100111001110010101000000000000
hex:48C27395000
dec:5000000000000

which cannot be changed due to immutible blockchain

versus
GUI: 3.12500000
bin:10010101000000101111100100000
hex:12A05F20
dec:312500000
but instead
GUI: 3.12500000000
bin: 100100011000010011100111001010100000000
hex: 48C2739500
dec: 312500000000

which can be change..
where you have been implying "nothing breaks, its insignificant, blah crap, insult, ignore it"
legendary
Activity: 2268
Merit: 18748
it changes the number of halving events
You keep repeating this like it is a foregone conclusion, but it would be trivial to cap the number of halving events to ensure that the final supply is not changed. And even if this wasn't done, the difference from the rounding errors of 1 sat being the smallest unit compared to 1 millisat being the smallest unit are trivial. As things stand, the final number of bitcoin mined will be 20,999,999.97690000. If we converted to millisats before the first halving which it would matter (the 10th halving, which goes from 0.09765625 BTC to 0.04882812 BTC), then the final number of bitcoin mined will be 20,999,999.99997060. The "new bitcoin" as you put it would amount to around 0.02 BTC, and all your nonsense about 1.3 million new bitcoin is obviously just that - complete nonsense.
legendary
Activity: 4410
Merit: 4788
how ever thats the human conversation. not the actual rule at data level
You can check it on consensus/amount.h and see it yourself that one bitcoin is an actual unit of the system. You can also check yourself that the 21 million rule applies in line 26, wherein MAX_MONEY (which is used for sanity purposes only) is 21 million times COIN.

waste as much time as you like. or actually realise that things are not actually measured in bitcoins at rule/code/data level of the actual protocol
I know what's a satoshi, thanks for the kind clarification. I'm just saying that this line doesn't stop us from expanding the decimals. The total satoshis can remain 2,099,999,997,690,000.

hard rule peg you forgot to include in your manipulate ignorance
Quote

now go check the blockchain data of 13 years of ACTUAL data!!!

i dare you to look at the data.. of actual decentralised immutable blockchain data.. and then change the peg and see the result of the value and the amount "COIN" that enters supply when you change the 100000000 peg

..
now once you realise it does change the halving events and total supply amounts by changing the peg..

then do yourself another learning experience favour
go read the blockchain data again.. and show me anywhere in raw tx form where "COIN" is shown on the blockchain

realise "COIN" is the human expression for human display at GUI level. its not actually a hard rule

the real hard rule is starting from 5000000000 units from genesis for 210,000 blocks then halves
and you will see this truth by looking at the actual blockchain data. not the bastardised visual aid math cludge of software developers playing mind games

stick to what real hard data shows and not some silly comment you read in some comment section mis representing the hard rules

last lesson. stop sounding like a doomad echo.. your not helping yourself or anyone.



dont even bother responding unless you can come back with answers about the raw data of bitcoin involving a 2009-2012 coinbase reward in either:
bin:100101010000001011111001000000000
hex:12A05F200
dec:5000000000

where you can actually articulate these answers in a way that changing the peg will not affect the answer nor change the conversational basket terms of "coin" "btc" form, nor change the number of halving events nor change the total supply of sharable units

and do not respond just to sound like the drama queen hysterical insults i usually hear you repeat from doomads selection of insults.. just so you can avoid doing the research

in short do the research and learn something and come back with proper researched and calculated response of actual data
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
how ever thats the human conversation. not the actual rule at data level
You can check it on consensus/amount.h and see it yourself that one bitcoin is an actual unit of the system. You can also check yourself that the 21 million rule applies in line 26, wherein MAX_MONEY (which is used for sanity purposes only) is 21 million times COIN.

waste as much time as you like. or actually realise that things are not actually measured in bitcoins at rule/code/data level of the actual protocol
I know what's a satoshi, thanks for the kind clarification. I'm just saying that this line doesn't stop us from expanding the decimals. The total satoshis can remain 2,099,999,997,690,000.
legendary
Activity: 4410
Merit: 4788
black hat

there is no 21m hard rule at the real protocol level, its a conversational thing of interpretation

there is hard rule but not what you think
much like the block time rule is not actually a 10min rule..
its actually a target of 2016blocks per fort night. which translates for human display/conversation as being a "10 minute rule"
do you get the difference between actual protocol vs human expression/display

and so the actual protocol is this:
5000000000 units starting from block1 for 210,000 blocks
which then halves
yep there is a half the number of units...

by which time in roughly the year 2140
there will be
2,099,999,997,690,000 units

where by then the units FOR human interpretation of visual aid/conversation
then calculates that to being units /100,000,000 =
1btc= 100,000,000 units where the human conversation/display becomes
"21m million btc rule"

how ever thats the human conversation. not the actual rule at data level

the unit * /100,000,000 is a peg that is something people for years deemed a hard rule and hard protocol thing that should not be broke because it changes too many things and devalues and breaks alot of things by changing it

i truly dare you to actually find a transaction anywhere on the blockchain where at true data level(not human visual manipulation.. but actual data level) where a block reward in 2009-2012 was just the number "50"

waste as much time as you like. or actually realise that things are not actually measured in bitcoins at rule/code/data level of the actual protocol

so dont confuse human display stuff of conversation with actual rules

breaking the peg of sat to btc.. is going to break alot of things


thinkig that changing the 100,000,000 beg rate of sat(smallest unit to btc) to different numbers is of no concern where you group of malicious malcontents think it harms no one but only 1 undividual is completely wrong too (yes im linking in the other network of same conversation to make a wider point)

if one group of users want it to remain 100,000,000 math and another group want 100,000,000,000
then when one side wants "1btc" for $16k from both sides

guess what they both send different amounts of sub units
or when one group sends out the same sub units to different groups thinking they are paying the same amount. guess what other wallets will see they received different amount of "btc" one being 1000x less than the other


legendary
Activity: 3472
Merit: 10611
If Bitcoin development to the point where 1 Satoshi equals 1 USD that means an increase in demand,
It could also mean USD has lost its value and with the way they are printing it, that's not going to be far Tongue
1 Satoshi is already about 1 GNF (Guinean Franc).

Doing that would require a total blockchain data rewrite, something blockchain was designed to prevent.
Not necessarily. It is just data interpretation which means we could keep the blockchain files and transaction structure intact up to the point of the fork and deserialize it as before, but introduce new deserialization rules for any new blocks that come along. Somewhat similar to how we implemented SegWit.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
Say inflation was so crazy 1 Satoshi became $1 and a Hard Fork took place through which we add more decimals to Bitcoin.  It currently has 8.  If we add 4 more decimals, is 1 Bitcoin still just as scarce or do you consider it artificial injection of supply?
Yes. The 8 decimals isn't a strict protocol rule that affects monetary policy. Nobody ever promised there will be 8 forever. The only thing that's being said is that there won't be more than 21 million coins. Whether we have 8, 12 or infinite decimals, the 21 million rule is enforced. The fact that we'd have a few more coins in each decimal increase doesn't violate that rule.

it also breaks the halving cycles ru;le
Take a breath, calm down, sit and hear this: there is no halving cycle rule.
legendary
Activity: 4410
Merit: 4788
Adding more zeros to bitcoin will not change anything,

read some code. look at blockchain data..
look at how things need to change to get the "extra decimals"

dont just think from the prospective of the GUI

actually learn what is actual happening at the real rule and data level
breaking the rules to have more units at data level changes ALOT

it changes the number of halving events
it dilutes the 19m 'btc' to appear as 190k btc
meaning the "new btc" mined ends up as about 1.3m(1,332,187) btc at the end of all halvings in 2180

please do some maths and look at the data

check this post..
then read some code. check block data. and see how it actually changes..
.. surprise yourself by learning something
legendary
Activity: 3346
Merit: 3125
Adding more zeros to bitcoin will not change anything, the total amount of bitcoin will be 21 million... And seeing 1 satoshi in $1 is an impossible scenario.

But is important to mention that some services already added more zeros on bitcoin for practical proposes. Here is a good example, go to coinmarketcap and look at the dogecoin prize, there you will see:

1 doge = 0.000004113

That's right, 9 digits after the dot... For trading and markets, this is a good option for better manipulation.
legendary
Activity: 4410
Merit: 4788
I don't know why Core developers decided to invent a new size metric "vbytes", considering that only the scriptSig and some other fields are excluded from the byte calculation. IMO it would've been better to use the terms "transaction fee (legacy)" and "transaction fee (segwit)" and then keep the byte metric, but I guess it's much too late for that now.

the reason is simple.. dev politics

the scaling bitcoin was about increasing transaction count..
the debate then became named "blocksize" debate

one side wanted more transaction utility on the blockchain.
the other side wanted to make it look like the first side just wanted more data bloat without more transaction utility

hence throwing around useless names like "big blocker" rather than calling the desires what they were.. more transactions on chain

so core used the cludgy math of miscounting bytes to "break outside the 1mb blocksize" without actually truly giving any increase in transaction count potential.,
because in their view saying they are offering "4mb blocksize" aka bigger blocks.. which in their mind was what the community wanted.., same tx count but more "block size" even if it was not what is actually been requested.

yea they been saying "look blocks are now 4 instead of 1.. while the actual tx count is not 4x
.. all thats been done was multiply the legacy bytes by 4x

very shady manipulative crap was done to pretend they were offering what the community wanted but in the end not giving the community 4x tx capacity. and instead just some unfinished txformat that is just used as a gateway to other networks (its true intent) while faking legacy as being 4x to "give the community the 4x they wanted"


its the simple analogy of
"we have 1 wife of 120lb we would like 4 wives of 120lb"
and core devs decided lets give then 1 wife of 480lb as it sounds like what they want
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
look at actual bitcoin raw transaction data, there are no fractions
and no a hard drive does not see #'vbyte'
hard drives count data in actual bytes.

I don't know why Core developers decided to invent a new size metric "vbytes", considering that only the scriptSig and some other fields are excluded from the byte calculation. IMO it would've been better to use the terms "transaction fee (legacy)" and "transaction fee (segwit)" and then keep the byte metric, but I guess it's much too late for that now.
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
ill give you a hint 50 becomes 0.05

You had better days with your answers, really.

And no, 50 would not become 0.05. 50 would become 50.0000.
The question is about replacing 1 satoshi with 1.0000 satoshi, not with 0.0001 satoshi.
Your "math" would work only if such a change would be done by monkeys instead of programmers. And it's not the case.
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
crew of malcontents

Only in the delusional mind of franky1 could anyone other than himself be portrayed as the malcontent here.  I don't see anyone else disrupting every topic they can find to whine about "fake consensus" and the supposed perils of millisats.  Notice how it's only franky1 with the firework permanently lodged up their arse about such things.   Roll Eyes

For what must be the hundredth time, we've got what we want.  We're perfectly happy (aside from having an unhinged lunatic to contend with every time we say something, that part is definitely wearing thin).  We don't require a "narrative" to change things.  The change has already been made.  You are simply unable to come to terms with the change.  You are the one who despises everything and everyone.  This is very much a you problem.  You are the malcontent.
legendary
Activity: 4410
Merit: 4788
oeleo
i do read what you write and i have seen tactics many times, you are not new,..  you many times have subtle hints of mentioning thing in a way that has two meaning so that you can play ping pong games to irritate people and then recruit idiots to believe the other narrative you and your buddies try MANY times to push, while trying to play inocent about not pushing it by reciting other parts of the same paragraphs where you hint at the opposite. just so you can be wishy washy and hide from your narrative

you have many times been subtly pushing that satoshi and the community dont care about adding units because i know your buddies want to break bitcoin further to make it emulate LN. you have tried it before your crew of malcontents have also at times tried to change the meaning of what a full node is your crew have tried to say that pruning is safe to do and pretend it still protects the network and still distributes the ledger and all that crap, when pruning does not help distribute the ledger nor allow peers to seed from a pruned node for IBD, and other things.

your chums of malcontents do not understand consent and abstinence in regards to consensus. heck you lot are trying to redefine consensus to say that abstinence is consent, where you lot also think vetoing a feature is evil and not consenting is evil while thinking that ignoring non-consent and abstinence is something that should be allowed.. pretending both non consent and abstinence are equal to consent means performing an act on the community should still go forward even without majority readiness to even validate a new rule..

your crew love things that hinder bitcoin scaling and you hate people that want onchain scaling, pretending no one wants it bar one person is absolutely stupid narrative played.. you lot are soo narrow minded stuck in trying to break bitcoin just to populate your crummy sub network that you cant even see that bitcoiners want bitcoin to remain secure. you think everyone wants to break bitcoin and move to your crummy network so you continue these ping pong games of promoting that breaking bitcoin can happen without harm when it literally requires breaking bitcoin(harm) to do so.

you pretend sometimes your on the side of bitcoin by ending a paragraph to sound like your all for protecting bitcoin but you start paragraphs with you hinting that it can be broke easily without controversy.

oh and if you are going to now suggest that im wrong because [insert any excuse] to try distancing yourself from your chummy narrative of malcontents and say that you are not like them or you dont believe in their narrative.. atleast stop sounding like them first by avoiding copying their narrative, then maybe one day i wont keep mentioning you in the same regard as them


mnow i dare you to actually go and look at a raw transaction get the real binary data, and then see what that transaction value becomes if you changed a rule where the hard data subunit of a 50btc coin reward from 2009 was represented in your dream delusion of a LN emulating 11 decimal system

ill give you a hint 50 becomes 0.05
it also breaks the halving cycles ru;le where instead of finishing in 2142 it finishes in 2180 if it was imposed at the next halving to emulate LN digits
and he total coins mined so far (19m) will be diluted in representation to look like 190k bitcoin where the remaining new coin by 2180 will look like only 1.3m coins.
go try and look at data, code, rules, and do some math. and stop relying on comments you find as your source bases to break bitcoin. because no satoshi did not say he wanted to break bitcoins sub unit rule
AGD
legendary
Activity: 2070
Merit: 1164
Keeper of the Private Key
Even ChatGPT knows the answer:


Question about Bitcoin. What will the impact be, when we add 4 zeros after the decimal, so that there will be 12 zeros instead of now 8 zeros?


#Adding four additional decimal places to the representation of Bitcoin would not change the value or underlying properties of the cryptocurrency. It would simply allow for greater precision in the representation of small amounts of Bitcoin.

For example, currently the smallest unit of Bitcoin that can be represented is 0.00000001 BTC, which is called a "satoshi" in honor of Bitcoin's creator, Satoshi Nakamoto. If four more decimal places were added, the smallest unit of Bitcoin that could be represented would be 0.000000000001 BTC.

It's important to note that this change would not affect the underlying value of Bitcoin or the amount of Bitcoin that exists. It would simply allow for the representation of smaller amounts of Bitcoin in a more precise way.
legendary
Activity: 2338
Merit: 1775
Catalog Websites
While answering in another thread, this debate came up in my mind about Bitcoin and decimals.  Curious to know what the general user thinks.

Say inflation was so crazy 1 Satoshi became $1 and a Hard Fork took place through which we add more decimals to Bitcoin.  It currently has 8.  If we add 4 more decimals, is 1 Bitcoin still just as scarce or do you consider it artificial injection of supply?

-
Regards,
PrivacyG

Of course, such measures will not lead to a change in the essence of Bitcoin and will not have any effect on its price. 

The number of Bitcoins in the world will not increase, and its deflationary supply model will not suffer.

In addition, such a change in the Bitcoin code is largely meaningless, since this measure will still not allow the poor to buy 1 satoshi cheaply.  This is due to the fact that all Bitcoin transactions are made on a reimbursable basis. 

The income is received by miners.  At the same time, the commissions in the Bitcoin network are quite large.
legendary
Activity: 2268
Merit: 18748
no we do not
stop playing user display cludgy math games to pretend proposals to break bitcoin code rules and data structures is a nothing burger..
look at actual bitcoin raw transaction data, there are no fractions
and no a hard drive does not see #'vbyte'
hard drives count data in actual bytes.

again you arw talking about human cludgy math, of the human GUI display of how bad math wants to calculate a fee based on data it ignores "for discount" or pretends is 4x bigger than actual bytes for legacy
Another excellent strawman. You should try arguing against things that are actually said, instead of just inventing points which weren't made to argue against.

Obviously there is no fraction of raw bytes, and I never claimed that there was. There is however, undeniably, fractions of virtual bytes. BIP 141 is quite clear that transactions are measured in weight units, and that virtual bytes are equal to weight units divided by 4, which leaves us with fractions of virtual bytes, which are then rounded up to the nearest whole byte for the purpose of calculating the fee.

you are again trying to set up a narrative that we actually do have sub units of sats on bitcoin
That's the exact opposite of what I said, when I pointed out that a minimum fee of 1000 sats/kvB obviously does not allow you to pay 172.25 sats for a transaction which weighs 689 weight units / 172.25 vbytes since fractions of a satoshi do not exist on the main chain, and so the minimum fee must be 173 sats.

Try actually pausing and reading what people are writing before launching in to another tirade.
Pages:
Jump to: