You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
The beacon node needs to verify the credentials.
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?
🛠️ 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
The text was updated successfully, but these errors were encountered:
🎯 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):
The beacon node needs to verify the credentials.
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?
🛠️ Proposed solution
I hope that the original way of using beacon-api is compatible with the new version.
🧪 Tests
The text was updated successfully, but these errors were encountered: