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
The TS SDK should support queuing of transactions. This feature would allow developers to queue multiple transactions and ensure they are executed sequentially. For example, once transaction X is completed, transaction X+1 should automatically start, and so on. (i.e. once X tx is done, do X + 1, etc).
This feature is particularly useful in scenarios where a series of dependent transactions need to be processed in a specific order. It simplifies the workflow for developers who otherwise would have to manually handle the sequencing and execution of transactions.
@nedsalk I believe it would, but the funding of transaction X + 1 should happen after transaction X is processed (In case X + 1 needs to use UTXOs created by X).
Since this approach is designed to wait for X to be processed in order to submit X + 1, any output produced from X (UTXOs or even a deployed contract) will be usable on X + 1.
The TS SDK should support queuing of transactions. This feature would allow developers to queue multiple transactions and ensure they are executed sequentially. For example, once transaction X is completed, transaction X+1 should automatically start, and so on. (i.e. once X tx is done, do X + 1, etc).
This feature is particularly useful in scenarios where a series of dependent transactions need to be processed in a specific order. It simplifies the workflow for developers who otherwise would have to manually handle the sequencing and execution of transactions.
The text was updated successfully, but these errors were encountered: