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

Language relating to Trinity and Open Ethereum clients is not accurate #3358

Closed
tvanepps opened this issue Jun 28, 2021 · 1 comment · Fixed by #3357
Closed

Language relating to Trinity and Open Ethereum clients is not accurate #3358

tvanepps opened this issue Jun 28, 2021 · 1 comment · Fixed by #3357
Labels
bug 🐛 Something isn't working

Comments

@tvanepps
Copy link
Contributor

tvanepps commented Jun 28, 2021

A twitter user recently tried to sync the Trinity client, which failed.

Many in the Ethereum community are aware that Trinity is not a mainnet client, but this is not called out on the Nodes and Clients page of the website. There is also a flag above the table which says "All of them are actively worked on."

It might make sense to separate out clients that are 1. continuously maintained 2. are not going to be deprecated.

Related to #2, consider mentioning that OE will be deprecated after London and that users should look into migrating to other clients.

@tvanepps tvanepps added the bug 🐛 Something isn't working label Jun 28, 2021
@pipermerriam
Copy link
Member

Trinity will no longer be developed or maintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants