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
We want to store info about the "operation/transaction bundle" and also the actual transactions with a separate txHash triggered from that operation.
-- The user wants to send 0.3 DAI from account A to account B (operation/bundle), 1 send and 1 bridge gets triggered from that.
Some operations require an additional parameter after getting the route when sending the transaction to the chain (like Swap requires setting a Slippage value)
We'll want to store the full raw tx data (We always want to have the "interacted with" contract address) and some "interpreted data" (for token transfers we want to know the destination address and the amount, for approvals we want to store the spender amount and spender address, for example)
subtask of #5801
Storage
The text was updated successfully, but these errors were encountered: