LogoLogo
AboutOORT AIOORT StorageOORT Edge
  • What is OORT Storage
  • Getting Started
    • How it works
    • User Guide
      • Sign Up
      • Create a Bucket
      • Upload an Object
      • Download an Object
      • Delete Objects or Buckets
    • Billing and Pricing
      • Free Tier, Always Free
      • Pay-as-you-go Pricing
      • OORT Credits
      • Manage Your Payments
  • Manage Storage
    • Work with Buckets
    • Work with Objects
      • Objects Overview
      • Object Keys
      • Object Details
      • Upload Objects
      • Multipart Upload
      • Download Objects
      • Delete Objects
      • Share Objects
      • Use Folders
    • Storage Classes
    • Access Control
    • Tools and Clients
      • Use Rclone
      • Use AWS CLI
      • Use S3 Browser
      • Use Arq Backup
      • Use TntDrive
    • Sync files to OORT Storage
      • Step 1: Download the rclone
      • Step 2: Do the OORT Storage remote configuration
      • Step 3: Check where your files are stored in?
        • Google Drive
        • Amazon Drive
        • Tencent Cloud Object Storage (COS)
        • Alibaba Cloud (Aliyun) Object Storage System (OSS)
        • IPFS
        • Others
      • Step 4: Check the configuration
      • Step 5: Do the files syncs
  • Developing with OORT Storage
    • Access Keys
    • Use S3-Compatible API
  • OORT Storage for Business
    • Web3 Web Hosting
      • Upload Website
      • Backend Hosting
      • Publishing
Powered by GitBook
On this page
  • File upload and retrieval
  • PoH Consensus
  • Decentralized and Open Source
  1. Getting Started

How it works

OORT Storage is a decentralized cloud storage platform that aims to provide a secure, private, and cost-effective alternative to traditional centralized cloud storage services. Here's how it works:

File upload and retrieval

Pre-processing Files

When a user wants to upload a file to OORT Storage, the file is split into small fixed-size pieces known as "shards". The total number of “shard” is determined by the size of the file.

Encryption and Erasure Coding

Each shard is encrypted using client-side encryption AES-256, ensuring that only the file owner can access the content. After encryption, the file is processed using a technique called erasure coding such as polar code and LDPC code. This process generates additional "parity" shards, which provide redundancy and allow the file to be reconstructed even if some shards are lost or unavailable.

Shard Distribution

These shards (both the original and the parity ones) are then distributed across OORT infrastructure nodes. These nodes are operated by individual users around the world who share their unused bandwidth and storage space in exchange for rewards.

Retrieving Files

The shard IP-based distribution is recorded in the decentralized database system in OORT. When the user wants to retrieve their file, the client-side application requests the shards from the corresponding nodes by querying the database. As the result of the erasure coding technology, the file can be reassembled and decrypted even if some shards are not available due to node failure or network congestion.

PoH Consensus

OORT Storage uses the PoH consensus to guarantee the integrity and availability of the stored shards on the nodes. Nodes that successfully deliver the request shards and meet the service level agreement are rewarded.

Decentralized and Open Source

There's no central authority that controls the data in OORT Storage. This design makes it resistant to censorship and single points of failure. Also, The source code of OORT Storage will be open in the future, which allows anyone to review the code and contribute to the project.

PreviousWhat is OORT StorageNextUser Guide

Last updated 1 year ago