Disclosure: The author holds PAR. This is a technical guide to a public onchain contract, not investment advice. The caller can only execute the predetermined distribution, receives none of the fees, and cannot redirect the assets.

Part of the fees generated by PAR trading are burned directly, but the burn does not happen at the moment of every swap. Fees first remain inside the Uniswap v4 pool until someone calls collectFees(PAR). The locker then collects the fees, burns the protocol’s PAR share, and credits the remaining share to the creator’s fee account.

The function is permissionless. Any address may call it without administrator approval, a keeper whitelist, or a requirement to hold PAR.

This guide covers the complete process: inspect, simulate, submit and verify. You do not need to approve PAR or transfer PAR to any address. The caller pays only Robinhood Chain ETH gas and receives none of the fees.

1. Understand what the call does

The function:

collectFees(address token)

performs the following actions:

1. Collects accumulated LP fees from PAR’s locked Uniswap v4 position.
2. Calculates the protocol and creator shares using parameters fixed at launch.
3. Burns the protocol’s PAR share.
4. Credits the creator share to the fee escrow.
5. Distributes the quote asset under the same frozen rules.

The caller cannot choose the burn amount, change the recipients or redirect fees to itself. It merely presses a public execution button.

2. Verify the network and contracts

• Chain ID: 4663
• RPC: https://rpc.mainnet.chain.robinhood.com
• PAR: 0x507b6f349a80114097a67b8b4677367acc15b220
• PairPadLaunchLocker: 0x8a6d37B2E6a2AC7970eF69d2932757F04be0A231

Verification pages:

• PAR token contract
• PairPadLaunchLocker
• PAR official live statistics

Call the locker, not the PAR token contract. The transaction’s native value must be zero, and no ERC-20 approval is required.

3. Check for pending fees

Using Foundry’s cast:

cast call \
  0x8a6d37B2E6a2AC7970eF69d2932757F04be0A231 \
  "pendingFees(address)(uint256,uint256)" \
  0x507b6f349a80114097a67b8b4677367acc15b220 \
  --rpc-url https://rpc.mainnet.chain.robinhood.com

The two values follow the pool’s currency0, currency1 order and are returned in each asset’s base units. PAR has 18 decimals.

If both values are zero, there are no fees to collect and no reason to spend gas on a transaction.

4. Simulate before signing

Use the same RPC endpoint to simulate collectFees:

cast call \
  0x8a6d37B2E6a2AC7970eF69d2932757F04be0A231 \
  "collectFees(address)(uint256,uint256)" \
  0x507b6f349a80114097a67b8b4677367acc15b220 \
  --rpc-url https://rpc.mainnet.chain.robinhood.com

The simulation should succeed and return the two asset amounts available for collection. If it reverts, do not force a broadcast. Check the network, locker address, PAR parameter and current pool state first.

Simulation does not alter onchain state or consume gas.

5. Trigger the call through a wallet or block explorer

Method A: verified contract interface

1. Open the PairPadLaunchLocker contract page.
2. Open the contract write interface and connect a wallet.
3. Select collectFees(address).
4. Enter the PAR address: 0x507b6f349a80114097a67b8b4677367acc15b220.
5. Confirm that value is zero.
6. Review the gas estimate and sign.

Method B: wallet with raw-calldata support

Chain ID: 4663
To: 0x8a6d37B2E6a2AC7970eF69d2932757F04be0A231
Value: 0
Calldata: 0xa480ca79000000000000000000000000507b6f349a80114097a67b8b4677367acc15b220

0xa480ca79 is the selector for collectFees(address). The remainder is the left-padded PAR address.

6. Verify that the burn occurred

After confirmation, do not rely only on a website’s success message. Check at least four pieces of evidence:

1. The transaction receipt status is successful.
2. PAR emits a Transfer from the locker to the zero address.
3. A fresh pendingFees(PAR) read is close to or equal to zero.
4. The reduction in PAR’s totalSupply matches the zero-address transfer.

A corresponding transfer of the creator share into fee escrow provides an additional check that both sides of the distribution executed as predetermined.

7. A live execution example

On October 15, 2026, an ordinary community wallet collected:

• 2,957,409.099700 PAR in fees;
• 1,478,704.549850 PAR was burned directly;
• 1,478,704.549850 PAR was credited to the creator fee account;
• pendingFees(PAR) fell to zero;
• gas cost 0.000005355353632 ETH, or roughly 1.25 cents.

Verify the transaction:

• Blockscout
• Hoodscan
• Stonkscan

The cumulative buyback-burn figure did not change across the transaction. The entire increase therefore came from PAR-denominated trading fees, not a buyback.

8. Safety checklist

• No PAR approval is required.
• No PAR transfer is required.
• Native value must be zero.
• Call only the verified locker address.
• Simulate with eth_call or the wallet before submitting.
• Never paste a private key or seed phrase into a website, chat or shell command.
• Prefer a hardware wallet or the wallet’s own contract-call interface.
• When pendingFees is very small, triggering the transaction may not justify the gas cost.
• If someone calls first, your transaction may collect almost nothing or return zero.

9. Conclusion

PAR’s direct burn is not a private backend task reserved for the project team. It is an open onchain operation: anyone can inspect pending fees, simulate execution and trigger the predetermined distribution.

Permissionless does not mean automatic. It provides the community with takeover capacity. When the official keeper does not execute, another participant can complete the final step without asking for permission.

Verifying the burn does not require trusting the project or a statistics page. Transaction events, the zero-address transfer, the supply reduction and cleared pending fees form a complete and reproducible evidence chain.