feat: Herodotus Data Commitment Facts #120
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contains the initial work to have BlobstreamX Starknet use
state_dataCommitments
from BlobstreamX L1. This is done by using Herodotus Storage Proofs to relay all missingstate_dataCommitments
from L1.The PR contains :
Scripts :
request-data-commitments.sh
: This makes a request to the Herodotus API for all DC yet to be included on Starknet.wait-for-herodotus-fulfill.sh
: Helper script used to monitor Starknet Herodotus Fact registry until expected value relay is done.Src :
update_data_commitments_from_facts(l1_block)
: New BlobstreamX entry point which tries to fetch and update the lateststate_proof_nonce
andstate_data_commitments
from the Herodotus Fact Registry. ( includes tests )EVMFactRegistryMock
: Mock of the necessary storage/functions from the Herodotus EVM Fact Registry Contract.Expected BlobstreamX update control flow :
request-data-commitments.sh
->update_data_commitments_from_facts(l1_block)