Skip to content

Client inconsistency: maximum size of a single network transaction message #32724

@1033309821

Description

@1033309821

Hi, We repeatedly filled a single transaction message with identical transactions until reaching its maximum capacity, and then sent it to different clients. Results showed that only Geth successfully processed this message, and we were able to locate these transactions in its MemPool. The other four clients directly rejected the data packet at the network layer, preventing the included transactions from entering their MemPools.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions