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

Transactions of the block number in the artifact are never certified by the prover #1762

Closed
2 tasks done
jpraynaud opened this issue Jun 18, 2024 · 0 comments · Fixed by #1779
Closed
2 tasks done
Assignees
Labels
bug ⚠️ Something isn't working

Comments

@jpraynaud
Copy link
Member

jpraynaud commented Jun 18, 2024

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

  • Investigate the problem
  • Fix the problem
@jpraynaud jpraynaud added the bug ⚠️ Something isn't working label Jun 18, 2024
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>
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
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
Labels
bug ⚠️ Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants