Decentralization Client: Handle payer commit failures

[mkysel]

Is your feature request related to a problem?

In the decentralized world, some messages (such as commits) go to the blockchain via the payer.

Regular messages can be retried and even retried via a different node.

Blockchain payloads will generate a new block and hence a completely new event.

Imagine a scenario such as:

• client wants to write a commit
• the payer is processing the commit
• the network between the client and the payer severs or the payer service fails
• the blockchain finishes the write

In this scenario the client needs to have a way to determine whether the event was successfully written to the chain or whether it needs to retry.

The obvious way to attempt to do this is to read from a node. But the node might be delayed and there is no upper bound on the out-of-dateness that a node can have.

Describe the solution to the problem

No response

Describe the uses cases for the feature

No response

Additional details

No response