Skip to content

Commit

Permalink
Merge pull request #394 from alchemyplatform/eth_getLogs_fix
Browse files Browse the repository at this point in the history
fix params for eth_getLogs
  • Loading branch information
SahilAujla authored Jun 4, 2024
2 parents b00d83d + 428eee5 commit 08024dd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion evm_body.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1827,7 +1827,7 @@ blockNumber_or_blocktag_param_eth:
String - Either the hex value of a **block number** OR **block tags**:
1. **block number** (in hex) OR
2. **block tag** (one of the following):
* `pending` - A sample next block built by the client on top of latest and containing the set of transactions usually taken from local mempool. Intuitively, you can think of these as blocks that have not been mined yet.
* `pending` (Not available on Ethereum) - A sample next block built by the client on top of latest and containing the set of transactions usually taken from local mempool. Intuitively, you can think of these as blocks that have not been mined yet.
* `latest` - The most recent block in the canonical chain observed by the client, this block may be re-orged out of the canonical chain even under healthy/normal conditions.
* `safe` - The most recent crypto-economically secure block, cannot be re-orged outside of manual intervention driven by community coordination. Intuitively, this block is “unlikely” to be re-orged.
* `finalized` - The most recent crypto-economically secure block, that has been accepted by >2/3 of validators. Cannot be re-orged outside of manual intervention driven by community coordination. Intuitively, this block is very unlikely to be re-orged.
Expand Down

0 comments on commit 08024dd

Please sign in to comment.