You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a continuous configuration of Borrowing there will be lot of proposals with EVM calls which are very unreadable for anyone, especially regular voters.
normally atleast you can decode it with polkadot js like subsquare does and see whats going on, but to be able to decode EVM calls is on another level for our users as they have to supply correct ABI for each contract used - which shouldn't be problem for our UI which already does this
Since we are already able to decode EVM calldata for users on the confirmation screen, it would be awesome to use it here so anyone can tell what will be done in the given proposal.
With a continuous configuration of Borrowing there will be lot of proposals with EVM calls which are very unreadable for anyone, especially regular voters.
normally atleast you can decode it with polkadot js like subsquare does and see whats going on, but to be able to decode EVM calls is on another level for our users as they have to supply correct ABI for each contract used - which shouldn't be problem for our UI which already does this
Since we are already able to decode EVM calldata for users on the confirmation screen, it would be awesome to use it here so anyone can tell what will be done in the given proposal.
All ABI's currently necessary should be available here: https://github.com/galacticcouncil/aave-v3-deploy/tree/hydration/deployments/hydration
Additionally verified contracts on explorer.evm.hydration.cloud could source ABI's.
The text was updated successfully, but these errors were encountered: