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

Context

The Context is a concept in our Computer model, representing the state of the process. It acts as a container for all relevant data, including variables, their current values, and additional parameters required for executing assigned tasks.

When an actor is assigned a task, the associated context is passed to it. This context includes the current state of all accessible variables and any necessary cryptographic infor- mation, such as keys or the cryptographic context. As the actor executes the instructions, it generates a new context that reflects the updated state. This new context is then submitted to the blockchain, where it updates the global state of the relevant process.

The context serves as the medium through which actors communicate the results of their computations, including intermediate results. Throughout the execution of the application, the context evolves, and a final context is formed and saved once the application completes. While the context itself is stored on the blockchain, it is designed to be lightweight. Large objects, such as arrays and ciphertexts, are stored on external data layers, with the context containing only references (e.g., hashes) to these objects. This design ensures efficiency and scalability.

PreviousTask re-DelegationNextContext Structure

Last updated 5 months ago

Page cover image