Open gregLibert opened 5 months ago
The expiration durations, in number of periods, for our various products should be aligned as much as possible. And documented.
As of today we have:
Note that the node client does not wait for the transaction. The 10 periods (not slots !!) you are referring to are the number of periods in the future that the expiry period of the transaction is set to when it is emitted. Is is set to 10 in order to match the validity duration of operations: https://github.com/massalabs/massa/blob/main/massa-models/src/config/constants.rs#L146
In general, waiting a constant time is not the right way to proceed as finality can take up to 1 cycle in practice.
Here is how to proceed: https://github.com/massalabs/massa-web3/issues/472#issuecomment-1720861767
Add to the documentation an explanation of when a transaction can be definitively considered as failed. This includes the nominal case, where a transaction is included in a final block as failed, but also more exotic cases such as: