🦾
The FCT Platform
  • Overview
    • Introduction
    • FCT Language
    • How it works
    • Sub-systems
  • Main Contracts
    • FCT_Controller
    • FCT_ENS
    • FCT_Engine
    • FCT_Runner
    • FCT_Actuator
    • FCT_Tokenomics
    • FCT_Funding
    • FlashLoans
      • FCTFlashLoan_Aave_v2
    • Extensions
      • FCT_Ext_TokensValidator
      • FCT_Ext_TokensSafeMath
      • FCT_Ext_SecureStorage
      • FCT_Ext_SignersValidator
    • Libraries
      • FCT_Lib_UniswapV2
      • FCT_Lib_MultiCallV2
  • tokenomics
    • Architecture
    • Whitepaper
  • Engines
    • FCT_BatchMultiSig
      • Meta
      • Engine
      • Limits
      • Recurrency (Optional)
      • MultiSig (Optional)
      • Computed (Optional)
      • Validation (Optional)
      • Calls
        • Call Header
        • Call Params
      • Variables
        • External
        • Returned Data
        • Computed
        • Global
      • Solver Call
  • Runners
    • Vault
Powered by GitBook
On this page
  1. Engines
  2. FCT_BatchMultiSig

Variables

Variables can be used either in calls params and in called function input params.

There is no type check for variables, so it is the responsible of the FCT builder & activator to do type checking offline.

In order to allow variables as part of a standard EIP712 message, rarely used values were chosen to represent variables.

Variables can be created from multiple sources:

  • Injected by the activator when executing an FCT (External)

  • Returned data for previous calls (Returned Data)

  • Runtime information taken from the EVM (Generic)

PreviousCall ParamsNextExternal

Last updated 10 months ago