We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/eth/v1/config/deposit_contract
Prysm nodes currently return the chain_id field in /eth/v1/config/deposit_contract as numeric value:
chain_id
{ "data": { "chain_id": 7011893058, "address": "0x6f22fFbC56eFF051aECF839396DD1eD9aD6BBA9D" } }
According to the specs this should be a string ("7011893058").
"7011893058"
Some downstream libraries (eg. attestantio/go-eth2-client) don't like that and fail on initialization because of that.
probably there since ~2 weeks, the relevant code has been touched in #12872
call /eth/v1/config/deposit_contract api and check result
No response
The text was updated successfully, but these errors were encountered:
Thank you for bringing this to our attention
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Prysm nodes currently return the
chain_id
field in /eth/v1/config/deposit_contract as numeric value:According to the specs this should be a string (
"7011893058"
).Some downstream libraries (eg. attestantio/go-eth2-client) don't like that and fail on initialization because of that.
Has this worked before in a previous version?
probably there since ~2 weeks, the relevant code has been touched in #12872
🔬 Minimal Reproduction
call
/eth/v1/config/deposit_contract
api and check resultError
No response
Platform(s)
No response
What version of Prysm are you running? (Which release)
No response
Anything else relevant (validator index / public key)?
No response
The text was updated successfully, but these errors were encountered: