-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Block production trigger #599
Conversation
b42d341
to
d220375
Compare
FYI: I retargeted this PR to diff against #409 As far as configuration is concerned, we'll want a way to connect/consolidate with the |
630fabf
to
751737d
Compare
Ready for the initial round of comments |
Can we upgrade tokio in a separate PR to reduce some of the noise? It would remove a handful of files from your PR. |
|
Looks like we'll need a separate PR for enabling the real block producer in fuel-core and disabling the |
Also, have you tried running fuel-core via CLI to see what happens when txs are submitted? I'm not seeing any options on the CLI to configure the block production settings. |
I've added the production settings to ChainConfig. I'm not sure if they should instead be command line parameters for fuel-core instead, but chain config seems potentially better place to keep this. |
52212a2
to
fbdd88b
Compare
ChainConfig does make sense. The reason I was thinking of having CLI options to select the mode is for development or debugging. It's a fairly common practice in Ethereum to fork the mainnet chain and then put it into instant mode for local testing. Given it's not that hard to edit the chainconfig json, I don't mind leaving the settings there for now. If we wanted to support CLI overrides in the future, we could use the chainconfig as a way to store the default settings and metadata needed for initializing a PoS network for example, but if the option to use instant mode is provided via CLI then chainconfig could be ignored. |
clippy is failing |
9626da5
to
1d01b1a
Compare
Co-authored-by: Brandon Kite <brandonkite92@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very cool use of tokio time!
the hybrid trigger is the most complicated piece here and also has the least amount of tests. But we can cover this more extensively during the integration with fuel-core.
The only thing that may need to change based on the current arch discussion is that notifying the txpool about the new block should probably be done in the block importer. But since the importer doesn't exist yet, we can defer that.
This was already resolved, deferring to a new issue
Closes #50
Requires #409 to be merged first