Skip to content
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

Learning from the Chronos project #3

Open
s1na opened this issue Aug 29, 2018 · 0 comments
Open

Learning from the Chronos project #3

s1na opened this issue Aug 29, 2018 · 0 comments

Comments

@s1na
Copy link
Member

s1na commented Aug 29, 2018

The great ChronoLogic team is working on a similar concept, called chronos.

Short intro

Chronos aims to achieve conditional execution, by having the user deploy a ScheduledTransaction contract, which contains the logic for checking whether the required condition (gleaned from the state) has been met. Upon seeing the new ScheduledTransaction, TimeNodes monitor the contract, and publish the signed transaction from the user to the network, when the condition is satisfied.

Analysis

Here's an attempt at learning from the benefits of their approach:

  • There's no need for the TimeNodes to provide proof, as the state can be checked on-chain on execution.
  • Condition is a view function, therefore no gas has to be paid for checking.
  • Signed transaction from users removes the need for using smart contract based wallets to do actions on user's behalf.

Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant