# How can i set a specific custome migration fee for l2 blockchains

**URL:** <https://governance.aave.com/t/how-can-i-set-a-specific-custome-migration-fee-for-l2-blockchains/25562>\
**Category:** New Asset\
**Created:** [August 29, 2026, 8:23pm UTC](https://governance.aave.com/t/how-can-i-set-a-specific-custome-migration-fee-for-l2-blockchains/25562 "2026-08-29T20:23:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsadsadasdas3](https://avatars.discourse-cdn.com/v4/letter/d/ee59a6/32.png) [@dsadsadasdas3](https://governance.aave.com/u/dsadsadasdas3)\
**Post date:** [August 29, 2026, 8:23pm UTC](https://governance.aave.com/t/how-can-i-set-a-specific-custome-migration-fee-for-l2-blockchains/25562/1 "2026-08-29T20:23:44Z")

</div>

Migrating assets between Layer 2 networks shouldn’t come with surprise costs. A custom migration fee lets you control exactly what users pay instead of relying on volatile gas estimates.

Start in your bridge or rollup contract: add a

setMigrationFee(uint256 \_fee)

function guarded by

onlyOwner

. Store the value in a public state variable and call it in your migration logic, adding  
the fee to the transfer amount or deducting it from the bridged token.

Test on a testnet first, then verify the fee on-chain before mainnet. A fixed, transparent fee builds trust — users know the cost before they bridge.