You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sequence numbers are u64s, 8 bytes, whereas inscription IDs are 36 bytes. Using sequence numbers as index keys and values might substantially decrease the size of the database, making indexing faster and reducing the index filesize. Additionally, we could use 4 byte sequence numbers, which would be enough for the next 100 years, given the current rate or inscription creation. And, since the size of the type used to store sequence numbers isn't visible externally, it can be increased at any time.
The text was updated successfully, but these errors were encountered:
Sequence numbers are u64s, 8 bytes, whereas inscription IDs are 36 bytes. Using sequence numbers as index keys and values might substantially decrease the size of the database, making indexing faster and reducing the index filesize. Additionally, we could use 4 byte sequence numbers, which would be enough for the next 100 years, given the current rate or inscription creation. And, since the size of the type used to store sequence numbers isn't visible externally, it can be increased at any time.
The text was updated successfully, but these errors were encountered: