Make a Standard About Action Callbacks

[clesaege]

See the example of should-refill in http://1corp.io/snow/docs

-Function with the prefix should_ and the same parameters. -Return True if need to call.

Ideally the standard should allow to do: When function1 with args1 of contract1 returns true, call function2 with args2 of contract.

A deamon could watch the blockchain, calling function1 with args1 of contract1 at repeated interval. When it returns true. It should call function2 with args2 of contract2. Incentives could be made with a protocol like snow, the ethereum alarm clock (https://github.com/ethereum-alarm-clock/ethereum-alarm-clock) or another incentive system.

The goal is to be able to have deamon executing some functions of a smart contract which can be called by anyone (like passPeriod, executeRuling and oneShotTokenRepartition in https://github.com/kleros/kleros/blob/master/contracts/KlerosPOC.sol). This would greatly increase the user experience while using dapps.

[clesaege]

By the way, for now it seems we have to use bytes (or do some ugly stuff with the ABI), but we may get something cleaner and backward compatible when https://github.com/ethereum/solidity/issues/1707 will be implemented.

[clesaege]

For now, we'll have to make some sort of "hack", we can come back to standardizing when the required tools will be developed in solidity.

[clesaege]

As discussed in the slack, we can make a standard even without any hack.

"Call Function of Contract with Args when calling it would not revert". We could also specify an interval between each test calls and a maxtime after which we stop calling.

[n1c01a5]

The link http://1corp.io/snow/docs is broken (I don't find the new link).

[clesaege]

I warned Zack about it. They may have abandoned the project.

[clesaege]

No answer, the project seems to be dead, let's not rely on it.

[epiqueras]

By the way, for now it seems we have to use bytes (or do some ugly stuff with the ABI)

What for?

[0xferit]

Is this still relevant? @satello @clesaege