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

Test "Tenure extend for bad tenures" on Nakamoto Testnet #5477

Closed
aldur opened this issue Nov 18, 2024 · 3 comments
Closed

Test "Tenure extend for bad tenures" on Nakamoto Testnet #5477

aldur opened this issue Nov 18, 2024 · 3 comments
Assignees
Labels
Milestone

Comments

@aldur
Copy link
Contributor

aldur commented Nov 18, 2024

Ref #5452.

@aldur aldur added this to the Nakamoto 3.0.0.0.3 milestone Nov 18, 2024
@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Nov 18, 2024
@aldur aldur moved this from Status: 🆕 New to Status: 📋 Backlog in Stacks Core Eng Nov 18, 2024
@obycode
Copy link
Contributor

obycode commented Nov 18, 2024

You could probably trigger the bad block commit scenario by adjusting the config on one miner, setting the block_commit_delay_ms to 0 in the [miner] section and setting max_rbf in the [burnchain] section to 100. That miner would then likely have a bad block commit every time it wins and the previous good miner should extend.

@obycode obycode moved this from Status: 📋 Backlog to Status: 💻 In Progress in Stacks Core Eng Nov 20, 2024
@aldur
Copy link
Contributor Author

aldur commented Nov 25, 2024

Assigning this to @jferrant to check that we have triggered the specific issue and it works as expected.

@aldur aldur assigned wileyj and unassigned deantchi Nov 25, 2024
@aldur aldur moved this from Status: 💻 In Progress to Status: ✅ Done in Stacks Core Eng Dec 4, 2024
@obycode obycode closed this as completed Dec 16, 2024
@blockstack-devops
Copy link
Contributor

This issue 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 Dec 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Status: Status: ✅ Done
Development

No branches or pull requests

6 participants