Page.Token and Crosschain

Support for Page.Token copies on multiple blockchains

The Crypto.Page solution is deployed simultaneously on multiple blockchains, at the same time the Page.Token contracts are independent between different blockchains. Since the biggest amount of Page.Tokens is generated as a compensation for the gas spent on creating posts, there is a possibility that a much larger amount of Page.Token tokens will be generated on a more expensive blockchain than on a cheaper one. For example, let's imagine that the cost of creating a post on Ethereum is about $2USD, while the cost of creating a post on Polygon will be $2UDS, which is at a price of 2 cents per Page.Token on both blockchains will lead to the creation of 100 times more Pages.Token on Ethereum, compared to the number of tokens created on Polygon.

By itself, this is not a big problem - since the user's expenses in both cases will be the same and will amount to about 2 cents per token, however:

• In cases where a certain percentage of tokens is allocated to the author of the post, and this author is not the creator of the token (repost) - it becomes more profitable for the post creator to place such a post on more expensive blockchains, and for the "reposter" - on cheaper ones.

• When creating comments, where part of the reward/compensation is allocated to the author of the original post, it becomes more profitable for commentators to leave comments on a cheaper blockchain, and it is more profitable for post authors to publish their posts (for which they expect income from comments) on a more expensive blockchain.

• When creating a community where any users can publish posts, it is also more profitable for community authors to create their communities on expensive blockchains (to maximize the reward for comments), and users wanting to create posts will prefer to create them on cheaper blockchains where their "uncompensated" gas costs will be lower.

• When voting inside Page.DAO, Crypto.Page participants who use more expensive blockchains will have more tokens while voting than the participants who use cheaper blockchains.

To solve this potential problem, the Crypto.Page team is going to use the following mechanisms:

• When transferring tokens (bridging) from one blockchain to another one, the number of tokens on the new blockchain is calculated based on the ratio of the current token price on that blockchain in relation to the token price on the previous blockchain, thus smoothing out temporary fluctuations in price.

• When voting, not only the amount of Page.Token tokens is taken into account, but also the reputation (in the form of Page.SoulBound), which in many ways acts as a Page.Token multiplier. At the same time, reputation is always calculated according to a fixed formula - and does not depend on the gas cost on some blockchain.

• We expect different demand for our services on different blockchains - for example, communities similar to OnlyFans subscriptions will be created on more expensive blockchains (increasing the income of the community authors for comments), and public communities will be created on cheaper blockchains, where creating posts requires minimal expenses from authors. Such a separation between communities and users on different blockchains is welcomed to maximize the coverage of all usage scenarios of social networks by different types of users.

It should be noted that just for the purposes of voting on issues that are relevant to all blockchains in Page.DAO, it is not necessary to transfer Page.Token from one blockchain to another one, Page.Crosschain.Merkle implementation periodically synchronizes the amount of Page.Token tokens from other networks to the "root" network (Page.DAO) for voting purposes.

The Crypto.Page team will monitor the market and adjust the modules for importing/exporting tokens from one blockchain to another one (via Page.DAO voting) to achieve a market balance between different stakeholders.