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

feat: do not issue a time-based tenure extend earlier than needed #5787

Merged
merged 6 commits into from
Jan 31, 2025

Conversation

obycode
Copy link
Contributor

@obycode obycode commented Jan 31, 2025

With this change, a miner will not issue a time-based tenure extend if it has used less than X% of the tenure budget, where X can be specified in the tenure_extend_cost_threshold config option.

This implements point 3 in #5757.

With this change, a miner will not issue a time-based tenure extend if
it has used less than X% of the tenure budget, where X can be specified
in the `tenure_extend_cost_threshold` config option.
Also update the configs in other tests so that they do not need to wait
for the default tenure extend threshold.
@obycode obycode requested review from a team as code owners January 31, 2025 17:33
@obycode obycode requested a review from kantai January 31, 2025 17:33
Copy link
Member

@kantai kantai left a comment

Choose a reason for hiding this comment

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

LGTM, just a couple comments

Also add one more assertion to the test.
@obycode obycode requested review from kantai and jcnelson January 31, 2025 20:09
@obycode obycode added this pull request to the merge queue Jan 31, 2025
Merged via the queue into develop with commit 6228b9b Jan 31, 2025
178 of 183 checks passed
@obycode obycode deleted the feat/extend-when-needed branch January 31, 2025 21:38
@blockstack-devops
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Feb 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants