Proposal for full Polygon PoS support. Bridge launch and partial 'Timelock' treasury transfer

Greetings, dear WhiteSwap community! Expanding the protocol on to other chains is the utmost priority for us. Would like to discuss Polygon networks’ (PoS/zkEVM) integration onto WhiteSwap DEX. In this regard, we suggest to start with a separate proposal for Polygon PoS functionality where the community can discuss this idea in details.

Abstract

This Proposal encapsulates the comprehensive integration of Polygon PoS (Proof of Stake) solution into the WhiteSwap Decentralized Exchange protocol. The core objective of this integration is to substantially enhance our platform’s scalability, transaction speed, and cost-effectiveness while upholding the ecosystem’s inherent decentralized ethos.

Motivation

Blockchains are continually advancing, and one crucial aspect these days is the scalability of blockchain networks. In this context, WhiteSwap should prioritize supporting a wide range of L2 solutions that are future-proof. One of the promising solutions we aim to support is Polygon PoS.

This is one of the most advanced blockchain solutions right now. WhiteSwap aims to offer convenient, fast, and cost-effective transaction solutions for its users. This is why we propose to implement Polygon PoS blockchain in addition to existing Ethereum, Tron and Polygon (mainnet).

The integration of Polygon PoS, known for their scalability and efficiency, aligns with the overarching aim of fortifying WhiteSwap’s operational efficaciousness and user satisfaction.

WhiteSwap team fully supports this initiative and for the correct implementation of the DEX functionality and governance, it is necessary to set up the ETH-Polygon bridge and transfer part of the treasury from Ethereum to Polygon PoS respectively.

To execute the transfer of WSD tokens, WhiteSwap plans to launch the Bridge mechanism from the Ethereum network to the Polygon PoS network. This bridge would allow regular users to transfer their WSD tokens from chain to chain, as well as the DAO migrating part of the existing Ethereum treasury through the governance proposal.

The proposed WSD treasury transfer is next:

  • 2 000 000 WSD to from Ethereum to Polygon PoS treasury

Later, these tokens would be distributed through the liquidity mining and other initiatives for the protocol contributors. Each token distribution program is a subject to a separate governance proposal voting on the respected chains.

Specification

  • Integration Framework:
    1. Establish a robust framework for the seamless integration of PolygonPoS into the existing WhiteSwap DEX architecture.
    2. Engage blockchain developers and engineers to oversee and execute the integration process.
  • Security Audits and Performance Testing:
    1. For the Bridge mechanism, WhiteSwap leverages an existing Polygon solution called Polygon FxPortal for Polygon PoS. WhiteSwap has configured FxPortal solution, enabling the transfer of ERC20 tokens with governance functionality instead of regular ERC20 tokens.
    2. Develop a conducive testing environment to meticulously analyze the performance, identify potential bugs, and ensure the compatibility of integrated solutions.
  • Community Engagement and Feedback:
    1. Foster an open communication channel for community feedback and suggestions regarding the integration.
    2. Write reviews and posts to educate the community about the benefits and technical nuances of the integration.
  • As part of the transfer of governance WSD tokens from the Ethereum Timelock to the Polygon PoS Timelock, the following steps will be taken:
    1. WhiteSwap transfers WSD tokens from the Ethereum Vesting contract to the Ethereum Timelock contract using the “Claim WSD” function
    2. Grant approval to the Polygon PoS Bridge to access WSD from the Ethereum Timelock contract
    3. Move funds from the Ethereum Timelock contract to the Polygon PoS Timelock through the bridge

Benefits

The amalgamation of PolygonPoS into WhiteSwap’s framework is anticipated to provide more advanced blockchain solutions to our users. This enhanced efficiency is poised to significantly better the user experience, thereby potentially attracting a wider user base. Moreover, this integration heralds an avenue for further technological collaborations, fostering a culture of continual innovation and improvement within the WhiteSwap ecosystem.

Appreciate your input.
Thanks!

11 Likes

Hi guys,

congrats towards first little step towards revamping the protocol. Sounds good to me.
Would only wanna dive deeper towards 2m wsd transfer and potential impact.

1 Like

Nice! Polygon POS provides high speed and efficiency of transactions. As a result it makes an ideal option implementation for DEXes.

Agree on that one.I guess it allows you to process thousands of transactions per second, which ensures fast execution of orders on the exchange.

Speaking about the proposed wsd treasury transfer i fully agree with the total. This amount looks reasonable

Hello! This is fundamental proposal team!
Good luck on that.
I also think you should make some kind of collab with Polygon to boost this company

Hey everyone. Let’s discuss this idea.
I’d rather have some opposite opinion. What about network instability and security issue? If the Polygon POS network or ZkEVM technology periodically encounters problems such as network failures or long transaction verification times… It may affect the operation of Whiteswap and degrade our experience

1 Like

I think such integration might attract more traders as a result higher liquidity to the DEX so I support this proposal.

Yea, as a result, it has great impact on transaction costs, which became low. Polygon PoS’s low transaction costs make it attractive for traders, especially those executing multiple trades or smaller transactions, as they can avoid high gas fees associated with the Ethereum mainnet.

I also don’t like the idea to depend on third-party networks…

Really powerful idea guys. I truly want these project to develop and integrate in different structures of web3 world.

1 Like

Nicely done! Lets vote for this implementation :fire: :fire: :fire: