PIP-87: Fixed Cost Payments Program This proposal introduces a fixed-cost program to provide predictable, fiat-denominated pricing on blockspace for payment companies building on Polygon. Fees from the program will flow to the ecosystem via PIP-82, PIP-85 and EIP-1559 systems. The goal: align the Polygon Chain’s pricing model with the requirements of payment providers, while strengthening the link between network usage and POL value accrual. See the PIP: forum.polygon.technology/t/p…

Giugliano Hardfork is now live on Polygon Mainnet for block number 85268500.

Giugliano Upgrade The Giugliano hardfork will be released on Polygon mainnet at block number 85,268,500, at approximately 2 PM UTC on April 8. This upgrade: enables faster finality by letting producers announce blocks earlier, adds fee parameters directly in block headers, and introduces new RPC support for fee data. All node operators must upgrade Bor to v2.7.0 (or Erigon to v3.5.0). See the countdown: polygonscan.com/block/countd…

After 6 months of observation and community discussion, its time to update @0xPolygon VEBloP economics. TL;DR: more equal distribution amongst validators, 50% fee directly to stakers.

Lisovo Hardfork is now live on Polygon Mainnet for block number 83756500.

Lisovo Hardfork The Lisovo hardfork will be released on Polygon mainnet before block number 83756500, at approximately 2pm UTC on Mar 4. This update: subsidizes agent-to-agent gas costs for payments (PIP-82), improves smart contract compatibility for the Count Leading Zeros (CLZ), includes better support for passkey-based wallets, enables flexible fee tuning, and includes improvements for more reliable transaction delivery and stronger checks. All node operators should upgrade Bor to v2.6.0 (or Erigon to v3.4.0). See the countdown: polygonscan.com/block/countd…

PIP-82: Agentic Commerce Gas Program This proposal calls for recycling up to $1M in gas base fees to promote Agentic Commerce transactions (using PIP-65). All non-recycled POL will be burned. See the PIP: forum.polygon.technology/t/p…

PIP-70 LIVE PIP-70 sets a higher minimum self-stake for new validators at 100,000 POL. Polygon PoS security depends on validators running reliable infrastructure and committing meaningful stake. This change strengthens network health and security, and aligns validator incentives with the network’s long-term health. Existing validators and delegators do not need to take any action. Read more on the Polygon forum: forum.polygon.technology/t/p…

PIP-69 LIVE With PIP-69, validator share tokens now show up as a 1:1 representation as dPOL, which improves wallet visibility and will expand the utility of staked POL. This enables full ERC-20 functionality to simplify the creation of POL liquid staking tokens (LSTs) and DeFi composability. If you’re already staking POL, you’ll see these tokens in your wallet. These may appear as dPOL, dPOL1 or dPOLa4 depending on your wallet. (This is not an airdrop) Read more on the Polygon forum: forum.polygon.technology/t/p…

Polygon PoS Network Update: Demand at All-Time High Polygon PoS just hit an all-time high for demand and single-day fees generated, with a burn of 3 Million $POL (0.03% of POL's total supply). This demand has led to a rise in gas costs for some users, caused by persistent block saturation. → Polygon uses an EIP-1559 fee mechanism. When blocks are consistently above the target utilization (currently 50%), the base fee increases to match demand high demand → fuller blocks → higher base fees What we’re doing now Moving fast to expand capacity and smooth fees as demand grows. Concretely, this means supercharging the network in real time: • Increasing gas limit from 60M to 65M, expanding network capacity by ~8–10%. • Preparing a hard fork to adjust EIP-1559 target gas limit, raising the utilization target above 50% to support fuller blocks that come with higher demand. → This means allowing more of each block to be utilized before fees rise, making gas prices more manageable and predictable under sustained demand. Gas prices should also normalize faster after a burst of activity. Security will remain the top priority as each implementation is made. What’s next • Short term: keep pushing toward 5,000 TPS • Medium term: continue execution on the Gigagas roadmap for long-term scaling For nodes, hard fork coordination details are coming shortly. We will share updates as each step rolls out. Thanks for your patience!

This afternoon, Polygon PoS experienced an issue affecting a subset of RPC nodes. The network remained online and continued producing blocks throughout the incident, with no chain downtime. The team quickly identified and rolled out a patch to operators to restore full service to nodes. Validators are currently syncing and arriving at the quorum. A number of RPC nodes remained fully operational during this period and transactions were flowing in and getting processed. The block explorer may still appear behind while nodes complete synchronization. For real-time network status updates, please refer to the Polygon status page: status.polygon.technology/