Purpose
Withdrawal history is currently stored in browser based off of user activity. The withdrawal history is not stored on chain in a transparent way, and thus to reconstruct it across multiple devices requires either introspecting past events or retrieving and filtering on chain data through an external data repository like our block explorer.
Preferably, the functionality to filter out withdrawal and deposit events that took place on our bridge would be handled through our SDK. The same for the status introspection of a withdrawal. Since this functionality is not yet available, withdrawal history reconstructing is done through filtering on our block explorers transaction and checking against the input fields of a withdrawal transaction.
Issues
51
Changes
Add token details retrieval through a specified token address.
Add UI overflow control to the withdrawal history.
Retrieve, filter and store missing withdrawal transactions.
Check list
[x] Code runs without regressions even though new code is incomplete
[x] Code reviewer has been explicitly notified outside automatic notification channels
Purpose Withdrawal history is currently stored in browser based off of user activity. The withdrawal history is not stored on chain in a transparent way, and thus to reconstruct it across multiple devices requires either introspecting past events or retrieving and filtering on chain data through an external data repository like our block explorer.
Preferably, the functionality to filter out withdrawal and deposit events that took place on our bridge would be handled through our SDK. The same for the status introspection of a withdrawal. Since this functionality is not yet available, withdrawal history reconstructing is done through filtering on our block explorers transaction and checking against the input fields of a withdrawal transaction.
Issues
51
Changes
Check list