Unique serial number for every single satoshi

[JiiBs]

While the OP might be a large text to read more carefully to understand, I might follow through on some of them but, I really didn’t pick in on how (what I might consider as the constant) 110000. While .5000000000 and all might explain for failing zeros and the 50BTC in Satoshi conversion, how did the supposedly #110000 which continues to reoccur in the rule of inheritance for output and input comes to be?

[1714768195]

1714768195

[1714768195]

1714768195

[1714768195]

1714768195

[1714768195]

1714768195

[1714768195]

1714768195

[odolvlobo]

... I really didn’t pick in on how ... 110000. ...

110000 is the number of the block that the satoshi was created in. Using the numbering system in the post, the 5,000,000,000 satoshis created in that block are numbered 110000.1 through 110000.5000000000.

[NotATether]

... I really didn’t pick in on how ... 110000. ...

110000 is the number of the block that the satoshi was created in. Using the numbering system in the post, the 5,000,000,000 satoshis created in that block are numbered 110000.1 through 110000.5000000000.

I feel as though the numbering system would save a LOT of space if it was in binary.

21,000,000 bitcoins in circulation * 100,000,000 sats per bitcoin would put the total number at around 2,100,000,000,000,000. That will take about 50 bits (in hex this value would be 775F05A074000 which is 13 hex characters long, but since the upper nibble (4 bits) of the first character is unused it can be omitted).

The block height is the part that can get tricky as it needs to be future-proofed.

We are way past 800k blocks over the last 15 years. Obviously a 14-bit number (64-50) cannot hold this amount so 64-bit ints are out. But you can fit every possibly practical block height inside a 78-bit (128-50) integer. I chose 128 bits because of memory alignment issues where smaller amounts will basically use this amount of space anyway.

[alexeyneu]

But you can fit every possibly practical block height inside a 78-bit (128-50) integer. I chose 128 bits because of memory alignment issues where smaller amounts will basically use this amount of space anyway.

it's not style bitcoin written in. there're own types like one used for nBits (it's called like vInt or something) . in packet structure it'll be rounded up to 8 bits . with no alignment . as it is in blockheader struct. nBits goes appended to smth else so complete thing occupies integral number of bytes. And it itself has integral size too .But may be it hasn't do not remember. Like 3 bytes

[odolvlobo]

110000 is the number of the block that the satoshi was created in. Using the numbering system in the post, the 5,000,000,000 satoshis created in that block are numbered 110000.1 through 110000.5000000000.

I feel as though the numbering system would save a LOT of space if it was in binary.

There are many ways to represent an Ordinals satoshi. It is up to the implementation. At its core, an ordinal is a number from 0 to 2099999997689999. As long as  the specification is followed, everything else is just a conversion between numbering systems.