> For the complete documentation index, see [llms.txt](https://monobridge.gitbook.io/monobridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monobridge.gitbook.io/monobridge/case-study/3.1-curve-building-a-unified-cross-chain-rewarding-logic/3.1.2-value-for-application.md).

# 3.1.2 Value for application

Curve demonstrates how the rewards of liquidity providers can be calculated based on the total liquidity on multiple chains and fully reflects how a unified cross-chain business logic can be achieved through cross-chain Dapps built with anyCall. The calculation formula is as follows:

&#x20;                𝑃i\
\----------------------\
𝑃𝐸𝑡ℎ𝑒𝑟𝑒𝑢𝑚 + 𝑃𝐹𝑎𝑛𝑡𝑜m

Specifically, 𝑃𝑖 refers to the aggregate number of liquidity provided by user i for Ethereum and Fantom; 𝑃𝐸𝑡ℎ𝑒𝑟𝑒𝑢𝑚 is the liquidity on Ethereum; and 𝑃𝐹𝑎𝑛𝑡𝑜𝑚 is the liquidity on Fantom. Curve builds a unified logic for calculating rewards of liquidity providers on the two chains, while similar applications calculate the user's liquidity contribution separately on the relevant chains, that is\
𝑃𝑖−𝐸𝑡ℎ𝑒𝑟𝑒𝑢𝑚 𝑃𝐸𝑡ℎ𝑒𝑟𝑒𝑢𝑚 ∧𝑃𝑖−𝐹𝑎𝑛𝑡𝑜𝑚 / 𝑃𝐹𝑎𝑛𝑡𝑜𝑚 are calculated separately. That means that liquidity pools on different chains were fragmented. Without a unified business logic, it is impossible to make dynamic adjustments of rewards among chains. This may lead to an unfair situation in which users who invest less liquidity on a chain with low liquidity gain more rewards that those who contribute more on a chain with high liquidity. For project developers, chains with stronger demand for transactions will contribute more TVL and transaction volume, and constitute a more important market that requires greater liquidity support. Unfair distribution of rewards will lead to the behavioral disorder of users in liquidity provision and undermine the overall development of projects.

For the purpose of calculating rewards, the sum of the liquidity of the same trading pair in a multichain environment is used as the denominator, and that of the liquidity provided by users on each chain is used as the numerator. This can be easily achieved by a centralized system, but not by Dapps built in the current ways in a decentralized system.

With anyCall, Curve has enabled the cross-chain transfer of generic messages, such as data and business logic between Child Liquidity Gauge and Root Liquidity Gauge. It marks a great attempt in exploring new forms of cross-chain Dapp. Curve can also easily and quickly build similar applications in a multi-chain environment with more than two chains. So far, the application has been deployed and tested on the testnet and is expected to be launched soon.
