Skip to content

Check functionality for RPC methods depending on the pending tag #1112

Open
@rodrigo-o

Description

@rodrigo-o

Right now the block number resolver which may receive a tag works returning always the latest block, BUT every RPC call will probably need to have different logic for pending. For example, eth_getTransactionCount instead of getting the nonce for the tie it gets it from the mempool first and just defaulting to the latest block later (which was needed for #1092). As far as i know that's the only RPC method which is handling pendings as expected for now, we need to check how about the others.

This might become an umbrella task if every one of those methods proves to be complex in itself.

Metadata

Metadata

Assignees

No one assigned

    Labels

    rpc-apiPublic rpc-json api for users

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions