Mitja's web page
Everscale White Paper
Everscale White Paper
  • Everscale Whitepaper
    • Abstract
    • Preamble
    • Chapter One: Everscale
      • Decentralization
      • Meritocratic Token Distribution
      • Governance
      • Economy
    • Chapter Two: Ever Kernel (EK)
      • Context
      • WorkChains
      • Multithreading
      • SMFT (Soft Majority Fault Tolerance) Consensus
      • Masterchain Slashing and Recovery Protocol (MSRP)
      • Distributed Dynamic Validator Set (DDVS)
      • Improved Finality
      • REMP — Reliable External Messaging Protocol
    • Chapter Three: Ever Operating System
      • About Ever OS
      • File System
      • File names and directories
      • Tonix
      • Storage and other Peripheral Workchains
      • File index smart contract
      • IceChain
    • Chapter Four: Web Free
      • Smart Contract Languages
      • Programs security
      • Distributed programming
      • Resolving
      • Reverse resolution via Index smart contract
      • DeBots
      • Pipes
      • Code Handling
      • Upgradability
    • Conclusion: The Evolution
    • References
Powered by GitBook
On this page
  1. Everscale Whitepaper
  2. Chapter Three: Ever Operating System

File System

In Ever Kernel the address of a smart contract is calculated by hashing its code and initial data. The full address, consisting of a 32-bit WorkChain_id, and the 256-bit internal address or account identifier account_id inside the chosen WorkChain. In operating system terms it provides address space management functionality.

In the context of the Ever Operating System though, The Merkle tree of Ever Kernel 1.0 provides just part of the necessary functionality to build a fully distributed file system. Therefore we are adding two additional search trees in which nodes would represent contract code hash and contract data and leafs would be contract addresses. We are optimising for fast lookup for contracts with similar data or code hash from within the Node and adding subsequent instructions to ESVM to allow this lookup from within smart contracts. Additionally, we add code versioning within these trees thus allowing following the evolution of a smart contract code after setCode operations.

This functionality will be particularly useful in the Distributed Programming Paradigm (see below).

PreviousAbout Ever OSNextFile names and directories

Last updated 3 years ago