What problem does your feature solve?
Lab has a rigid transaction flow.
What would you like to see?
For the re-design transaction flow, I think we should think about separating out how to enable the users to simulate and sign multiple times. The transaction starts with Build transaction and ends with Submit transaction but simulation and signing is not a linear path. If we can put the components on the single page, with the beginning (Build) and the end (Submit) defined, and enable the simulate and sign to be more flexible that would be a great step forward.
[Classic vs Soroban transactions] We should be able to determine if a transaction requires simulation or not by looking at the operations. If it doesn't require simulation, we can skip to sign and submit.
What problem does your feature solve?
Lab has a rigid transaction flow.
What would you like to see?
For the re-design transaction flow, I think we should think about separating out how to enable the users to simulate and sign multiple times. The transaction starts with Build transaction and ends with Submit transaction but simulation and signing is not a linear path. If we can put the components on the single page, with the beginning (Build) and the end (Submit) defined, and enable the simulate and sign to be more flexible that would be a great step forward.
[Classic vs Soroban transactions] We should be able to determine if a transaction requires simulation or not by looking at the operations. If it doesn't require simulation, we can skip to sign and submit.