Skip to content

Conversation

bgravenorst
Copy link
Contributor

@bgravenorst bgravenorst commented Oct 13, 2025

Description

Add documentation for the eth_config method.

Issue(s) fixed

Fixes #1849

Preview

https://besu-docs-git-fork-bgravenorst-doc-1849-hyperledger.vercel.app/public-networks/reference/api#eth_config

Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Copy link

vercel bot commented Oct 13, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
besu-docs Ready Ready Preview Comment Oct 17, 2025 5:01am

Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
@bgravenorst bgravenorst marked this pull request as ready for review October 13, 2025 04:10
@bgravenorst bgravenorst requested a review from a team as a code owner October 13, 2025 04:10
@macfarla
Copy link
Contributor

@bgravenorst maybe it is worth clarifying that last is the known fork with the largest timestamp

the furthest known fork into the future. futuremost?

idk how best to say it

but "last" is ambiguous. I know that's what they use in the spec.

Otherwise LGTM

Signed-off-by: bgravenorst <byron.gravenorst@consensys.net>
Comment on lines +2529 to +2531
- `next`: _object_ or _null_ - next fork configuration. `null` if no future fork is scheduled.
- `last`: _object_ or _null_ - the furthest configured future fork configuration (the future fork with
the largest `activationTime` among the client’s configured forks). If only one future fork is configured, `next` and `last` are the same object. `null` if no future fork is scheduled.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `next`: _object_ or _null_ - next fork configuration. `null` if no future fork is scheduled.
- `last`: _object_ or _null_ - the furthest configured future fork configuration (the future fork with
the largest `activationTime` among the clients configured forks). If only one future fork is configured, `next` and `last` are the same object. `null` if no future fork is scheduled.
- `next`: _object_ - next fork configuration, or `null` if no future fork is scheduled.
- `last`: _object_ - the furthest configured future fork configuration (the future fork with
the largest `activationTime` among the client's configured forks). If only one future fork is configured, `next` and `last` are the same object. `null` if no future fork is scheduled.

Minor edit for consistency with other method param descriptions

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

Successfully merging this pull request may close these issues.

Document eth_config RPC

3 participants