At the moment, when we have task n who has an action which submits a new task to gelato, then we cannot really choose a valid expiry date when we encode the payload for submitTask, because we dont know when the task will actually be submitted.
Similar to the Stateful conditions, we could use a delta for that, where users input that they want the claim to be active for e,g, 24 hours. Gelato will then calculate the respective timestamp on-chain.
At the moment, to create have one task submit another which is limited to a certain timestamp, we have to write a wrapper action around gelato which enables you to do that.
At the moment, when we have task n who has an action which submits a new task to gelato, then we cannot really choose a valid expiry date when we encode the payload for
submitTask
, because we dont know when the task will actually be submitted.Similar to the Stateful conditions, we could use a delta for that, where users input that they want the claim to be
active
for e,g, 24 hours. Gelato will then calculate the respective timestamp on-chain.At the moment, to create have one task submit another which is limited to a certain timestamp, we have to write a wrapper action around gelato which enables you to do that.