-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
Security Token implementation #1322
Comments
@darioAnongba Here's the reference implementation I'm happy to collaborate and help! |
I would be happy to collaborate on this. Count me in! |
I'm working on the implementation that is more compliant with the draft ERC and will share it here. |
Thanks @MichalZalecki ! |
Any news about this topic? |
@jochenonline Currently the go-to resources are: https://github.com/SecurityTokenStandard/EIP-Spec and https://github.com/ConsenSys/ERC1400 |
We don't see sufficient interest in this area to justify working on it at the moment. Feel free to show support in this issue so we can reconsider it in the future. |
🎉 Description
Hi everyone,
Currently, we are interested in implementing a security token and know that this is something that interests most people in the space. That's why we thought that the implementation could be done with OpenZeppelin in order to achieve a higher degree of security and reviews.
📝 Details
The ERC1400 proposal seems like a good place to start: ethereum/EIPs#1400
The EIP is not in last call but both definition and development could be done in parallel. Security tokens being a necessity, we will have to create a standard someday anyways.
Implementing a non-standard security token would be a disaster as it won't be interoperable with others and wouldn't be integrated in exchanges, explorers, etc. All those that need to implement a security token are welcome to collaborate on this.
👍 Other Information
[TO BE ADDED]
The text was updated successfully, but these errors were encountered: