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

Unify the sending process after the best route is generated by the router #16335

Open
Tracked by #14636
saledjenic opened this issue Sep 16, 2024 · 0 comments · May be fixed by #16330
Open
Tracked by #14636

Unify the sending process after the best route is generated by the router #16335

saledjenic opened this issue Sep 16, 2024 · 0 comments · May be fixed by #16330
Assignees

Comments

@saledjenic
Copy link
Contributor

The Flow:

  • a client requests from statusgo to build transactions for the best route that was displayed
  • statusgo:
    • builds all transactions and sends signal to the client asking for signing transactions or
    • builds transactions one by one and sends to the client for signing, in the order which is determined by the router
  • the client:
    • signs transactions and calls statusgo to send built transactions providing signatures for all of them or
    • signs transactions one by one and calls statusgo to send built transaction providing signature for it
  • statusgo:
    • sends built transactions with received signatures
    • sends built transaction with received signature and waits for its execution before asking the client to sign next transaction
  • once all transactions from the bundle are sent statusgo notifies client via signal that the multitransaction is sent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Code Review
Development

Successfully merging a pull request may close this issue.

1 participant