Crypto Page Whitepaper
  • Introduction
  • Disclaimers
  • Overview
    • Social media owned by the user
    • Project Description
    • Like... but better!
    • More than that!
  • Key modules
    • Interaction patterns
  • Technical aspects
    • Technologies used
    • Best practices
  • Page.Account
  • Page.Content
    • Page.Content ID
    • Arweave storage
    • Comments
    • Likes/Dislikes
    • Posts and comments burning
    • Transmission control
    • Metadata
    • Hidden posts and comments
    • Encrypted posts
    • Copyrights and reposts
  • Page.Token
    • Page.Token usage scenarios
    • Emission model
    • Content monetization
    • Calculation formulas for created tokens
    • Tips
    • Integration with DEX
    • Page.Token and Crosschain
  • Page.Community
    • Community Settings
    • Encrypted Communities
  • Page.SoulBound
  • Page.DAPP
  • Page.Mobile
  • Page.Messenger
  • Page.DAO
    • Supermoderator
  • Page.Treasury
  • Page.Marketplace
  • Page.Bank
  • Page.Registry
  • Page.Crosschain
    • Page.Crosschain.Root
    • Page.Сrosschain.Bridge
    • Page.Crosschain.Merkle
  • Page.SafeDeal
  • Page.Ads
  • Page.Identity
    • Verification via social networks
    • Verification via partners
    • CrossChain verification
    • Page.DAO and Page.Identity
  • Page.Future
  • Road Map
  • Links
Powered by GitBook
On this page

Technical aspects

Architecture

From a technical point of view, the Crypto.Page ecosystem is a set of software components working together, which can be divided into the following functional blocks:

  • Smart Contracts hosted on the blockchain - Page.NFT, Page.Token, Page.SoulBound, Page.Community, Page.DAO, Page.Treasury, Page.Bank, Page.Registry, Page.SafeDeal and others.

  • DAPP applications that allow the user to work with such smart contracts in a convenient way - Page.DAPP, Page.Mobile, Page.Marketplace, Page.Ads.

  • A backend for DAPP applications based on TheGraph's subgraph solution.

  • The Page.Messenger application with a scaling system to support the communication of a large number of users at the same time.

  • A set of services implemented as lambda functions for metadata generation, synchronization between blockchains, etc.

PreviousInteraction patternsNextTechnologies used

Last updated 2 years ago