Fix: Document blockAccessListHash in block results

[alexandratran]

What should be changed?

Update the block result docs for the behavior merged in besu-eth/besu#10373.

Besu changed the JSON key returned by eth_getBlockByNumber and eth_getBlockByHash for the EIP-7928 block access list hash from balHash to blockAccessListHash, matching geth's types.Header field naming. The PR notes that the old key caused tooling such as spamoor to read BlockAccessListHash as nil, which affected Amsterdam activation detection and EIP-8037 gas calculations.

Suggested docs updates:

• Update docs/public-networks/reference/api/objects.md#block-object to document the blockAccessListHash field on the block object.
• Verify the field type and fork availability against the Besu implementation before publishing, but the PR describes it as the EIP-7928 block access list hash.
• Update any eth_getBlockByHash and eth_getBlockByNumber response examples in docs/public-networks/reference/api/index.md if they should show Amsterdam block result fields.
• Do not document balHash as the public JSON-RPC key.

Docs page

• https://besu.hyperledger.org/public-networks/reference/api/objects#block-object
• https://besu.hyperledger.org/public-networks/reference/api/#eth_getblockbyhash
• https://besu.hyperledger.org/public-networks/reference/api/#eth_getblockbynumber

Issue type

• Outdated content
• Missing content

Source links

• fix: rename balHash JSON key to blockAccessListHash in block results besu#10373
• JSON-RPC: block header uses 'balHash' instead of 'blockAccessListHash' (EIP-7928) besu#10359