Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using sequence numbers as index keys and values #2641

Closed
Tracked by #2613
casey opened this issue Nov 8, 2023 · 0 comments · Fixed by #2664
Closed
Tracked by #2613

Consider using sequence numbers as index keys and values #2641

casey opened this issue Nov 8, 2023 · 0 comments · Fixed by #2664

Comments

@casey
Copy link
Collaborator

casey commented Nov 8, 2023

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.

@casey casey mentioned this issue Nov 8, 2023
30 tasks
@casey casey linked a pull request Nov 13, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant