Foreverbox Whitepaper
  • 📈Jump start your foreverbox
  • Overview
    • 👁️Vision
    • 🔰Design Philosophy
    • 🗃️FBOX Storage
    • 🔐Data Security
    • 🔑Data Encryption
    • 🗂️Data Replication
    • 📑Data Sharding
    • 🛠️FBOX Architecture
  • Tokenomics
    • 🪙FBOX Token
    • 🛣️Initial Stage Roadmap
Powered by GitBook
On this page
  • DApps can be built on top of the Sharder Network.
  • Storage and Validation API:
  • FBOX Token Incentive Layer:
  • The P2P Layer (Peer to Peer):
  • Pluggable Storage Layer:
  • FBOX DFS (Distributed File System):
  • IPFS:
  1. Overview

FBOX Architecture

Below is the overall architecture for FBOX:

PreviousData ShardingNextFBOX Token

Last updated 1 year ago

DApps can be built on top of the Sharder Network.

Storage and Validation API:

This provides a Storage and Validation service API for external applications to leverage the Storage & Validation capability provided by IFBOX.

FBOX Token Incentive Layer:

Provides FBOX tokens to miners to secure and maintain the stability of the infinity BOX.

The P2P Layer (Peer to Peer):

The fundamental network layer for Sharder to build a P2P network fthe or Binance Smart chain. Credit Based Proof of Stake (CPOS) is the consensus mechanism for FBOX to maintain the public ledger for Binance Smart Chain

Pluggable Storage Layer:

The adaptor used to interact with different storage engines. It hides the storage engine difference and provides one unified storage interface for other components to use.

The adaptor is used to interact with different storage engines. It hides the storage engine difference and provides one unified storage interface for other components to use.

FBOX DFS (Distributed File System):

Designed by Foreverbox’s team and will be enabled as the default data storage system by the FBOX client.

IPFS:

Integrated into the FBOX client as part of the FBOX storage layer and could be switched to use it manually.

🛠️