When a deposit is queued using DepositManager.depositFor, it is difficult as a contract consumer to determine what subtree the deposit will become part of and how many deposits are currently part of that subtree. This also makes it difficult to correlate the deposit to the DepositsFinalised event from Rollup.submitDeposits.
Solution
Add uint256 subtreeID and uint256 depositCount to the IDepositManager.DepositQueued event.
Problem
When a deposit is queued using
DepositManager.depositFor
, it is difficult as a contract consumer to determine what subtree the deposit will become part of and how many deposits are currently part of that subtree. This also makes it difficult to correlate the deposit to theDepositsFinalised
event fromRollup.submitDeposits
.Solution
Add
uint256 subtreeID
anduint256 depositCount
to theIDepositManager.DepositQueued
event.