Use an oracle to have a dynamic minimum_lock_time while still having a constant script hash

[SebastienGllmt]

Right now minimum_lock_time is a compile-time constant to ensure we have a constant script hash. However, this isn't great because we may have to dynamically update minimum_lock_time for hololockers if Cardano hardforks to change the slot time

The best way I can think of solving this is that instead of using a constant minimum_lock_time, we instead change it so that this value is fetched from a reference input. Unfortunately, doing this requires increasing contract complexity, and also developing a separate smart contract that manages the inline datum for this minimum_lock_time with some kind of DAO behind it

[SebastienGllmt]

As a slight note to this,
When creating a transaction, ttl and validity validity_start_interval` are specified in slots, but Plutus scripts themselves see them as POSIXTime (in milliseconds - the conversion is done by the Cardano node internally before being forwarded to the contract)