0

I would like to create a generic ERC-20 token with identification. The token would only be transferred to previously identified addresses. The way identification is implemented should be as decoupled as possible from the token itself.

We also want to reuse this token in different scenarios (with different business rules). Is there any standard or reference to this goal?

  • reuse this token in different scenarios (with different business rules) - Do you actually expect to get a reference to that? It's like saying "I want to do stuff, can you give me a reference to this goal?"! – goodvibration Jun 22 at 20:05
  • I think I described what stuff means in this case. Glad if you can contribute – Suzana Maranhão Jun 22 at 20:10
  • With regards to The token would only be transferred to previously identified addresses - this is generally referred to as KYC (Know Your Customer), so you can look it up. With regards to reuse this token in different scenarios - like I said, this is a general statement, which I doubt that anyone can help you with (when you ask for something, you need to know what it is, and you to know how to explain to others what it is). – goodvibration Jun 22 at 20:13
  • The closes thing I know are security tokens. Polymath has an implementation github.com/PolymathNetwork/polymath-core. There are other proposals for the same type of token EIP 1450, and EIP 1462. – Ismael Jun 23 at 0:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.