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.

Sign up for GitHub

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

Jump to bottom

block export (or any sub command) starts a BFT mining coordinator #6674

Closed
matthew1001 opened this issue Mar 4, 2024 · 0 comments · Fixed by #6675
Closed

block export (or any sub command) starts a BFT mining coordinator #6674

matthew1001 opened this issue Mar 4, 2024 · 0 comments · Fixed by #6675
Assignees
@matthew1001
Labels
bug Something isn't working

Comments

@matthew1001
Copy link
Contributor

Description

When running the block export or block import commands, a BFT mining coordinator is started. If the node is the only validator is will continue to produce new blocks even during export/import.

Acceptance Criteria

Don't start a mining coordinator when running any of the sub-commands

Steps to Reproduce (Bug)

Run besu --genesis-file=../genesis.json --data-path=./data blocks export --to=blocks.bin. If the node is the only validator it will produce new blocks during the export
@matthew1001 matthew1001 added the bug Something isn't working label Mar 4, 2024
@matthew1001 matthew1001 self-assigned this Mar 4, 2024
@matthew1001 matthew1001 changed the title block export command starts a BFT mining coordinator block export (or any sub command) starts a BFT mining coordinator Mar 4, 2024
This was referenced Mar 4, 2024
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matthew1001 matthew1001

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't start the BFT mining coordinator when it is created, just enable it matthew1001/besu
1 participant
@matthew1001