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

Implement updated KIP9 mempool rules (excluding TN11) #448

Merged
merged 3 commits into from
Apr 8, 2024

Conversation

michaelsutton
Copy link
Contributor

As suggested by KIP9, this PR updates mass calculations to reflect the final proposal wherever possible. This includes:

  • Applying a maximum over stoarge_mass and compute_mass rather than summing them
  • Using the relaxed formula for the cases |O| = 1 OR |O| <= |I| <= 2

The updates are applied on mainnet and TN10 on the mempool level. TN11 requires a hard-fork for this update and remains unchanged for now also on the mempool level (since the new rules are more permissive)

Copy link
Collaborator

@coderofstuff coderofstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

@michaelsutton michaelsutton merged commit 292d6cc into kaspanet:master Apr 8, 2024
6 checks passed
smartgoo pushed a commit to smartgoo/rusty-kaspa that referenced this pull request Jun 18, 2024
* apply the updated kip9 rules wherever possible (excluding TN11)

* temp

* bump version to 0.13.6
D-Stacks pushed a commit to D-Stacks/rusty-kaspa that referenced this pull request Jul 12, 2024
* apply the updated kip9 rules wherever possible (excluding TN11)

* temp

* bump version to 0.13.6
D-Stacks pushed a commit to D-Stacks/rusty-kaspa that referenced this pull request Jul 17, 2024
* apply the updated kip9 rules wherever possible (excluding TN11)

* temp

* bump version to 0.13.6
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