-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Tracking: Engine revamp #8742
Labels
A-engine
Related to the engine implementation
C-debt
A clean up/refactor of existing code
C-tracking-issue
An issue that collects information about a broad development initiative
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
Comments
This was referenced Jun 15, 2024
Closed
This was referenced Jun 27, 2024
This was referenced Jul 13, 2024
This was referenced Jul 22, 2024
This issue is stale because it has been open for 21 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-engine
Related to the engine implementation
C-debt
A clean up/refactor of existing code
C-tracking-issue
An issue that collects information about a broad development initiative
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
Describe the feature
The current engine <-> tree design has several drawbacks
sequential processing
Tree Read lock that interferes with rpc (pending block access)
very complex request processing that requires multiple tree access roundtrips
This must be redesigned entirely
This should allow us to support other interfaces like ABCI,Arbitrum or others via the Node Builder
Tasks
BuiltPayload
#10159BlockchainProvider2
#10186InsertBlockFatalError
#10219Additional context
No response
The text was updated successfully, but these errors were encountered: