Skip to content

Inconsistent Behavior When Querying Unconfirmed Transaction Inputs #2230

@mgpai22

Description

@mgpai22

I encountered unexpected behavior while querying inputs of chained unconfirmed transactions in the mempool.

Scenario:

  • Unconfirmed Tx1:

    • Inputs: [A, B]
    • Outputs: [C, D]
  • Unconfirmed Tx2:

    • Inputs: [C, D]
    • Outputs: [E, F]

Both transactions are chained within the mempool.

Observed Behavior:

  • Inputs A, B:

    • Query successful via endpoints:

    • /utxo/byId

    • /blockchain/box/byId

    • /transactions/unconfirmed/inputs/byBoxId

  • Inputs C, D (unconfirmed):

    • Query fails via endpoint:

      • /transactions/unconfirmed/inputs/byBoxId (unexpected)
    • Query correctly fails via endpoints:

      • /utxo/byId
      • /blockchain/box/byId
    • Query succeeds via endpoints:

      • /utxo/withPool/byId
      • /transactions/unconfirmed/outputs/byBoxId

Expected Behavior:

Chained unconfirmed inputs (C, D) should be retrievable via /transactions/unconfirmed/inputs/byBoxId.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions