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 names and directories

The Ever OS user should be able not only to call a program by internal processor address, but to use human readable names, store data not only in the contract internal memory but have access to some peripheral devices such as hard drives, long term storage and so on that would represent a natural functionality of an operating system kernel.

File names and directories have been implemented by a protocol we call DeCert (Decentralized Certificates) in general and in particular DeNS (Decentralized Name Service).

The implementation of DeNS is an example of the Distributed Programming Paradigm of Everscale (see a special chapter below for more information) which provides an instant name resolution.

PreviousFile SystemNextTonix

Last updated 3 years ago