-
Module Affected
Rust Version1.75.0 Operating System
Issue DescriptionWe are currently using ZK Stack to enable builders to spin up their ZK Rollups on Bitcoin via an intermediate EVM-compatible Layer 1 called BVM (https://bvm.network/). In the original ZK Stack flow, a batch of transactions is directly stored on Layer 1 in blobs. However, in BVM, we would like to store the batch in alternative Data Availability (DA) storages such as Celestia, Polygon, etc. We've made the following changes to the ZK Stack's source code to achieve this:
Our question is whether there are any security concerns with the changes we made, as described above, and if so, please advise us on how to address them. Thanks in advance. Expected BehaviorThere is a way to change Data Availability layer for storing batches of transactions instead of storing them directly on Layer 1 Current BehaviorThe batches of transactions are directly stored in Layer 1 Repository Link (if applicable)https://github.com/TrustlessComputer/zk-rollups Additional DetailsNo response Prior Research
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thanks for the post, we'll get back asap |
Beta Was this translation helpful? Give feedback.
We are currently working on having other DA options available for ZK Stack, but it's not quite available yet.
Regarding any security concerns, it would be best to get an audit to make sure that there would be no issues with the changes that you made.