8000 Transactions are stuck in mempool if unconfirmed output is reused in another transaction. · Issue #1790 · jl777/komodo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Transactions are stuck in mempool if unconfirmed output is reused in another transaction. #1790
Open
@artemii235

Description

@artemii235

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

  1. Send the transaction.
  2. Reuse it's unconfirmed output in another transaction.

Expected behaviour

All transactions mined.

Actual behaviour + errors

All transactions get stuck in some nodes mempool. E.g. these are visible in explorer, but not present on electrum servers, etc. The mempool is not synced between nodes.

The version of Komodo you were using:

Not sure about it, last error reported for OOT chain: https://discordapp.com/channels/412898016371015680/449950331577565194/661586034643042315
The transactions:
https://explorer.utrum.io/tx/d140693bc9c106ecfa28dd2d1cb3d5890371ee0dedd08f667f259faf9d8bf9b3
https://explorer.utrum.io/tx/bed8b7a4e6b42c1cdfdf689f8d279467eb266098dea7f585352b8b5349a3ea51
https://explorer.utrum.io/tx/90c9d04f6209825e2d42973e894d976cae0936514fd44cedd37fefac2359a449
were stuck unconfirmed until I explicitly rebroadcasted them using electrum server that didn't have them in mempool.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0