Call for Feature Requests - Polygon PoS: Pilani Upgrade

Polygon PoS: Pilani Upgrade

Call for Technical Feature Requests

Polygon PoS developers have decided on a name for the upgrade following Ahmedabad. Now formally named Pilani, the upgrade will likely take place in Q4 of 2024 and provides an opportunity to add a range of new features and optimisations to the Polygon PoS chain.

What We’re Looking For

Community-driven innovation is at the core of Polygon PoS development. The network’s strength lies not just in its technology but also in the collective vision and contributions of its vibrant community of developers and users.

We want your feature requests across all aspects of the Polygon PoS network. Here are some areas where your ideas can make a significant impact:

1. User Experience:

  • Features that make the network more user-friendly and accessible.
  • Enhancements for wallets, explorers, and other user-facing tools.

2. Scalability Improvements:

  • Enhancements to transaction throughput and latency.
  • Solutions for handling network congestion and increased capacity.

3. Decentralisations/Security Enhancements:

  • Improvements to existing security protocols and mechanisms.

How to Submit Your Feature Requests

Simply comment below. We are not specifically looking for long-form answers here; that is what PIPs are for!

In a couple of sentences:

1. Identify the problem/area of improvement:

  • Define the problem or opportunity your feature addresses.

2. Propose a solution:

  • Outline your solution; relevant technical details are appreciated.

3. Explain the benefits:

  • Highlight how the feature will benefit the Polygon network and its users.

Whether you’re a developer, a user, or simply an enthusiast, your insights are invaluable in driving the development of the Polygon PoS chain.

I look forward to hearing your thoughts and encourage you to provide feedback however you see fit.

11 Likes

I propose PoS including the Point Evaluation precompile found at 0x00…0A on Ethereum Mainnet specified in EIP-4844 to further support EVM compatibility

2 Likes

I propose we get an AggLayer connection please!

3 Likes

I believe now is the time to considering a large upgrade to current functionality + an extension to PoS.

  1. PoS should upgrade to the Unified LxLy bridge, paving the way for connection to the AggLayer.
  2. PoS should include a new role which is able to post data to the Agglayer to perform bridge updates. To begin this can happen without any changes to PoS to use execution proofs, and can instead rely on the pessimistic proof + the existing pos finality guarantees.
5 Likes
  • Top feature needed is the move to zkEVM validium, we know this is coming but adding it here anyway as I think it should be a top priority (I’m sure it is already :slight_smile: ).

  • Improve polygonscan, especially the token approvals which is a pretty broken feature. Polygonscan may not be necessarily an in-house polygon issue, but it is something that would significantly enhance the user experience. Many people don’t know what they’re doing on-chain, and making the “reading the chain” process as simple as humanly possible can only be a benefit to new users. Outside of wallets, chain history is a major choke point for less tech savvy (or time constrained) potential users. This would also make it easier for content creators to amplify Polygon’s features. Built-in complex and simple analytic tools for all levels of those wanting to interact, contract analyzers, efficient audited contracts listings, ability for new contract creators to easily upload imagery to associate their contracts with their projects and to claim their contracts as part of their platform, more clear labeling for multi-step transactions involving dapps, etc. this could all be relayed to CDK chains and could be a strong basis for an AggLayer analyzer. This could really separate Polygon in the space.

  • Use the monad client, idea taken from JD originally, or learn from their approach. Per Samuel Furter on X “A simple TX tracer and slightly customized Trie implementation (if actually needed) would make it ZK provable as well”. I would imagine a zkMonad client would be insanely efficient under load.

  • A permissionless “building on POS” website, categorized and sub categorized by sector of web3, features, etc. teams could submit their own projects and project details, which would give them a marketing/visibility edge. this would be great as a basis for CDK chains and AggLayer integrations so their is easy access visibility about what’s being built, gives creators a great space to find projects of interest to amplify. Gives contract auditors a place to quickly find projects to sell services to. Could also include sections called “last called” and “exploited”, that shows when the last usage was to indicate if a product has gone ghost/defunct and when/how a project was exploited and if there was a fix. This could be lumped into the same site as chain analyzer.

  • CEXs offering direct Polygon on-ramps. Could also be included in the same website with the above items.

  • AggLayer integration (I know this is coming too).

  • Might add more later! Thanks for providing a forum for us to share ideas.

1 Like

Posting a community request for an ed25519 curve precompile.

h/t @pedrouid
https://x.com/pedrouid/status/1800294803139182858

1 Like

Linking a previous post from @sxtcat Support for BLS12-381 Curve Operations

1 Like

Bring Bor close to the upstream improvements made on Geth, especially PathDB. It enables efficient state management and pruning. #1, #2 and #3 are obvious and well documented.

1 Like

Goons,

Corn from Yearn here. We’ve completed building a new product called Stake The Bridge (STB) and we’d like to have it considered for integration in the Pilani upgrade. This product was built for any Polygon CDK partner to integrate so they can earn yield natively and make even idle assets productive.

Native Yield is big meta right now, and STB allows a user to bridge from an L1 to the L2, while the asset is generating yield on the L1, and the user receives a vanilla token on the L2.

The idea is to take that yield on the L1 and make it productive. For instance, I propose we take that yield and buy back $MATIC tokens and put them into a grants treasury. We can do what we’d like with the yield.

Some strategies and assets we can start with are:

USDCe - yvUSDC
USDT - yvUSDT
ETH - stETH
DAI - sDAI
FRAX - sFRAX

This product is built and ready for integration right now:

Design docs and code: https://github.com/yearn/yearn-stb
Audit: https://reports.yaudit.dev/reports/05-2024-Yearn-STB-yAudit-report/

3 Likes

I propose upgrading heimdall’s tendermint fork with the newer CometBFT, coming in with enhanced ABCI++ features.

2 Likes

One improvement for heimdall is also to bump up cosmos-sdk version to latest (v0.50.x) in order to leverage the new set of functionalities available upstream

2 Likes

@ConstantinoTheGreat @pgpg @Web3corey sharing a new post from @pgo & Uma on Phase 1 of zkPoS connecting PoS to AggLayer

https://forum.polygon.technology/t/pre-pip-discussion-zkpos-phase-1-connecting-to-the-agglayer/14250

1 Like

speaking only in my capacity as an individual member of the polygon community, as a user, staker and dev - I am strongly supportive of a limited trial of Stake-The-Bridge on PoS - potentially on DAI (via sDAI similar to how zkEVM is setup), legacy USDC.e (ideally with a 1:1 redeemable solution such as stUSD or a Morpho Blue Vault such as those from Steakhouse or Gauntlet), and FRAX (via sFRAX) managed via yearn v3 vaults.

I would hope that any strategy / proposal ensures that all assets can be instantly or near instantly redeemed should liquidity be needed, without penalty, and yield is of sufficient size to be worth the integration/risk.

I also believe that all yield should either flow to stakers to offset the decreases in staking yield called for by the staking schedule, or to burners used to buyback and burn POL.

2 Likes

Hey guys,

Pablo from Angle here! Thanks for the initiative here.

The USDC & USDT big opportunity cost

Like some suggested above, I do think that finding ways to earn a yield on the USDC and USDT that are kept idle on the Polygon bridge contract on Ethereum L1.
This wouldn’t be a novel thing to do for a chain and the playbook of Gnosis Chain and Blast kind of speaks for itself.
At current rates and taking for a baseline the 5% risk free from US Tbills (even if in DeFi currently there are ways to get better rates than this), this is approximately:

  • $50m that is lost away in yield every year to Tether with the USDT held
  • $10m missed out on by holding USDC instead of other yield opportunities.

I’m not that deep into the Polygon DAO to know what’d be the best way to allocate this money, but I just know that there is an easy catch to do, and that one should never say no to at least $60m in revenue on a yearly basis.

Taking advantage of a permissionless yield bearing stablecoin

Ok there’s $60m to be made, but what’s the best way to actually get this knowing that:

  • you don’t want to risk funds that are bridged and prevent users from going back to mainnet: what if the USDC/USDT are invested in a protocol that gets hacked or in a centralized solution that leaves with the money? Risk tolerance should be very minimal and I don’t think that the policy should be about going for the maximum yield, but rather the highest risk-adjusted yield
  • you want to care for the liquidity of the underlying sources here. Typically let’s say that the USDC investment is solvent but you can only redeem USDC back from what was bridged at T+1, this creates a pretty bad experience for the user bridging back. And so typically, a liquidity buffer needs to be thought of or aim should be for the most liquid products possible (redeemable instantly)
  • not all yield products can be accessed permissionlessly. There are many solutions which impose a KYC on the primary market. While tracking customer funds and doing some AML is key to unlock integrations with the “real-world”, this is often inadequate for smooth and permissionless solutions like the Polygon bridge. There are some yield-bearing stablecoins which through an optimistic approach are able to pass these KYC requirements and unlock access to these yield markets.

I’ll be speaking for our own name at Angle, and there may be other solutions to look into, but I want to suggest the Angle USDA stablecoin, with its stUSD yield solution as a candidate for a yield solution if this had to be implemented.

Angle yield solution and stUSD

Angle is a decentralized stablecoin protocol behind 2 stablecoins, USDA and EURA.

Our stablecoins are fully backed and collateralized and work with several submodules, including a smart price stability module enabling anyone to mint USDA with USDC, and a borrowing infrastructure enabling people to borrow our stablecoins from secured.
The protocol is earning a yield on its reserves (borrowing interest, tokenized securities - RWAs held in the backing, very low risk DeFi lending strategies) and this yield is allocated to people who deposit their USDA into our stUSD yield product.
Average APY for stUSD over the last 30 days was 18.2% (APY was high because not all USDA are in the savings product but savings product receives full yield earned on all the USDA)

You may find more detailed docs for how the stablecoin works and operates here.
As a fully decentralized and onchain system, the backing and the reserves of the stablecoins can be accessed transparently and in real-time on our analytics dashboard.
The protocol is of course fully audited and the systems behind Angle have been running in production for almost 3 years now (on the Euro stablecoin at first)

In general, Angle stablecoins are meant to optimize (and in this order) for:

  • solvency: reserves are managed by the DAO, but DAO is advised by an asset liability management committee made up of professionals like the Steakhouse Financial team. The equity to liability ratio of USDA is the highest among all other USD stablecoins.
  • liquidity: there are no fees for minting or burning USDA. The stablecoin can be minted and burnt with no fees from USDC. From the Polygon perspective, there will be no fees taken when entering or leaving from a position in USDA and stUSD. The protocol also keeps a liquidity buffer to ensure there is always enough USDC available when burning the stablecoin
  • yield: the goal of the protocol is to optimize its balance sheet under solvency and liquidity constraint. The policy for the stUSD yield product is that it should offer the best of very low-risk . We’re risk averse in essence, so while we do our best to earn a yield, yield is sourced from the lowest risk platforms. Typically, protocol lends USDC on Morpho immutable lending protocol, or buys securities tokenized by Backed to earn the RWA yield.

All of this should make Angle and stUSD a perfect candidate for Polygon’s needs.
Contrarily to other solutions in the market, Angle stUSD is also not going to deprecate any time soon, and so this could be a long lasting solution to serve Polygon use cases.

Probably going too far, but if we go with a full-scale integration for this, we could envision a deeper integration where Polygon also unlocks ownership into the Angle Protocol based on the TVL and volume contributed. This way, Polygon would not only earn the yield that the protocol is providing but also get ownership into the protocol, making USDA & EURA become de facto Polygon stablecoins.

Happy to further discuss on this in case there are any questions.

3 Likes

Objective:

Implement a feature that allows partial detachment of a validator’s own stake without compromising its position or status.

Key Features:

  1. Controlled Detachment: Enable a validator to be temporarily detached from the system without affecting its validity or permanent status. Currently, it is not possible to remove any own stake without being expelled as a validator.

  2. Security and Access Control: Ensure that only authorized users, such as validators, can perform the unbonded.

Technical Requirements:

  • Compatibility: The feature must be integrable with the currently used infrastructure.
  • Performance: Maintain system performance within acceptable limits during and after the unbonded process.
  • Security: Implement robust measures to protect against unauthorized access.

Constraints:

  • Minimum Downtime: Minimize downtime caused by unbonded and reconnection of the validator.
  • Minimal Impact on End Users: Ensure that operations visible to end users are not affected during the unbonded process.

Impact:
The implementation of this feature should not negatively impact the core functionalities of the validation system.

2 Likes

Interface Configuration for Matic to POL Migration

Objective:
Develop an intuitive interface that allows users to migrate from “MATIC” to “POL” and continue staking using the same validator.

Key Features:

Selection of Network: Allow users to select between “MATIC” and “POL” within the interface.
Simple Migration: Option to seamlessly migrate user funds and staking position from “MATIC” to “POL”.
Continued Staking: Ensure users can continue staking with the same validator after migration.

Technical Requirements:

Integration: The interface must integrate directly with the blockchain networks.
Security: Implement robust security protocols to protect migration transactions and user information.
Compatibility: Ensure the interface is compatible with various devices and browsers.

Migration Steps:

Authentication: Ensure secure and authorized access.
Network Selection: Allow users to choose between “MATIC” and “POL”.
Migration Confirmation: Confirm the migration of funds and staking position.

Benefits:

Ease of Use: Simplify the migration process to enhance user experience.
Continued Participation: Enable users to continue supporting with the same validator without significant interruptions.

2 Likes

Hi, I would like to request an upgrade of the PoS Staking contract so that Validators are able to remove stake freely from their node.

Currently the only way to remove some Matic/Pol is to renounce our node as a Validator, which is … far from ideal. This is more a bug than a feature, and it would be great if it is fixed.

1 Like

I believe an upgrade to cosmos-sdk-v0.50.0x and cometBFT is overdue.
This will especially provide a fix for the vulnerability in IAVL state proofs that allowed the binance bridge hack of 2022.

https://x.com/samczsun/status/1578172227400310786?lang=en

The only way to trustlessly bridge to Polygon POS is to verify the Milestones included in the Heimdall state tree, but Heimdall is still using the initial IAVL spec that can possibly allow a fake milestone to verify successfully with a forged proof.

An upgrade to the ICS23 IAVL spec in the newer tendermint or CometBFT consensus will fix this.

1 Like

RWA Initiative for the Polygon POS Bridge

Hi everyone - Grayson from k/factory, a core contributing organization to the Centrifuge protocol.

Size of the Opportunity / Problem

In looking at the top USDT and USDC holders ranked on Ethereum, the Polygon bridges sit at #7 for Tether with $915M, and also #7 for USDC with $305M. This alone is $1.2B in stablecoins not accruing TVL to the Polygon Network, and not earning yield for the community.

Solution: Ultra-safe RWAs

We propose taking a small portion of stablecoins (USDC & USDT) in the Ethereum bridge, and investing them into T-Bills native to the Polygon Pos Chain, or other applicable Polygon chains. The Anemoy Liquid Treasury Fund currently yields ~5.15% (net of fees), meaning a conservative 20% allocation from stablecoins could earn an annual yield of $12.4M that otherwise doesn’t occur.

The following is an example with solely T-Bills, although other assets could be implemented as well:

This solution would take x% of idle stablecoins in the USDC and USDT Ethereum bridges, and invest them into T-Bills in the form of the Anemoy Liquid Treasury Fund.

Some example key parameters being:

  • RWAt - the target allocation to T-Bills (ex. 20%)
  • RWAUB - the upper bound allocation (ex. 25%)
  • RWALB - the lower bound allocation (ex. 15%)

This allows the bridge to maintain RWA allocations within a certain defined range. If T-Bills in this scenario reach 25% of the bridge, 5% would automatically be sold for stablecoins to revert to the 20% target and vice-versa.

There is also a significant opportunity to integrate other asset classes such as corporate bonds and various forms of private credit purpose built for the bridge. We are happy to explore!

Centrifuge is unique in its ability to work with DAOs to build out the legal and operational infrastructure to access permissioned products through our Centrifuge Prime offering. This would allow a real world foundation to be set up on behalf of the bridge to execute orders from governance.

About Centrifuge

Founded in 2017, Centrifuge is one of the original and largest real-world asset protocols, having financed over $600M in assets. Some of our previous work includes working alongside MakerDAO, BlockTower Capital, GnosisDAO, Frax, Morpho, and Aave.

Centrifuge is asset-agnostic, and multi-chain by design. Centrifuge works with many asset managers to bring funds and assets onchain, to any EVM compatible network. We currently support Ethereum, Base, Arbitrum, and Celo, with capability to support Polygon if the proposal moves forward. This proposal would not only benefit the community in earning yield and growing TVL, but be the catalyst for RWAs expanding on the network.

We propose that Polygon initially allocate to the Anemoy Liquid Treasury Fund consisting of U.S Treasury Bills due to the conservative nature of T-Bills matching what’s needed for this integration with Centrifuge. It’s important to note that as a next step if requested by the community, higher yielding products like corporate bonds, or tokenized DeFi yield funds could be added as well with partners like BlockTower Capital.

About the Anemoy Liquid Treasury Fund (LTF)

Quick Links:

The Anemoy Liquid Treasury Fund invests exclusively in U.S T-Bills with a maximum maturity of 6-months, focusing on maximizing interest rates and minimizing price and duration risks. U.S. T-Bills are held directly by the fund with the U.S custodian, and the individual asset holdings can be viewed onchain 24/7, and can be redeemed within 8-48 hours. The fund is a BVI-licensed fund open to non-U.S Professional Investors.

View the fund in our app

Below you will find the current asset makeup of Anemoy’s Liquid Treasury Fund as of 6/20/2024.

The Centrifuge app takes transparency seriously as a core value to investors and the public. In the assets tab, anyone can see the individual Bills held by the Anemoy Liquid Treasury Fund, with the ISIN/CUSIP securities identification number available.

Above is a detailed view in the Centrifuge UI of a single T-Bill security.

Source: Anemoy Deck

Benefits of the Anemoy structure include:

  • ‍Daily Liquidity: The fund offers daily redemption orders with settlement in 8-48 hours depending on market hours.
  • Direct Ownership: The tokens serve as direct evidence of ownership of the fund shares, allowing cost-efficient redemptions and providing full legal claims on assets.
  • Investor Protection: Prospective investors must adhere to the Know Your Customer (KYC) and anti-money laundering requirements of a BVI-regulated professional fund, ensuring a secure and transparent investment environment well-protected from regulatory risk and sanctions enforcement.
  • Transparency: Centrifuge provides near real-time onchain visibility of holdings, returns, and tokenized U.S. Treasury Bills.
  • Ulta-low fees: Fees for the fund are 15bps annually (7.5bps Anemoy management fees + 7.5bps Centrifuge protocol fee).

Anemoy LTF tokens are the individual shares in the BVI fund, and come with full legal shareholder recourse rights to the underlying assets under BVI law (shares are issued as tokens following BVI law). The token price directly reflects the NAV of the fund with fees already withheld from the price. The NAV is updated daily or when an investor invests/redeems in the fund before any investment or redemption. The token is not a rebasing token.

As RWAs continue to grow in sentiment and size, we think key initiatives like this within decentralized networks have a chance to push both DeFi and RWAs forward. Centrifuge is uniquely positioned to be able to work alongside decentralized organizations as demonstrated by experience, and our platform being the one-stop shop for RWA integrations and offerings as demand for different assets arise.

We look forward to engaging with the community on this initiative to answer questions, and dig deeper into the details. We hope that by sparking these initial conversations, we can further develop a RWA strategy for the network/DAO.

2 Likes