For the Extension, we are only supporting sending on native chains for the MVP version so it's 1 transaction only and we don't have to cater for multiple transactions.
On the webapp we currently have:
send from native to non native - 1 tx
send from non native to native - 1 tx
send from non native to non native - 2 tx
send from non native to non native with memo - 3 tx
DoD:
multiple tx flow for extension
possible redesign for webapp's send flow to align with extension? there has been general feedback that the existing send flow on webapp is quite confusing
Pre-requisite
Let's have a sync with FE team as well on what's the best UX to proceed with handling multiple tx on Extension, as we aren't storing transaction history right now.
So if the user starts a 3 tx Send flow and then exits the extension, only the 1st tx will go through and there's no way to enter the flow again to complete the Send
For the Extension, we are only supporting sending on native chains for the MVP version so it's 1 transaction only and we don't have to cater for multiple transactions.
On the webapp we currently have:
DoD:
Pre-requisite Let's have a sync with FE team as well on what's the best UX to proceed with handling multiple tx on Extension, as we aren't storing transaction history right now. So if the user starts a 3 tx Send flow and then exits the extension, only the 1st tx will go through and there's no way to enter the flow again to complete the Send