Better management of storage merging in parallel-executor
- Dominant language
- Rust
- Stars
- 56.8k
- Forks
- 2.9k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 5
Description
// 0. Make a transaction with the DA changes in a Arc used by everyone afterwards
// 1. All contract changes in 1 changes
// 2. Create a storage transaction on top of the storage transaction that have the DA Changes
// (created at the start of run function and re-used by all executions)
// 3. Execute the transactions on top of this storage transaction
Contributor guide
Research direction
Start by locating the parallel-executor run function and the storage-transaction code it uses. Trace how DA changes and contract changes are currently handled across executions. Done means the three listed transaction-management steps are implemented and the storage merging behavior is covered by the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100