I

Invincible Node

Providing interoperability between Ethereum and Polygon and based on leveraged liquid staking with stable-hedging, the Invincible Polygon aims to increase profits and liquidity as a Defi.

The problem Invincible Node solves

Polygon is one of the most scalable solution. We believe that our product, the Invincible Polygon, should further enhance Polygon’s scalability by increasing transaction throughput and decentralization. To achieve this goal, we must incentivize more users to participate in staking activities. Therefore, we aim to address the risks associated with staking, such as low profitability, price drops, and long unbonding periods. By offering a solution like leveraged liquid staking with stable-hedging, the Invincible Polygon will mitigate these financial risks and add value to $Matic, while also attracting assets from EVM-compatible chains to the Polygon ecosystem.

Challenges we ran into

We faced difficulty with staking on Polygon. At first, we tried to stake our $Matic on the Polygon network, but found that it wasn’t possible. After some research, we discovered that we had to delegate our $Matic on Polygon validators through the Ethereum network instead. This was a bit of a struggle for us at first, but we were able to figure it out with some persistence and the help of online resources. Despite the initial challenges, we believe that staking on Polygon is worth the effort due to its scalability and potential for high transaction throughput.
In the early stages of our product development, we initially retrieved token prices off-chain. However, we found that the data’s reliability was low. To solve this issue, we decided to bring the prices from an on-chain oracle and integrated Chainlink into our product. This increased the reliability of the data we were using.
We faced challenges in debugging and deploying our product due to the complexities of contract languages. To simplify the process, we used Hardhat and Remixd to connect our local repository to Remix. In terms of running our validator, we had to either operate it ourselves or connect to an RPC provided by the validator operator. However, we experienced issues with slow speeds when using a public RPC, which we were able to resolve by connecting to a faster and more stable RPC provided by QuickNode.

Discussion