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
  1. Technical aspects

Best practices

Practices that the Crypto.Page team used during development

To control the quality and ensure the security of smart contracts the Crypto.Page team actively used:

  • OpenZeppelin Smart Contracts:

    • Upgradable to support the possibility of upgrading contracts.

    • AccessControl for role and access control.

  • Modular construction of smart contracts for ease of expansion and customization of behavior.

  • 100% test coverage of our smart contracts to ensure security

PreviousTechnologies usedNextPage.Account

Last updated 2 years ago