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

Beacon node is unavailable due to go-eth2-client Package #3224

Open
5 tasks
xiaowangba2dai opened this issue Aug 9, 2024 · 0 comments
Open
5 tasks

Beacon node is unavailable due to go-eth2-client Package #3224

xiaowangba2dai opened this issue Aug 9, 2024 · 0 comments
Labels
protocol Protocol Team tickets

Comments

@xiaowangba2dai
Copy link

🎯 Problem to be solved

Hi, when I upgraded charon to the latest v1.0.1 version, I found that the beacon api returned 401.
My beacon-api-endpoint configuration is shown in the following figure (https://ip:port/credential):

image

The beacon node needs to verify the credentials.
image

After some analysis, I found that the new version of github.com/attestantio/go-eth2-client will replace the credential with *** , resulting in beacon-api-endpoint can not be used, do you have any solution?

image

🛠️ Proposed solution

  • Approved design doc: link
  • Core team consensus on the proposed solution

I hope that the original way of using beacon-api is compatible with the new version.

🧪 Tests

  • Tested by new automated unit/integration/smoke tests
  • Manually tested on core team/canary/test clusters
  • Manually tested on local compose simnet
@github-actions github-actions bot added the protocol Protocol Team tickets label Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol Protocol Team tickets
Projects
None yet
Development

No branches or pull requests

1 participant