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
Actually the transaction subscriber notify each replication attestation as the number of confirmations.
The problem is that when a user wants to send mutiple transaction from the same chain, it has to wait the full validation of a transaction before sending the next.
Actually the user don't know of many confirmations the transaction will have and cannot send the next transaction when it gets the first confirmation because all storage not didn't finished the replication.
Describe the solution you'd like
We could provide a way to notify the user if the transaction is fully validated or not. There is mutiple options :
In the response we can send the number of confirmation and the maximum number of confirmation expected
We can add a flag in the last confirmation to say that the transaction is fully validated
We can add an option to the sibscriber to notify either each confirmation or only when all confirmation are received
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Actually the transaction subscriber notify each replication attestation as the number of confirmations.
The problem is that when a user wants to send mutiple transaction from the same chain, it has to wait the full validation of a transaction before sending the next.
Actually the user don't know of many confirmations the transaction will have and cannot send the next transaction when it gets the first confirmation because all storage not didn't finished the replication.
Describe the solution you'd like
We could provide a way to notify the user if the transaction is fully validated or not. There is mutiple options :
Additional context
No response
The text was updated successfully, but these errors were encountered: