Limits
Global limits for running and managing FCTs
Typed Struct (EIP712)
Params
valid_from
uint40
expires_at
uint40
tx_data_limit
uint32
payable_gas_limit
uint32
max_payable_gas_price
uint40
purgeable
bool
blockable
bool
valid_from
Defines the date and time from which signed FCT can be executed on-chain.
expires_at
Defines the date and time from which signed FCT cannot be executed anymore.
tx_data_limit
The max tx.data length that can used for this FCT
This value protects the user from paying high fees, by blocking the activator from pushing unused data at the end of the transaction.
payable_gas_limit
Defines the maximum amount of gas the user is willing to pay for.
It can be used together with the max_payable_gas_price to give users a discount.
max_payable_gas_price
The max gas price that the use is willing to pay.
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.
purgeable
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.
blockable
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 FCT runner might override this functionality, e.g. implementing "blocking all FCTs" function that blocks all FCT regardless of the "blockable" field
Last updated