Listener Functions

[OFRBG]

EIP: <>
Title: Listener Functions
author: Oscar Fonseca <hiro@cehh.io>
Type: Standards Track
Category: Interface
Status: WIP
created: 2018-08-19

Summary

Allow users to pay gas upfront and execute the call until a specific event has been triggered.

Abstract

Allowing developers to attach a conditional call to Ethereum events or other functions would prove useful. In order for this to work, the call needs to be done like every other on the mempool, except that miners are required to include that call if and only if the target event has triggered.

Rationale

Token contracts are usually monolithic and do not implement anything other than the balances and the token logic. Merchants or users might want to add listeners to the events. While this is possible via a setup with a node listening to the calls, end-users and developers using remote nodes have no way of achieving this. All in all, this would make the workflow of a task more efficient.

Example

It would be possible to make an airdrop for registered users with locked up "stake" ether. Users could call a listener function version of mint(). This call would be attached to a public function that may only be called after a certain block number. Once the participation period is over, the attached mint() calls are released, and the tokens are airdropped and the ether is returned to the users.

[fulldecent]

Evaluating the transactions takes time and resources (which are limited). So having an infinite pool of listening transactions, which are not paying gas, won't work.

BUT if you read the Yellow Paper there is a footnote about humans originating transactions which does apply to your situation.

[OFRBG]

I was thinking of solving the problem of

Evaluating the transactions takes time and resources (which are limited). So having an infinite pool of listening transactions, which are not paying gas, won't work.

with your proposal for rentals. These listener functions would pay a rent to be on the nodes. Listeners probably need a max lifetime, and if we implement the rent space, resource allocation is also served.

[fulldecent]

Okay, now I understand! Thanks for explaining.

[github-actions]

There has been no activity on this issue for two months. It will be closed in a week if no further activity occurs. If you would like to move this EIP forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.

[github-actions]

This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.