hackbg / chainlink-makerdao-automation Goto Github PK

Instead of calling approve for DAI and LINK in the top up function

Ex: https://github.com/beefyfinance/beefy-contracts/blob/master/contracts/BIFI/keepers/contracts/UpkeepRefunder.sol#L150

So we can build a dashboard like this one: https://dune.com/wei3erHase/MakerDAOUpkeep

• "Nice to have" optimization
• No impact since it's a view function called by keepers

Must be possible to deploy the contracts independently.

Todo:

• Split deploy script into two separate
• Update docs with instructions which functions need be called to link the contracts

implement functions from contract:

• getUpkeep
• getMinBalanceForUpkeep
• addFunds

helper functions:

• setBalance
• setMinBalance

https://forum.makerdao.com/t/mip63-maker-keeper-network/12091

Keeper Networks should have a mechanism for receiving one-time payments. This can be used in emergency situations to top up the buffer without having to go through an executive vote.

AC:

• use hardhat-deploy plugin
• flows for hardhat/local, testnet/staging and mainnet/prod
• reuse fixtures in tests

• Sequencer
• Job

Currently during unit and staging tests the excess payment amount stays in the contract.

SwapRouterMock contract should be able to take tokens from the vest and use Vest event as we are currently relying on that vested tokens are left in the contract which shouldn't be the case.

Include:

• Overview
• Architecture diagram
• Setup instructions

Background:

• Currently end-to-end tests are running on a fork of Goerli testnet until the mainnet deployment of KeeperRegistry v2

Todo:

• Switch to mainnet and drop the additional staging env variables

AC:

• check that jobs are executed and upkeep is getting refunded
• run on forked mainnet
• simulate upkeep calls via the registry

Use NatSpec