In lecture 3 of the Plutus Pioneer Program Vesting.hs, I noticed that the example vesting give/ grab endpoints work by waiting a number of slots after the deadline. The script then checks
deadlineReached = contains (from $ deadline dat) $ txInfoValidRange info.
However, these docs for
txInfoValidRange say that the default range is infinite. In the lecture video and in the playground, I don't see that we set the txInfoValidRange explicitly, so I assumed it was infinite, but that means a from range would never contain it.
I must be misunderstanding the linked documentation. At some point, the
txValidRange must be getting set on the transactions submitted through the playground, otherwise,
deadlineReached would always be false. I can't find where this default is being set though.
Is this set by Plutus clients? In this case, the Playground?
There is a related question here, but I understand the
contains function. What I don't understand is how the
txInfoValidRange is set.