You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want separate deposit Merkle trees for each token type? Do we need a Merkle tree on-chain or would a simple list of ‘pending deposits’ suffice with the Merkle trees only generated by Operator?
So if I'm understanding correctly the operator does a “getPendingDeposits” operation to take the current 'pending deposits' from the EVM to the side chain.
It gets them off Ethereum and adds them to the deposits Merkle tree on the sidechain, and then clears the 'pending deposits' list on-chain.
I don't believe we need to store a permanent record of each individual deposit on-chain (we will just emit events) because we don't need to know how much each user deposited after it's added to sidechain. Now sidechain logic / the SNARKS are used to tell you how much money you have.
Do we want separate deposit Merkle trees for each token type? Do we need a Merkle tree on-chain or would a simple list of ‘pending deposits’ suffice with the Merkle trees only generated by Operator?
No they should all go in the same tree.
So if I'm understanding correctly the operator does a “getPendingDeposits” operation to take the current 'pending deposits' from the EVM to the side chain.
That is correct.
I don't believe we need to store a permanent record of each individual deposit on-chain (we will just emit events) because we don't need to know how much each user deposited after it's added to sidechain. Now sidechain logic / the SNARKS are used to tell you how much money you have.
Deposit coins from EVM into snark side chain.
The text was updated successfully, but these errors were encountered: