You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a transaction is included in a block, the consensus node notifies you of its commitment with a string value but does not provide a proof. In the future, we aim to verify all write paths using transaction commitments, ensuring that all shares are correctly included within the block. This issue could potentially become a larger effort, as it requires coordination with the Celestia node. Here, we want to focus on defining the criteria and detailing the work required to integrate proofs into the consensus client.
Acceptance Criteria
Speak to the node team and understand the requirements from their side
Make an initial/plan design and present to the core/app team
Take care of all follow-up tickets/project management so that tickets are workable right after
The text was updated successfully, but these errors were encountered:
Description
Currently, when a transaction is included in a block, the consensus node notifies you of its commitment with a string value but does not provide a proof. In the future, we aim to verify all write paths using transaction commitments, ensuring that all shares are correctly included within the block. This issue could potentially become a larger effort, as it requires coordination with the Celestia node. Here, we want to focus on defining the criteria and detailing the work required to integrate proofs into the consensus client.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: