Handle errors in the middle of transactions chain #41
Description
Is your feature request related to a problem
At the moment of an error occurred in the any part of transactions chain there is at least no excess sending to initiator address
Ideally we should handle all corner cases, especially errors in votes counting to avoid double voting / vote ignoring
Describe the solution you'd like
Not sure about best solution. Maybe bounce handling? And of course excess sending to initiator
Describe alternatives you've considered
No response
Additional context
The last "tactical battle" had a condition of returning the excess to the sender. Could be helpful for reference