🦾
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. Main Contracts
  2. Extensions

FCT_Ext_SignersValidator

Smart contract that validates a signature of a predefined data struct. The signed data is the result of keccak256 hashing on two concat bytes32 values.

Use the fct message hash global variable in order to make sure the signature can be used only on a specific fct

PreviousFCT_Ext_SecureStorageNextLibraries

Last updated 10 months ago