NethermindEth / NethermindEth/Catalyst
[Contract] Proper Handling of Prover Bonds
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Problem:
In the latest version of the Taiko inbox, the assigned prover is hard-coded to be the msg.sender of TaikoL1.sol (related PR). This is problematic since, with a preconf protocol, the msg.sender will be the preconf AVS contract instead of the proposer itself. As a result, the prover bond is accounted for from our AVS contract, TaikoTaskManager.sol, instead of the proposer.
Potential Solution(s):
- Do accounting for per-proposer bonds and manage approvals and withdrawals of taiko tokens through the task manager.
- Modify the Taiko inbox contract to (re)decouple the proposer from the prover.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing TaikoL1.sol and the related PR to understand how the prover is assigned, then inspect TaikoTaskManager.sol and PreconfTaskManager.sol at line 111 for the current bond accounting. Decide whether the change belongs in the task manager or the Taiko inbox, and verify that proposer bonds, approvals, and withdrawals are accounted for correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100