Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong ledgerInclusionState #132

Open
Thoralf-M opened this issue Sep 3, 2023 · 4 comments
Open

Wrong ledgerInclusionState #132

Thoralf-M opened this issue Sep 3, 2023 · 4 comments

Comments

@Thoralf-M
Copy link
Member

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

@cleverground
Copy link

cleverground commented Sep 3, 2023

It looks like the following message ids are also affected:

2a3d18e3fbca480e45cf66b8c665465b91af101b0eae02ec7856340ac2640b81 1942e5f29a82f5db09b66dd1d9179fea758380c33ba3c150def32e2787565a51 7f10d8019695763de74eb24e65c0c91102291cda84f6e4144e82d6fbf56a0d59 9ce2376ab446913f32b8319e3750c60280b6a1b5753d20a9e3c54e84269c8004 02a95b9ce7b9e684bf8cb2c20a5fb7397dab38e4dc7cf3e770c7a4d48d4b523f 6709bc581b04f10fbd70abcf1dc54d3c42f1f00c70ba22e3e3ee5d1585c34601 3def27d2b9b31534212186a7bdc3fc3ee11711599dab4ee526820d2e190b421b 244ec4baa30bce169af78f1a3698227a41a71f13d5030aa5fc5542af66683d82 2ccb726c43a2aa419cab65082a64cba2fbbbf4a83f390a33c24f85c712dece7c cba9cb378c605d875b6ed5ae9eaece62f53f27bd7dc189b5204ddb9bb18e58b7

@cleverground
Copy link

And here are some message ids where it seems to be the other way around (Chronicle returns included instead of conflicting):
836a027bd28917f4336145d221f438e848d12cb388ef745e4915cbacfb325161 18232aa32252da22290be33cc0f114b5b6b4317776f648526e5f5641278f8f18 07f2352b4ca32bf5fe30af3fb731669242b2f32dac0e297e6763e4ac7a3b578e 998a5b4148227f1c763e57fe63d7cd35f268ffa28b44fb477b33cc79f438eca6 00d285311fd09ab578642257175fce6d953355317fdd17e063f04eb26d484125 00866f5211e1e734149a79c90e89a93ae2e8b34e04e71561fb737c583474b2f5 93c5e51ce6dd96774029f308824c3067557f94bfcd15f5df7fd6d2aa64eae2c6 3142c9ec613cede4c8a558fcd63330077a4230ac11df297417dd12f870cd6c11 2f3e9b8cdc0a1b73920b91a4f7d1074b86f670b5937e30ff4d08a0a1259a78a1 2f3a2f003212af486e1b2ec295bae1b0a67351d77040309da3365538c9caef55 24b121af6c1141c1fcf11f7e25aa89af9225996ea0c1e37e1b0d3517a3364b87 2be6348d6a6329e5853f754c108a4107c192e21d9e4f89b7cf46a7e0cf9e5ab7 18c59abfaf758759e59be10228627df349f0b4c201891eabc69bac6fe29f4eca 9dc010fd1ae95fb4b1f0cfa12401868f60ceede269938675b659aca60b338119 a1b879b47b72cd5b7b406c5430b1a6e524caf618a6b2c90231c7b98bf2fe1b30

@DaughterOfMars
Copy link

Wrong repo?

@Thoralf-M
Copy link
Member Author

@Alexandcoats this issue is for mainnet/Chrysalis, inx-chronicle is only for Stardust, no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants