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 SendAction, we should change the order of processing a send action:
Insert it into local action pool
If everything goes well, we move forward to broadcast it to other nodes
If error happens at 1, we should notify users of the error.
Another thing we want to measure is how much we add the e2e latency, because we now need to wait synchronously until the actpool adds or rejects the action.
Why is this needed:
Users sometimes are confused that they send an action, but it eventually isn't put on chain. They have no information to tell what the problem is.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
In SendAction, we should change the order of processing a send action:
If error happens at 1, we should notify users of the error.
Another thing we want to measure is how much we add the e2e latency, because we now need to wait synchronously until the actpool adds or rejects the action.
Why is this needed:
Users sometimes are confused that they send an action, but it eventually isn't put on chain. They have no information to tell what the problem is.
The text was updated successfully, but these errors were encountered: