Skip to content

Commit

Permalink
Add exceptions subsection
Browse files Browse the repository at this point in the history
  • Loading branch information
qdm12 committed Jan 14, 2025
1 parent 813df77 commit 2101c6e
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions content/docs/api-reference/c-chain/api.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ services:
- `txpool_`
- `debug_` (note: this is turned off on the public API node.)

You can interact with these services the same exact way you'd interact with Geth. See the
You can interact with these services the same exact way you'd interact with Geth (see exceptions below). See the
[Ethereum Wiki's JSON-RPC Documentation](https://ethereum.org/en/developers/docs/apis/json-rpc/)
and [Geth's JSON-RPC Documentation](https://geth.ethereum.org/docs/rpc/server)
for a full description of this API.
Expand All @@ -81,10 +81,12 @@ For batched requests on the [public API node](/tooling/rpc-providers) , the maxi
number of items is 40. We are working on to support a larger batch size.
</Callout>

Note the `eth_getProof` is acting differently from release v0.14.1:
#### Exceptions

- On archive nodes (`"pruning-enabled": false`): queries for historical proofs for state older than approximately 24 hours preceding the last accepted block will be rejected by default. This can be adjusted with the new option `historical-proof-query-window` which defines the number of blocks before the last accepted block which should be accepted for state proof queries, or set to `0` to accept any block number state query.
- On `pruning` nodes: queries for proofs past the tip buffer (32 blocks) will be rejected
- `eth_getProof` behaves differently than geth, from release v0.14.1, with the following differences:
- On archive nodes (`"pruning-enabled": false`), queries for proofs for state older than approximately 24 hours preceeding the last accepted block will be rejected by default.
This can be adjusted with the option `historical-proof-query-window` which defines the number of blocks before the last accepted block which should be accepted for state proof queries, or set it to `0` to accept any block number state query.
- On pruning nodes (`"pruning-enabled": true`), queries for proofs past the tip buffer of 32 blocks are always rejected


### Avalanche - Ethereum APIs
Expand Down

0 comments on commit 2101c6e

Please sign in to comment.