Skip to content

Receiving transactions on txpool after the transactions has been confirmed #951

@soltrac

Description

@soltrac

Describe the bug
I don't know if this is intended or not, but my node receives in txpool all transactions after they have been confirmed. Maybe is a problem that I'm not connected to enough peers, how can I increase the maximum amount of peers to connect?

To Reproduce
Fire a transaction, read the txpool. I receive the block where the transaction is validated before receiving the txhash of the transaction on the mempool.

Expected behavior
I should receive the transaction on the txpool before the block. If not always, at least, most of times. The difference sometimes is about 5 seconds

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions