HIP-4: Use Keepers to Close Weekly Fee Periods
Use Chainlink Keepers for a decentralized automated closing of the weekly fee periods
Last updated
Use Chainlink Keepers for a decentralized automated closing of the weekly fee periods
Last updated
Type: Horizon Improvement Proposal Date: August 30th, 2022 Status: Draft 1 | Completed
Deploy a Keepers Upkeep contract and register a Keeper to automate the weekly fee period close.
Deploy a Keeper-compatible contract that automates the weekly period close to the BNB Chain mainnet
Register and fund the Keeper
The closeCurrentFeePeriod() function in the FeePool contract is responsible for closing the current week’s collected fees and rewards and starting a new period each week (Claim Day). This function will also migrate any unclaimed rewards from the previous claimable period to the current claimable period, snapshot the fees/rewards for users for the new claimable period, and start a new period.
While the Horizon Protocol team actively maintains the closure of the fee period each week, this can also be done by anyone in the community, as the closeCurrentFeePeriod() is a public function that anyone can execute.
The integration of Chainlink Keepers to automate this important protocol maintenance operation will help mitigate potential scenarios where the function isn’t called on time and help further decentralize the protocol.
The Keepers upkeep will require ERC677 LINK tokens, which will be funded by the Community Fund. The Keeper Upkeep charges a 30% premium (which is low relative to other networks) to the gas fee required to call the function in order to fund the upkeep operation on their network. The closeCurrentFeePeriod() function uses ~220,000 gas (~$0.30) on the BNB Chain mainnet, so the estimated cost of each transaction will be ~$0.40 paid in LINK tokens. Additionally, a Minimum Balance must be maintained in the upkeep or it will cease to function.
The implementation of this HIP might come with some risks, including the following:
A minimum balance of LINK tokens must be maintained in the Keeper or it will not perform the upkeep
Additional thoughts we should take into consideration:
Should there be any failure in the Keeper network, the community should be aware that they can also call the closeCurrentFeePeriod() themselves to help maintain the protocol.
If you have any questions or concerns, please do not hesitate to reach out.