Comment on page
Cross Chain
Our cross-chain infrastructure architecture adopts a hub-and-spoke model with Ethereum as the main chain and other chains serving as side chains. All message passing is aggregated on the main chain, which then performs computations and distributes the results to the respective side chains. This approach ensures data consistency between the chains and delegates all computational processes to the more secure Ethereum network.
Initially, we will follow Pendle's footsteps and deploy on Ethereum and Arbitrum. To address the high cost of participating in PENDLE votes, we have optimized the voting functionality of EQB and deployed it on multiple chains. This way, if users do not want to accept the high costs associated with the mainnet, they can choose to vote on Arbitrum.
Moreover, to ensure the unity of the token economy, we have implemented a deflation mechanism that synchronizes across all chains.
All the cross-chain features are built on top of Layerzero.
Protocol fees will be generated across multiple chains, but we believe that a multi-chain ecosystem should not operate independently. Instead, it should function as a unified entity with shared token mechanisms and fees. This approach allows users to freely choose the chain they prefer to use. Unlike deploying on individual chains separately, where fee calculations may differ, we employ a consolidated reporting method to calculate the fees generated by each chain.
Then, based on the proportion of ePENDLE and vlEQB held on each chain, their respective fees are determined. After calculation, rewards are distributed to each chain. In cases where time discrepancies occur due to bridges, we will utilize reserve funds to facilitate the timely disbursement of rewards.
For example, in an extreme scenario where all users choose the cheaper option of Arbitrum to lock EQB, the protocol fees that should be allocated to EQB on the mainnet will be entirely distributed on Arbitrum.
Last modified 5mo ago