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
Description Some RPC API inconsistencies with Geth
admin_peers
>> admin_peers { "clientId": "Geth/v1.11.6-stable-ea9e62ca/linux-arm64/go1.20.3", "host": "13.213.1.104", "port": 41220, "address": "[::ffff:13.213.1.104]:41220", "isBootnode": false, "isTrusted": false, "isStatic": false, "enode": "enode://4201b68cca91c01456cce2e629f812688fde695528f3f423725605ad7a150528edca5c9abe4576adef36ec735764b2611e84df4d4feaa2f4e3fa1c137d9ac37c@13.213.1.104:41220" }
admin_nodeInfo
config
protocols
>> admin_nodeInfo { "enode": "enode://56613efb7a5c93632689426410f8ae2a48842103eea9d91e54fe2263a28a71349874017c11e415fc10ae869927c62e40873051d80b78245cd6edd1046c231f00@13.229.140.233:30303", "id": "ccd2022b4b05ba94081a2993f3773bdf4954425131113d5972bc0acaac3962d7", "ip": "13.229.140.233", "listenAddr": "13.229.140.233:30303", "name": "Nethermind/v1.28.0+9c4816c2/linux-arm64/dotnet8.0.8", "ports": { "discovery": 30303, "listener": 30303 }, "protocols": { "eth": { "difficulty": "0x675", "genesis": "0x32f35e2b2c31e5556e3233d5fab3c5de1bc0ef3199508bb990e3e889a9a88856", "head": "0x5497bf99b5ab661caa3021f6f7d47eda10b479df4c7626790d8ea3858a5f0f3b", "network": "0x539" } } }
Expected behavior Please provide a clear and concise description of what you expected to happen.
Screenshots
The text was updated successfully, but these errors were encountered:
reference here: https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-admin#admin-nodeinfo
Sorry, something went wrong.
obasekiosa
No branches or pull requests
Description
Some RPC API inconsistencies with Geth
admin_peers
: The clientId seems incorrect, it looks more like a client name.admin_nodeInfo
: Missingconfig
inprotocols
Expected behavior
Please provide a clear and concise description of what you expected to happen.
Screenshots
The text was updated successfully, but these errors were encountered: