Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Activity Simplification] Storage #5825

Open
friofry opened this issue Sep 11, 2024 · 1 comment
Open

[Activity Simplification] Storage #5825

friofry opened this issue Sep 11, 2024 · 1 comment
Assignees

Comments

@friofry
Copy link
Contributor

friofry commented Sep 11, 2024

subtask of #5801

Storage

  • Add DB tables to store full required information when sending a transaction (bundle + single tx data)
  • Migrate entries from the old multi_transactions and transfers tables to the new ones.
  • Remove old DB tables
@dlipicar
Copy link
Contributor

Some things I had in mind:

  • 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants