LogoLogo
  • Overview
    • Intro
    • Fair Math Actor
      • Fair Math Controller
      • Fair Math VM
      • Setup an Actor
    • Hello (CIFAR) world!
  • FHE Computer
    • Overview
    • Architectural Layers
      • Application Layer
      • Orchestration Layer
      • Verification Layer
      • Execution Layer
      • Data Layer
    • ISA
      • fhe
      • arith
      • tensor
      • polycircuit
    • Operating System
      • Computer State
      • Application
        • Running Applications
        • External Functions
        • Interactive APPS
      • Execution Graph and Tasks
        • Atomic and Composite Instructions
        • Instruction Unrolling
        • Task Dependencies
        • Execution Graph
      • Process
        • Process lifecycle
        • Resource Allocation and Isolation
      • Order Book
        • Matching Mechanism
        • Task Complexity
        • Instruction Complexity
        • Task re-Delegation
      • Context
        • Context Structure
      • FHE Component Repository
    • Fair Math Actors
      • Task State Monitoring
      • Execution Pairs
      • Rewards and Penalties
    • Ethereum Endpoint
    • CIFAR10 App
  • Whitepapers
    • FHE Computer
    • FHERMA
  • FHERMA
  • Resources
    • Computer CLI
    • FHERMA
    • POLYCIRCUIT (CPP)
    • OpenFHE-rs
    • Talks and Podcasts
  • Social
    • Twitter
    • Linkedin
    • Website
    • Github
Powered by GitBook
LogoLogo
On this page
  1. FHE Computer
  2. Operating System
  3. Application

Running Applications

Applications in the Fair Math Computer are triggered through transactions, which can perform two types of actions:

  1. Starting a New Application A transaction can launch a new application by providing its unique identifier and any required input arguments. This creates a new process linked to the application. The process starts executing from the specified entry point or the main function by default.

  2. Calling a Specific Function A transaction can directly call an external function within a running application by providing the following details:

    • Application ID: Uniquely identifies the target application.

    • Function Name: Specifies the function to invoke as the entry point.

    • Process ID: Links the call to the correct application process. Input arguments can be passed dynamically, enabling flexible interaction with the application during its execution.

PreviousApplicationNextExternal Functions

Last updated 5 months ago

Page cover image