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

ERC1592 Address and ERC20-compliant transfer rules #1597

Closed
sirhill opened this issue Nov 19, 2018 · 3 comments
Closed

ERC1592 Address and ERC20-compliant transfer rules #1597

sirhill opened this issue Nov 19, 2018 · 3 comments
Labels

Comments

@sirhill
Copy link
Contributor

sirhill commented Nov 19, 2018

Simple Summary

We propose a standard and an interface to define transfer rules, in the context of ERC20 tokens and possibly beyond.

A rule can act based on sender, destination and amount, and is triggered (and rejects the transfer) according to any required business logic.

To ease rule reusability and composition, we also propose an interface and base implementation for a rule engine.

Abstract

This standard proposal should answer the following challenges:

Enable integration of rules with interacting platforms such as exchanges, decentralized wallets and DApps.
Externale code and storage, improve altogether reusability, gas costs and contracts' memory footprint.
Highlight contract behavior and its evolution, in order to ease user interaction with such contract.
If these challenges are answered, this proposal will provide a unified basis for transfer rules and hopefully address the transfer restriction needs of other EIPs as well, e.g. EIP-902, EIP-1066 and EIP-1175.

This document proposes specifications for a standard of transfer rules and interfaces to both the rules and the rule engine, which was made to be inherited by a token, but may have a much broader scope in the authors' opinion.

The last section of this document illustrates the proposal with a rule template and links to rule implementations.

Draft document

A draft already exist and can be found here #1592
Its content can be discussed below.

@aquabu
Copy link

aquabu commented May 31, 2019

@sirhill This looks similar to #1404 #902 and #1066 which have some momentum.

@github-actions
Copy link

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 github-actions bot added the stale label Nov 21, 2021
@github-actions
Copy link

github-actions bot commented Dec 5, 2021

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.

@github-actions github-actions bot closed this as completed Dec 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants