-
Notifications
You must be signed in to change notification settings - Fork 79
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
[EPIC] Sending transaction - improvements #14636
Labels
Comments
IvanBelyakoff
moved this to In Progress
in Do not use - tasks moved to unified Desktop / Mobile Board
May 9, 2024
iurimatias
removed this from Do not use - tasks moved to unified Desktop / Mobile Board
May 13, 2024
saledjenic
moved this from In Progress
to Iteration Backlog
in Status Desktop/Mobile Board
May 16, 2024
saledjenic
changed the title
Sending transaction - improvements
[EPIC] Sending transaction - improvements
May 17, 2024
saledjenic
added a commit
that referenced
this issue
Sep 13, 2024
saledjenic
added a commit
that referenced
this issue
Sep 17, 2024
saledjenic
added a commit
that referenced
this issue
Sep 24, 2024
saledjenic
added a commit
that referenced
this issue
Sep 25, 2024
saledjenic
added a commit
that referenced
this issue
Sep 26, 2024
saledjenic
added a commit
that referenced
this issue
Oct 1, 2024
saledjenic
added a commit
that referenced
this issue
Oct 1, 2024
github-project-automation
bot
moved this from In Progress
to Done
in Status Desktop/Mobile Board
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue depends on #14635
Apart from the things stated below, sending logic should know, based on the route, which transactions should be placed in parallel (immediately) and which of them should wait for execution of previously placed transaction/s.
The text was updated successfully, but these errors were encountered: