POLTRACKPOLTRACK

Priority Fee Distribution: PIP-65 / PIP-85

This page explains how Polygon Chain priority fees are allocated under PIP-65 and PIP-85. These mechanisms are implemented on the network also known technically as Polygon PoS. For general fee mechanics, start with Polygon Chain Fees. For how POLTRACK measures batches and validator income, see Methodology & Data Sources.

What PIP-65 Changed

PIP-65 changed how Polygon PoS priority fees are redistributed after block production. Instead of treating all transaction fees as a single economic bucket, priority fees are routed into distribution pools.

Under the PIP-65 model tracked by POLTRACK:

PoolShareRecipient logic
Block producer pool26%Directed to the elected block producer
Validator pool74%Distributed across validators by performance-weighted stake

These distributions happen in batches, not as smooth daily wallet payments. POLTRACK treats observed payments as realized distribution facts and keeps them separate from modeled daily fee generation.

What PIP-85 Adds

PIP-85 changes the downstream economics of the PIP-65 validator pool by allocating a staker/delegator share and changing the remaining validator-pool formula.

The PIP-85 formula specifies:

Block producer pool = 26% of total priority fees
Staker / delegator pool = 50% of the 74% validator pool = 37% of total priority fees
Remaining validator pool = 37% of total priority fees

The remaining validator pool is then weighted by the PIP-85 equality and performance formula rather than only the earlier stake-weighted approach. POLTRACK therefore labels PIP-85 staker fee yield as modeled economics until realized claim or payout artifacts are directly observable.

This is why POLTRACK separates fee-based staking APR from emission-based staking APR.

Why It Matters

Priority fees connect network usage to validator and staker economics. When transaction activity rises, the fee pool can become a more important part of staking economics. When activity falls, emission can dominate the yield picture.

PIP-65 and PIP-85 are important for:

  • validator income comparisons;
  • staker yield modeling;
  • fee distribution transparency;
  • analysis of how Polygon PoS activity flows back to network participants.

How POLTRACK Tracks PIP-65

POLTRACK reads PIP-65 distribution transactions from the Polygon PoS multisig and maps payments to validator records. The validator analytics product shows batch history, total received, pool share, and recent trend.

Validator fee share = validator PIP-65 amount / total validator pool

POLTRACK does not treat a modeled PIP-85 staker share as the same thing as a realized claim. Realized PIP-65 validator payments, modeled staker fee allocation, and future claimable/claimed PIP-85 artifacts are separate data concepts.

For the live product, see Validator Analytics. For the product guide, see Validator Analytics guide.

Data Limitations

PIP-65 batches can lag the underlying fee collection period. A payment observed on one date may represent fees collected earlier. POLTRACK therefore treats batch payment date, fee collection period, and validator state as related but not identical facts.

PIP-85 activation and distribution mechanics should be read from the canonical PIP text and public implementation evidence. If Merkle claimer contracts, roots, distributions, or reference code are not observable, POLTRACK keeps staker fee values clearly labeled as modeled rather than realized.

Common Questions

What is PIP-65?

PIP-65 is the Polygon PoS fee redistribution model that routes priority fee income to a validator pool and a block producer pool.

What is PIP-85?

PIP-85 changes priority fee economics by allocating 50% of the PIP-65 validator pool to stakers/delegators. That equals 37% of total priority fees because the PIP-65 validator pool is 74% of total priority fees.

Does PIP-65 income go directly to delegators?

PIP-65 tracks validator-side fee distribution. Delegator economics depend on validator commission, staking mechanics, and later fee-sharing policy such as PIP-85. Under PIP-85, delegator/staker fee sharing is a separate distribution path rather than the same thing as historical PIP-65 validator payments.

Why are payments batched?

The redistribution flow is settled periodically. That creates observable batch payments rather than a smooth daily payout stream.

How should I compare validators using PIP-65 data?

Compare total received, number of batches, pool share, and recent trend. Do not compare one batch in isolation.

Related Pages

Primary References