Conditional Scheduling made simple — introducing Automate
Automate now! https://automate.chronologic.network/
Automate is our take on hybrid conditional scheduling. It allows users to execute conditional transactions in a cheap and efficient manner by trading-off some of the decentralized protocol properties.
It takes advantage of Ethereum signed transactions to ensure the security and adds a conditional layer on top to make sure that a transaction won’t be executed before certain conditions are met.
Let’s now walk through some of the components and features of Automate.
Transaction
Automate expects correctly signed standard Ethereum transaction as an input. In fact, all Ethereum wallets produce such transactions and broadcast them to the network.
For that, you can use tools for offline transactions on popular wallets like:
MyCrypto https://legacy.mycrypto.com/#offline-transaction
MyEtherWallet https://www.myetherwallet.com/#offline-transaction
Condition
This is the conditional part of Automate. Conditions are guarding the transaction and are tested periodically before the execution.
The most generic representation of what Automate does is:
In the current version, we allow users to set the condition for ETH or ERC-20 token balances. To simplify the process, we provided a tool to create such conditions.
Such a condition can be represented as:
E.g.:
Sender balance of ETH is greater than 2.
Receiver balance of DAY token is greater than 100.
0x9012C0e070e67f433e363bFfb7B6F03427654e2c balance of DAY token is lower than 1000.
In the future, we are planning to provide the possibility to use any Smart Contract return value, event occurrence or transaction.
Multi-nonce support
Automate makes sure that transactions are broadcasted in the correct order by their nonces. This means you can schedule many transactions ahead, yet the execution will occur in a serial fashion, from the lowest nonce to the highest.
Multi-network support
We are currently supporting the Ethereum MainNet and all Ethereum Test Networks.
Support for more networks coming soon!
Execution
As of now, Automate relies on a backend system for watching and execution that is run by ChronoLogic. This approach is different from our decentralized protocol Ethereum-Alarm-Clock or Chronos, where execution is provided by the second layer execution market.
User interface
Automate vs Chronos vs Ethereum-Alarm-Clock
Here, I want to compare other solution in that space that we are working on at ChronoLogic, even though most of you are familiar with Ethereum Alarm Clock protocol and our research project, Chronos.
