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

How is data availability proven? #156

Open
TimTinkers opened this issue Oct 10, 2024 · 2 comments
Open

How is data availability proven? #156

TimTinkers opened this issue Oct 10, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@TimTinkers
Copy link

Hello, I've read the documentation and in this diagram I feel I understand everything except the data availability.

image

The OP Stack is running, presumably its op-batcher is still happily filling up blobs, and op-succinct is generating validity proofs for confirmation on L1. But how is the data from those blobs confirmed as part of the proof? I'm missing the link that takes this from validium to rollup.

Thank you!

@Thegaram
Copy link

I just came here to ask this question when I saw your issue.

From the values passed to the verifier, the only one that can capture DA is _l1BlockHash.

My guess is that BlobProvider verifies that the raw data matches the blob hash, then ChainProvider verifies that the blob hashes belong to a certain L1 block hash, then we verify that these blocks chain up to _l1BlockHash.

It seems that all data needed for proving is passed here, and verified here using InMemoryOracle.

@ratankaliani
Copy link
Member

That's correct @Thegaram! In the future, when Optimism moves to using nonces for the SystemConfig and DepositTransaction's, this derivation will become easier to prove.

@ratankaliani ratankaliani added the documentation Improvements or additions to documentation label Oct 10, 2024
@ratankaliani ratankaliani self-assigned this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants