Skip to main content
LI.FI has upgraded its fee handling mechanism on supported EVM chains, migrating from the FeeCollector contract to a new FeeForwarder contract. This page explains what changed, what it means for your integration, and what—if anything—you need to do.

​
Why this change?

The previous FeeCollector model required fees to accumulate in a contract and be manually withdrawn later. This added operational overhead and delayed payouts to fee recipients. With FeeForwarder, fees are forwarded immediately to the configured recipient wallet at transaction execution time. No manual withdrawal step is required. The contract is also designed to support future multi-party fee distribution models, such as splitting fees between LI.FI, an integrator, and a reseller.

​
What changes for partners?

​
Immediate fee forwarding

On chains where FeeForwarder is deployed, transactions call the new contract and fees are distributed automatically at execution time. No action is required from partners.

​
Backward compatibility

On chains where FeeForwarder has not yet been deployed, the system automatically falls back to the legacy FeeCollector contract. Existing withdrawal endpoints remain available, and no API changes have been introduced. Fee data in /status responses is unchanged.

​
Event changes

For partners who parse on-chain events, the EVM fee event signature has changed. Previous event (contract): 
event FeesCollected(
    address indexed _token,
    address indexed _integrator,
    uint256 _integratorFee,
    uint256 _lifiFee
);
New event (contract): 
struct FeeDistribution {
    address recipient;
    uint256 amount;
}

event FeesForwarded(
    address indexed token,
    FeeDistribution[] distributions
);
This sample transaction shows fees forwarded directly from the LiFiDiamond address to the configured fee receiving wallets. The Status API has been updated to correctly parse the new event format. Fee data, including integratorFeeCost, continues to be returned in the same /status response structure.

​
What is not changing

  • No API response structure changes
  • No changes to fee configuration
  • No changes required in partner integration code
  • Solana, Bitcoin, Sui, and Move implementations are not affected
  • Existing fees accumulated in FeeCollector are not automatically migrated; they remain claimable via the existing withdrawal endpoints

​
Summary

FeeCollector (legacy)FeeForwarder (new)
Fee settlementAccumulated, claimed manuallyForwarded immediately at execution
Manual withdrawalRequiredNot required
Partner action neededNoneNone
Backward compatible—Yes, chains without FeeForwarder fall back automatically
This is a backend contract upgrade. Partners do not need to take any action.
If you have questions about fee configuration or how the Status API reports fees for your transactions, reach out via your usual support channel.