5 ms·
* Recurring and Scheduled payments. On the first of every month, the alarm service pings my wallet to pay my utility bill. Most of the other potential applica
by pipermerriam 11y ago
* Recurring and Scheduled payments. On the first of every month, the alarm service pings my wallet to pay my utility bill.
Most of the other potential applications it's easy to argue that they could set up their own incentives to get some user in the system to execute the call. (lottery payout, scheduled trade, crowdfunding payout, etc).
I think that yes, each of those applications has a viable way of motivating some party to execute the call. However, if a service like Alarm proved to be very reliable, it may be simpler to just automate it with a scheduling service. Scheduled or recurring execution doesn't have to be the only solution to a problem for it to still be a good solution.
- vessenes 11y agoOK, that's interesting, and I agree that for the use case you specify you're essentially fixing a hole in the ethereum specification / building out the 'standard library' in a useful way. If I were running it, I would still make strong recommendations that recipients of the alarm 'ping' only execute idempotent functions which do not rely on any data from the ping itself, or on the ping being executed implying any state anywhere in the world, whether on blockchain or not.
- pipermerriam 11y agoA point of clarification. All call execution is just a ping. If the call requires call data it is supplied by the scheduler and cannot be manipulated or changed by the caller. All call execution is relayed through the alarm service so it only relies on the executor to initiate the transaction and then the alarm service does all of the rest.