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

Ethereum Erigon - Add Caplin as an option for consensus layer client #129

Open
frbrkoala opened this issue Sep 23, 2024 · 4 comments
Open

Comments

@frbrkoala
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Erigon has a built-in consensus client called Caplin. It is recommended by the Erigon team to use it for the nodes setup.

Describe the solution you would like

Link to the documentation: https://erigon.gitbook.io/erigon/advanced-usage/consensus-layer

Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 24, 2024
Copy link
Contributor

github-actions bot commented Nov 3, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2024
@frbrkoala frbrkoala reopened this Dec 19, 2024
@github-actions github-actions bot removed the stale label Dec 20, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jan 19, 2025
Copy link
Contributor

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
@frbrkoala frbrkoala reopened this Jan 31, 2025
@github-actions github-actions bot removed the stale label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant