BIT AI v1.0.3
  • πŸ‘‹Welcome to BIT A.I
  • BIT A.I Overview
    • πŸ’‘Ecosystem
    • ✨Our Mission
    • πŸš€Our Vision
    • πŸ–₯️Integrated Systems
    • πŸ™οΈA.I Based NFT Collection
  • BIT Token
    • πŸͺ‚BIT Token
    • πŸ€Tokenomics
    • πŸŽ–οΈBiT AI Roadmap
  • A.I Overview
    • 🧩History
    • πŸ’‘Artificial Intelligence
    • 🌈Why you need BIT A.I
  • Ecosystem Overview
    • πŸ“ͺThe Ecosystem
    • πŸ“ŽStorage System
  • Journey Phases
    • 🧍Pre-mature Phase
    • πŸ‘¨β€βš•οΈSemi-mature Phase
    • πŸ‘¨β€βš–οΈMature Phase
  • Public
    • πŸ”₯Support
    • 🚻Community
    • 🌎News
  • Bit A.I Glossary
    • πŸ“’Audit Report & KYC
    • ⛱️Glossary
    • ♻️Privacy Policy
    • βœ…Security Remarks
    • πŸŽ—οΈReferences
Powered by GitBook
On this page
  1. Ecosystem Overview

Storage System

How it works

Using a public ledger to facilitate the macrocodes for machine is challenging, not only because of high processing throughput, but also for storage space management. To achieve the β€œcode-per-byte” granularity, each software could send out a language every few seconds.

With even a moderate 0ne hundred thousand concurrent users, it could generate a couple thousands of codes per second. Even with the off-chain Marchine language pool which already reduces the amount of on-chain processing dramatically, the block and state data could still balloon rather quickly. We have designed a storage system that addresses this problem, and can adapt to different types of machines, be it a powerful server cluster running in data centers, or a commodity desktop PC

PreviousThe EcosystemNextPre-mature Phase

Last updated 2 years ago

πŸ“Ž