🟦About L2 Rollup

Q:What are the advantages to using ZK-rollup among competitors?

Zk-rollup is our design for phase 2.

In phase 1 of our design, we have implemented GlacierDB using SCP, similar to other database solutions (such as WeaveDB/KwilDB) over Arweave. SCP provides a simple and rapid method for prototyping a working database.

To further enhance the security and decentralization of GlacierDB, we have decided to leverage Zk-Rollup technology to anchor the security and decentralization of the Layer 1 chain. For example, if the Block Producer generates an invalid Block Proof, they will be unable to submit the Block Data to the Layer 1 contract, and the tokens that they have staked in the contract may be slashed.

To be more specific:

1. AR and other decentralized storage data is queried and presented in the DB Engine in the form of Table.

2. Rollup will generate two elements from the data (Block) by the DB Engine, which is block-proof and block-data.

  • Block-Proof is written to the L1 Settlement Layer (such as ETH), and Block-Data is stored permanently in AR and more decentralized storage.

  • If the Block-Data or Block-Proof is incorrect, it will be rejected when written into the L1 contracts, or a fraud-proof will be executed through the L1 contract to prove that this Block-Proof is incorrect afterwards.

ZK-Rollup is equivalent to taking advantage of L1 contracts for decentralization purposes. Meanwhile, the implementation of external DA at the same time can offload the limitation of data capacity to the outside of L1. This is also a brand new structure differentiating with other DB solutions.

Q:In terms of Zk-Rollup, what proof are you conducting?

GlacierDB uses STARK based proofs.

Q:Where are ZK-proofs conducted within the Glacier stack?

When the DB Engine generates a data block, it also generates ZK-proofs based on the data block. The entire state of the GlacierDB engine is composed of Merkel Trees generated by rows, collections, and namespaces. These proofs verify the validity of each transaction and its effect on the database state.

Q: What is your process for adding new chain support?

  1. Deploy and configure the L1 settlement contract on the new blockchain to handle Data Proof write-ins.

  2. Configure the schema of a new collection to specify which blockchain should be used for the data proof of that collection.

Last updated