-
Notifications
You must be signed in to change notification settings - Fork 41
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
Transactions of the block number in the artifact are never certified by the prover #1762
Closed
2 tasks done
Labels
bug ⚠️
Something isn't working
Comments
Alenar
added a commit
that referenced
this issue
Jun 25, 2024
This is due to the request to retrieve the precomputed block range roots in database using a exclusive bound comparaison instead of an inclusive, leading to the exclusion of the last block range root from the retrieved data. This means that not only the prover was impacted but the protocol message generation for the single & multi signatures too. Co-authored-by: Sébastien Fauvel <sfauvel@users.noreply.github.com>
9 tasks
Alenar
added a commit
that referenced
this issue
Jun 26, 2024
This is due to the request to retrieve the precomputed block range roots in database using a exclusive bound comparaison instead of an inclusive, leading to the exclusion of the last block range root from the retrieved data. This means that not only the prover was impacted but the protocol message generation for the single & multi signatures too. Co-authored-by: Sébastien Fauvel <sfauvel@users.noreply.github.com>
Alenar
added a commit
that referenced
this issue
Jun 26, 2024
This is due to the request to retrieve the precomputed block range roots in database using a exclusive bound comparaison instead of an inclusive, leading to the exclusion of the last block range root from the retrieved data. This means that not only the prover was impacted but the protocol message generation for the single & multi signatures too. Co-authored-by: Sébastien Fauvel <sfauvel@users.noreply.github.com>
Alenar
added a commit
that referenced
this issue
Jun 26, 2024
This is due to the request to retrieve the precomputed block range roots in database using a exclusive bound comparaison instead of an inclusive, leading to the exclusion of the last block range root from the retrieved data. This means that not only the prover was impacted but the protocol message generation for the single & multi signatures too. Co-authored-by: Sébastien Fauvel <sfauvel@users.noreply.github.com>
Alenar
added a commit
that referenced
this issue
Jun 26, 2024
…ficate_block_number_is_not_certified Fix #1762: CardanoTransactionSnapshot block number is not certified
2 tasks
12 tasks
locallycompact
pushed a commit
to cardano-scaling/mithril
that referenced
this issue
Sep 27, 2024
…not certified This is due to the request to retrieve the precomputed block range roots in database using a exclusive bound comparaison instead of an inclusive, leading to the exclusion of the last block range root from the retrieved data. This means that not only the prover was impacted but the protocol message generation for the single & multi signatures too. Co-authored-by: Sébastien Fauvel <sfauvel@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why
The transactions included in the block number referenced in the artifact (as the last block number signed) are never certified by the prover. Some early investigations have shown that it only the transactions from the penultimate block range are certified.
What
Investigate and fix the problem that prevents some transactions to be certified when they are signed.
How
The text was updated successfully, but these errors were encountered: