Limits
Global limits for running and managing FCTs
Last updated
Global limits for running and managing FCTs
Last updated
| Name | Type |
|---|---|
Defines the date and time from which signed FCT can be executed on-chain.
Number of seconds since January 1, 1970
Defines the date and time from which signed FCT cannot be executed anymore.
Number of seconds since January 1, 1970
The max gas price that can be used by the activator when running this FCT.
The tokenomics encourage activators to decrease the gas price by as much as possible, so only in rare cases the actual gas price will reach this limit.
When purgeable is true, on-chain information of an expired FCT can be removed from the blockchain by the activators as part of running newer FCTs. This will clean-up the blockchain from unused stored data and will reduce the overall gas usage of the transaction.
If the FCT is part of cross FCTs logic, "false" should be used to ensure that the data is always available on-chain.
FCT Engine sends the FCT's message hash to the FCT_Runner upon execution requests of calls. It allows the runner to block specific signed FCTs from executing on the blockchain.
The vault implements functions to block and unblock "blockable" FCTs
The FCT runner might override this functionality, e.g. implementing "blocking all FCTs" function that blocks all FCT regardless of the "blockable" field
valid_from
uint40
expires_at
uint40
gas_price_limit
uint64
purgeable
bool
blockable
bool