Page.Crosschain

Support for multiple networks

Crypto.Page is a cross-chain solution, allowing users to use all the functionality of the ecosystem on any of the supported blockchains. In the first phase of development, the Crypto.Page team plans to support the following blockchains:

Ethereum
BSC
Polygon

In the future, the ecosystem will be used on a significantly larger amount of networks, including:

Solana
Avalanche
Optimistic Ethereum
Tron
Other networks, both EVM-compatible and EVM-non-compatible.
- To support the Crypto.Page functionality, the blockchain network must:
  - Support smart contracts that are able to implement the functionality described in this document.
  - Have a decentralized stock market (like Uniswap) to determine the value of the Page.Token.

Crosschain support in key functional blocks

To implement support for multiple networks, all Crypto.Page contracts are deployed on each of the networks and the following solutions are used to synchronize data between these networks:

Page.NFT

Page.NFT tokens are always created on one of the blockchains chosen by the user, however, they can be transferred to another blockchain by the owner of such a token using the Page.Crosschain.Bridge mechanism. When transferring Page.NFT tokens, the token on the original network is not destroyed, it continues to exist. This approach is used to allow the author of the original content to use it to his/her advantage and earn money from such content on a variety of networks.

Page.Token

Each network has its own separate Page.Token. The real name of the token on each network is different - for example, on the Ethereum blockchain, the token is called Page.Token.ETH, however, using the Page.Crosschain.Bridge mechanism there will an opportunity to convert tokens from one network to the tokens from another network. When transferring tokens from one network to another one, tokens on the first network would be destroyed, while on the second one they would be created. Refer to the Page.Token and Crosschain section for additional details.

Page.SoulBound

Some of the Page.SoulBound tokens are non-transferable tokens, and the amount of these tokens a user has is synchronized across all supported networks using the Page.Crosschain.Merkle solution. This allows users who have a good reputation on one of the networks to receive bonuses from such reputation when voting and when creating a Page.Token on other networks. For transferred Page.SoulBounds - depending on each specific type - both synchronization using Page.Crosschain.Merkle and transferring tokens using Page.Crosschain.Bridge can be available. Determination of the available method of supporting cross-chaining occurs when registering a new type of passed Page.SoulBound. It should be noted that this carries some security risks (the possibility of using tokens multiple times), and it is not recommended to use the passed Page.SoulBound in voting and other similar processes.

Page.Community

Communities exist completely independently from each other on different networks.

Page.DAPP, Page.Mobile, Page.Messenger

Applications for working with the Crypto.Page project are blockchain-independent, and are able to display data from each of the supported networks.

Page.DAO

Page.DAO is used to manage the Crypto.Page project in each of its specific networks. Management issues are divided into network-specific issues (for example, the installation of any settings), or global issues for the project (for example, choosing where to invest the income from Page.Treasury and which of the blockchains requires additional development). Network-specific issues can be resolved through voting in a specific network, but global issues require the decision of a so-called "root network", voting in which will be mandatory for other networks. The decision of the root network described in the Page.Crosschain.Root section is implemented through voting in the current root network.

When voting, all Page.SoulBound tokens transferred via the Page.Crosschain.Merkle mechanism are taken into account. There are two ways for the Page.Token token' record - such tokens can be either transferred to the root network by users for voting purposes (which may not be very effective), or the Page.Crosschain.Merkle solution can be used for getting a snapshot of tokens from another network to the root network for counting votes based on such a snapshot. It should be noted that voting in Page.DAO cannot be based on blocking tokens (since the social network operation will be stopped in this case) and cannot be based on the approach when the user votes, but then completely freely disposes of his tokens (since such a user will transfer these tokens to another account and vote again, for the third time, and etc.). For these reasons, voting in Page.DAO will always be based on snapshots of the state of tokens at some point in time, and can safely use a Page.Crosschain.Merkle-based solution for synchronizing data about token owners.

Global decisions made inside the "root" Page.DAO are executed on other blockchains through the Page.Crosschain.Bridge mechanism.

Page.Treasury, Page.Bank

The Treasury and the Bank of the Crypto.Page project exist completely independently on different blockchains supported in the project. If, according to the voting results in the "root" network, Page.DAO decides on any actions in the Treasury or the Bank of a particular network, this action would be performed through the execution of a call from the corresponding Page.DAO of a specific network.

Page.Registry

The registry of contracts and settings exists completely independently from each other on different networks. If, according to the voting results in the "root" network, Page.DAO decides to change any settings on all networks, this would be done by making a call from the corresponding Page.DAO of each of the networks.

Page.SafeDeal

Page.SafeDeal safe deals and Page.SafeDeal-based marketplaces have independent implementations on each of the supported networks. Thus, two transactions on absolutely identical terms but on different blockchains are two independent transactions and should be processed and closed as two completely unrelated transactions. For the convenient usage of Page.DAPP there will be some information provided about the participants of transactions (their reputation and social profiles) in a combined form from all supported networks, but each specific transaction will be executed on the network selected by the participants of the transaction.

Page.Marketplace, Page.Ads

Page.Marketplace and Page.Ads solutions are completely independent from each other on different networks supported by Crypto.Page.

Page.Identity

Refer to the Crosschain verification section for details on the approach to user verification in various networks supported by Crypto.Page.