Management of blobs in the parallel-executor
- Dominant language
- Rust
- Stars
- 56.8k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
For the moment the parallel-executor doesn't manage blobs at all. Blobs can influence the execution of txs but we are not aware of which one can be used.
We chose to execute them at the end so that we don't need to include their changes in the state to execute normal transaction.
Flow is :
- Transaction source give us a blob transaction
- We decrease the global gas but we don't execute now we save it and we execute sequentially at the end (that's the reason of decreasing global gas and not worker one)
- We added the changes
Contributor guide
Research direction
Start by tracing the parallel-executor's handling of blob transactions and the described deferred sequential execution flow. The issue names no files or tests; done means blob effects are managed correctly without disrupting normal transaction execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100