reply on: Tail Emissions Are A Terrible Idea \ stacker news ~bitcoin

pull down to refresh

0 sats \ 1 reply \ @netstatic 24 Sep 2023 \ parent \ on: Tail Emissions Are A Terrible Idea bitcoin

There is no single X, value is subjective, but that's an aside. This just seems petty at this point. The whole point of the construction is under the assumption we (subjectively) valued satoshis at some exchange rate with something else. Like 2 people both valuing a sat as a loaf of bread. Yes, obviously individuals can value their sat at $1m if they choose. It has nothing to do with my point.

That's a convoluted way to look at it. It's just an increase in precision. More decimal places.

It's not convoluted, it's simple actually. Multiplying the value of sats does allow you to increase the precision, but whether we rename the basic units to something like millisatoshis or keep calling the base unit sats doesn't matter.

And yes in the implementation Bitcoin amount are expressed as 64 bit integers. 51 bits were not used in the amount.

https://github.com/bitcoin/bitcoin/blob/dcfbf3c2107c3cb9d343ebfa0eee78278dea8d66/src/primitives/transaction.h#L160

https://github.com/bitcoin/bitcoin/blob/dcfbf3c2107c3cb9d343ebfa0eee78278dea8d66/src/consensus/amount.h#L12

The main point is that it doesn't matter whether you keep the unit in satoshi and multiply everyone's supply equally or to multiply and change the base unit to millisatoshis. Everyone should still consider the value of their satoshis to be the same as before.

0 sats \ 0 replies \ @SpaceHodler 24 Sep 2023

It does matter. You can multiply by a power of 10 in the implementation, to stick to integer representations.

But it's a terrible idea to expose that change to humans at the nominal level, because, unlike the code, it results in countless references to update. And messes with their minds unnecessarily.

Let's say I bought 1 BTC and made a blog post about it. Now, after the split, I own 10 "new BTC", but someone reading the blog will read that I bought 1 BTC and won't know whether it refers to new or old BTC -- unless I update the blog post to clarify that.