# BGD. Aave \<\> ParaSwap fee claimer **URL:** \ **Category:** Development\ **Created:** [November 16, 2022, 10:16am UTC](https://governance.aave.com/t/bgd-aave-paraswap-fee-claimer/10671 "2022-11-16T10:16:36Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![bgdlabs](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/bgdlabs/32/1829_2.png) [@bgdlabs](https://governance.aave.com/u/bgdlabs)\ **Post date:** [January 13, 2023, 2:03pm UTC](https://governance.aave.com/t/bgd-aave-paraswap-fee-claimer/10671/3 "2023-01-13T14:03:29Z")
After a [successful snapshot vote](https://snapshot.org/#/aave.eth/proposal/0x4fd357741900bfe62a863d1e3ec84fbf79bfebd5bdda3f66eee75b8845274b6d) the `AaveParaswapFeeClaimer` was deployed via CREATE2 as [`0x9abf798f5314BFd793A9E57A654BEd35af4A1D60`](https://etherscan.io/address/0x9abf798f5314bfd793a9e57a654bed35af4a1d60#code) on all supported networks. The Aave IPFS interface was updated to redirect fees to this address. As of today [~10k USD](https://www.aavetreasury.com/) in positive slippage has accrued to the new claimers across all networks. These fees can now be claimed in a permissionless way. For the previously accumulated fees (which currently are worth around ~100k$) they have to be claimed via governance or the Aave Guardian. The governance payloads are already prepared on - [EthereumClaimPayload](https://github.com/bgd-labs/aave-paraswap-claimer/blob/main/src/contracts/EthereumClaimPayload.sol) - [PolygonClaimPayload](https://github.com/bgd-labs/aave-paraswap-claimer/blob/main/src/contracts/PolygonClaimPayload.sol) and as there really won’t be any opposition, could be included in another proposal targeting treasury management, to reduce governance overhead. --- _[View the full topic](https://governance.aave.com/t/bgd-aave-paraswap-fee-claimer/10671)._