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. Page.Community

Encrypted Communities

Ways to protect content for communities with limited access to posts

PreviousCommunity SettingsNextPage.SoulBound

Last updated 2 years ago

Depending on the community settings, some communities may restrict access to all posts or a part of their posts for some users (and allow access only to the members/users paying for the membership, and so on). To implement such functionality, communities use a combination of encrypted posts, special community plugins and offchain solutions to control access to encryption keys.

It should be noted that posts that should be encrypted, should be encrypted from the moment they were created - encrypting a post that was publicly available does not make sense. When publishing posts through the app, it is possible to encrypt a post with the current encryption key of the community through a simple and intuitive interface, if the user who wants to publish such a post has access to such a key (i.e. is a member of the community with the rights to read and publish posts).

Decryption of the post is carried out through Page.DAPP, which checks whether the user has access and rights to access such a post (depending on the settings of this community).

Page.DAPP