3 ms·
OK, 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 'standar
by vessenes 11y ago
OK, 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.