-
Notifications
You must be signed in to change notification settings - Fork 15
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
Comments
It looks like the following message ids are also affected:
|
And here are some message ids where it seems to be the other way around (Chronicle returns |
Wrong repo? |
@Alexandcoats this issue is for mainnet/Chrysalis, inx-chronicle is only for Stardust, no? |
Description
Chronicle returns a wrong ledgerInclusionState for a message id
https://chrysalis-chronicle.iota.org/api/mainnet/transactions/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be
conflicting
, but the message with the transaction payload actually gotincluded
as seen herehttps://chrysalis-nodes.iota.org/api/v1/messages/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be/metadata
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 attachmentFrom hornet it's
12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be
, the actual included messageSo 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
The text was updated successfully, but these errors were encountered: