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

make the upper limit of allocated atoms and pairs hard coded #358

Merged
merged 3 commits into from
Jan 8, 2024

Conversation

arvidn
Copy link
Contributor

@arvidn arvidn commented Jan 6, 2024

Now that the 1.8.0 soft-fork has activated, all blocks are validated with these limits. Hard coding the limit opens up the ability to use some of the bits in NodePtr to encode the category of the node, for instance.

…of configurable. Now that the 1.8.0 soft-fork has activated, all blocks are validated with these limits.
Copy link

coveralls-official bot commented Jan 6, 2024

Pull Request Test Coverage Report for Build 7432500517

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.001%) to 93.805%

Totals Coverage Status
Change from base Build 7279846177: 0.001%
Covered Lines: 5406
Relevant Lines: 5763

💛 - Coveralls

@arvidn arvidn marked this pull request as ready for review January 6, 2024 18:01
@arvidn arvidn requested review from richardkiss and Rigidity and removed request for richardkiss January 6, 2024 18:01
@arvidn arvidn merged commit 09276d0 into main Jan 8, 2024
27 checks passed
@arvidn arvidn deleted the limit-pairs-atoms branch January 8, 2024 11:37
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 this pull request may close these issues.

2 participants