Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.
This repository was archived by the owner on May 20, 2025. It is now read-only.

Wrong ledgerInclusionState #132

@Thoralf-M

Description

@Thoralf-M

Description

Chronicle returns a wrong ledgerInclusionState for a message id
https://chrysalis-chronicle.iota.org/api/mainnet/transactions/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be

{"data":{"messageId":"12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be","milestoneIndex":6980566,"outputs":[{"output":{"type":0,"address":{"type":0,"address":"eb8bc8b275fbc66500255f06de458ec5b6623b4171b17d8a26a47604860b3885"},"amount":19999500000},"spendingMessageId":null}],"inputs":[{"type":0,"transactionId":"9cc394d188acec61fd76b1ca13554390b02ab00170cad1bc7a6e28a8ede09409","transactionOutputIndex":2}],"ledgerInclusionState":"conflicting"}}

conflicting, but the message with the transaction payload actually got included as seen here
https://chrysalis-nodes.iota.org/api/v1/messages/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be/metadata

{"data":{"messageId":"12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be","parentMessageIds":["0ef7406a90b7ece91252858d070d76d9312c1f6f2520b30045fc09244821a222","ce9a144584fcb0fb25a9fac9f66c50a63bf843a6efd4d28182c3004925c0f97e","d8a3d93596ee50aa508251d564afcec33140479cbdf6f2330d9213cd2ce15216","e23c2f5ceb58283e66929d3405ecef0c9cb49ab0b4f3694a0331e4c47670cb2d"],"isSolid":true,"referencedByMilestoneIndex":6980566,"ledgerInclusionState":"included"}}

The output of the transaction is also available from chronicle and the hornet nodes, which makes it clear that the message really got included
https://chrysalis-chronicle.iota.org/api/mainnet/outputs/fa6ddafc118e66c88be157c88481f9841b156c9b233f9a12e51635d51f210f340000
https://chrysalis-nodes.iota.org/api/v1/outputs/fa6ddafc118e66c88be157c88481f9841b156c9b233f9a12e51635d51f210f340000

The message id for the output returned by chronicle is 9305df5b80e042d30a32f145a8df3bb7d98f1e3307d1e24943f16f7c5420601b, which is a conflicting attachment
From hornet it's 12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be, the actual included message

So somehow in chronicle the conflicting attachment got mixed up with the included one

Also https://chrysalis-chronicle.iota.org/api/mainnet/transactions/9305df5b80e042d30a32f145a8df3bb7d98f1e3307d1e24943f16f7c5420601b returns also the same information as for https://chrysalis-chronicle.iota.org/api/mainnet/transactions/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be

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