Open ozimos opened 3 years ago
Noted, I'll research more on this.
Here is an example that includes the setup for the next schedule call in the initial schedule call https://ethereum.stackexchange.com/questions/27320/automatically-calling-a-contract-function-every-24-hours
Noted, I'll research more on this.
Officially this task falls to Samuel. However, he has not joined the repository yet. And I did not want to leave the task unassigned. Any help you can provide is appreciated
The code for this issue is now in the develop branch under the TriggerRebase.sol file. Testing needs to be done to validate the trigger works. If it works then this is a viable approach to regular automated triggers of the rebase function Next steps:
Noted, I'll research more on this.
Officially this task falls to Samuel. However, he has not joined the repository yet. And I did not want to leave the task unassigned. Any help you can provide is appreciated
Hey
The Problem
The AlarmClockSample function shows one way of calling a contract's function at a later date. This solution does not handle the repeated scheduling. Further research is needed.
Useful Links
https://docs.chain.link/docs/chainlink-alarm-clock#config https://ethereum.stackexchange.com/questions/42/how-can-a-contract-run-itself-at-a-later-time/59836#59836