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.Content

Arweave storage

Storage of post content

PreviousPage.Content IDNextComments

Last updated 5 months ago

When creating a post, Crypto.Page perceives a link to Arweave as one of the parameters for calling the function to create a post. This link should store the content of the post to which smart contracts\Crypto.Page solutions will add the necessary metadata in the future. In and applications generation of such a link is automated, i.e. the user only needs to provide the content that he wants to publish, and the system will automatically upload this content to Arweave and generate a link for the user that will need to be passed inside the post creation function (which is also automated inside Crypto.Page applications). Crypto.Page does not prohibit the user from downloading the content and uploading the link themselves, however, it requires such a link to be an Arweave link.

It should be noted that Crypto.Page uses a solution from Arweave to upload data to blockchain. Arweave's services are paid for by at the expense of funds received from the sale of tokens in . Page.DAO can set limits inside Page.DAPP/Page.Mobile on the size of content uploaded to Arweave both within a single post and within the content uploaded by a single user in order to make sure that users will not use the system to store huge files as a substitute for their personal file storage.

In the future can make additional decisions and support storing posts in places other than Arweave.

Page.DAPP
Page.Mobile
Page.DAO
Page.Treasury
Page.DAO