Business Architecture

The Peeps platform consists of the following modules. The high-level ones can be divided into the following:

Account and identity management A module responsible for registering accounts and regulating the permissions of these accounts (for creating posts and channels, gaining access to content, moderating, etc.).

Channel management A module responsible for the ability to create channels and posts in the system, regulating access to these posts (using token management and account / identity management modules), as well as transferring ownership of the channel (and posts) between system participants.

Token management A module responsible for managing system assets in a digital form. These assets include local currency as well as NFTs tied to posts and NFTs that provide content moderation rights.

Financial interaction management These are modules designed to implement the economic model of infrastructure. This includes the logic of payments, staking, payments to channel-stakers, and channel selling.

Storage This module consists of 2 components - the core of the system (the component responsible for validating, storing and synchronizing transactions in the system) and the storage of additional data (content of posts). -> Moderation is a module required to implement the logic of decentralized content control (its validation and confirmation by participants with the role of CMs). -> Governance is a module that allows you to perform decentralized decision-making regarding system updates (DAO).

High-level architecture

The Peeps Platform includes the following components:

  1. Blockchain-based accounting system with core and modules for business logic implementation. It will leverage an existing blockchain infrastructure.

  2. Data storage - Pinned IPFS with a migration plan towards further decentralization.

  3. Bridges for interaction with external systems (liquidity and NFT bridging)

  4. Additional software for users and auxiliary components (such as oracles etc).

Peeps will launch in three phases, with iterative decentralization:

Phase 1. MVP/Prototype: Smart contract deployment on an EVM chain, no private content, centralized backend.

Phase 2. Semi-centralized product: The product is feature-complete on smart contract level, private content is kept on IPFS, encrypted at rest and pinned by the centralized backend.

Phase 3. Full decentralization: Private content is pinned by an incentivized decentralized network, content encryption and gating are managed between the parties.

Content storage

Public content is pinned on IPFS without encryption, with cid’s kept in smart contract storage. Before Phase 3, private content is encrypted by the backend and pinned to IPFS by Peeps. Whenever a user needs to access the content, the backend checks permissions and fetches it if the permissions are correct. Later stages will have decentralized pinning and leaderless encryption.

Info: While this is a very high-level explanation, our Prototype is already in the making and will be live soon! The Github code will become open source once the transition phase towards Phase 3 - Full Decentralization - will be announced.

Last updated