We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Maybe we could make this even more performant for users by introducing client-side generated proofs.
This is a blockchain most useful for data-heavy stuff. if you can get the stark proofs down to 0.01ms, you can do a lot more
If you control all of your storage leaves, then you can generate the proof yourself and include it in the sequencer submission.
Then optimistically assume that the leaves are the right ones, else pay a sequencing cost.
This has the benefit of naturally decentralizing the execution layer, since everything can be done client-side.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Maybe we could make this even more performant for users by introducing client-side generated proofs.
This is a blockchain most useful for data-heavy stuff. if you can get the stark proofs down to 0.01ms, you can do a lot more
If you control all of your storage leaves, then you can generate the proof yourself and include it in the sequencer submission.
Then optimistically assume that the leaves are the right ones, else pay a sequencing cost.
This has the benefit of naturally decentralizing the execution layer, since everything can be done client-side.
The text was updated successfully, but these errors were encountered: