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

Page.Content ID

What is the Token ID of Page.NFT

The ID of Page.Conten token is a 256-bit integer that increases with each newly created token. I.e., the very first token will receive an ID with a value of 1 (the value of 0 is reserved), the second token will receive an ID with a value of 2, and so on.

The highest byte in each ID token identifies the ID of the blockchain network in which such a token was originally created. I.e., for example, a token created in the Ethereum blockchain network will have 0 as the value of the most senior byte, a token created in the Polygon blockchain network will have 1 as the value of the most senior byte, and so on. This approach will allow the transfer of tokens between networks (bridging) while preserving the value of the token identifier and not creating duplicate tokens with the same ID in the same network after the transfer.

PreviousPage.ContentNextArweave storage

Last updated 5 months ago