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
In #9644, we introduced a new rpc endpoint broadcast_tx that allows a user to specify the finality they want to wait for when they submit a transaction. In some use cases such as fungible token transfer, however, it is beneficial to have more granularity in the number of receipts to wait for to ensure the success of ft transfer. In other cases where it involves a chain of cross contract calls, it may be useful to wait for the first few receipts to complete before returning. So it would be nice if we can introduce a new finality level that specifies the number of receipts to wait for in this rpc enpoint to offer more customizability for users. cc @gmilescu
The text was updated successfully, but these errors were encountered:
In #9644, we introduced a new rpc endpoint
broadcast_tx
that allows a user to specify the finality they want to wait for when they submit a transaction. In some use cases such as fungible token transfer, however, it is beneficial to have more granularity in the number of receipts to wait for to ensure the success of ft transfer. In other cases where it involves a chain of cross contract calls, it may be useful to wait for the first few receipts to complete before returning. So it would be nice if we can introduce a new finality level that specifies the number of receipts to wait for in this rpc enpoint to offer more customizability for users. cc @gmilescuThe text was updated successfully, but these errors were encountered: