-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alarm Clock for Neo #660
Comments
I think this feature is not suitable for being built into the consensus. It is easy for a third party to create such a service, and they can send transactions periodically via RPC. |
It is possible to build a similar feature from external dapps, where tx may execute approximately on the expected time. To be precise, I think it must be linked with consensus, but approximate may be good enough for most applications indeed. |
Ok Hugo, this is more related to a Dapp idea than a Core change, so we will close this. |
Is there any plan to create an alarm clock for Neo Dapps? I mean, to submit transactions automatically from time to time? The transactions costs can be pre-paid by the user.
The consensus node could put the alarm clock on a pre-paid table and automatically execute from given periods, like cron.
Plus, to avoid large periods, the price could be exponential, for example.
By the way, I'm student of @igormcoelho and I'm taking my first steps in the platform. :)
The text was updated successfully, but these errors were encountered: