[docs-agent] Fix invalid hex character in eth_getProof storage key example (DOCS-102)

[alchemy-bot]

Summary

The shared eth_getProof example in src/openrpc/chains/_components/custom/methods.yaml has a 32-byte storage key with a literal s character (0x283s34c8e2b1...). s is not a valid hex digit, so every EVM chain that inherits this example returns hex string invalid on Try It.

Replacing the s with 5 gives a syntactically valid 32-byte hex string. The corrected value (0x283534c8e2b1...) was live-verified to return HTTP 200 with a real eth_getProof result on eth-mainnet.g.alchemy.com/v2/docs-demo.

$ curl -X POST 'https://eth-mainnet.g.alchemy.com/v2/docs-demo' \
    -H 'Content-Type: application/json' \
    -H 'Origin: https://www.alchemy.com' \
    -H 'Referer: https://www.alchemy.com/' \
    -d '{"jsonrpc":"2.0","id":1,"method":"eth_getProof","params":[
        "0xe5cB067E90D5Cd1F8052B83562Ae670bA4A211a8",
        ["0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421",
         "0x283534c8e2b1456f09832c71e5d6a0b4f8c9e1d3a2b5c7f0e6d4a8b2c1f3e5d7"],
        "latest"]}'

{"jsonrpc":"2.0","id":1,"result":{"accountProof":[...],"address":"0xe5cb...","balance":"0x...","codeHash":"0x...","nonce":"0x...","storageHash":"0x...","storageProof":[...]}}

Impact

DOCS-101 audit caught this affecting ~29 EVM chains (every chain spec that $ref's the shared eth_getProof example). One-line fix in the shared YAML, no per-chain changes needed.

Linear

DOCS-102 — Fix invalid hex character in shared eth_getProof storage key example

Surfaced by DOCS-101 audit (PR #1340).

Requested by

@SahilAujla (via Slack thread)

[github-actions]

🔗 Preview Mode

Name	Status	Preview	Updated (UTC)
Alchemy Docs	✅ Ready	🔗 Visit Preview	May 29, 2026, 5:40 PM

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 72abe3776a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[SahilAujla]

@codex review