Could someone share more light on the Perform Upkeep operation #5624
Unanswered
bayurzxsmtp
asked this question in
Q&A
Replies: 1 comment
-
hello friend, i think that 30 sec its the duration of the contract before a winner is picked. 30 seconds was just for development purposes to see if the contract is doing what it is supposed to, i think you can set days (in secs) as the duration of the contract. And again i think 30 secs is hard coded in config file because when we invoke the chainlink keepers with our contract it needs to know after how long does it need to return a random number which we then use to calculate the winner. That is what l think concerning the chainlink keepers and interval. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 I am working on the Raffle.sol code and I having a bit of difficulty understanding how the performUpkeep works.
Breakdown:
keepers has been replaced with automations and we need to pick between time based or custom logic. I guess custom logic flows better with what we were taught
One of the variables(constants) we are passing into the contract constructor is the interval/i_interval/keepersUpdateInterval. Please what is the purpose of this interval, is it to determine how long our raffle last or is it the interval it takes for the keepers node to check up on our contract?
If it is the interval it takes for the raffle to end why was 30 secs hardcoded to the hardhat-helper-config.js file I think it's a bit too short and why was it called keeperUpdateInterval?

Any idea or point of view will be deeply appreciated. Tanhks
Beta Was this translation helpful? Give feedback.
All reactions