More detailed context on failure #113
Description
Story
As a user
I want to understand the reason why my transaction failed on execution
So that I can feel like my assets are safe
As a on-duty developer
I want to quickly understand the reason why transaction failed on execution
So that I can take appropriate actions
Background
We had a few incidents on PHA routes, where users had locked their founds for smaller periods as liquidity was missing on the destination chain. This on Explorer is displayed as generic failed transaction, where it would be a much better user experience if we showed the actual reason why this happened.
Details
This piece of art is a rough sketch of how something like this could look.
We are providing additional context on failed transactions. We could possibly even use this to automate retries based on fail context in the future.
Implementation details
We should start with something simple, such as only recognizing the situation where there is missing liquidity on the destination chain. Still, we should design a solution that can be extendable to hold different failed contexts.
Testing details
- Add unit tests
- Test on devnet/testnet
Acceptance criteria
- Indexer API expanded to save and provide information on failure context
- Explorer UI displays additional context for failed transactions