Custom DA Documentation

[Erol-K]

Team or Project

No response

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.75.0

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

Hi everyone,

I wanted to follow up on the custom DA documentation. February was indicated.

Do you have any estimations on when it will be published? Thanks in advance :)

Expected Behavior

Published Documentation

Current Behavior

No Documentation ;)

Repository Link (if applicable)

No response

Additional Details

Thank you!

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[bxpana]

Appreciate you checking up on this. Seeing what the status is and will get back to you guys.

[bxpana]

@Erol-K to my understanding this is the page with the custom DA documentation: https://docs.zksync.io/zk-stack/running/validium

Is there anything missing from this page that you guys would need for custom da?

[Erol-K]

@bxpana I believe we solved the confusion around custom DA. We wanted to deploy our own DA and were wondering how exactly to do it without re-inventing the wheel. We can adapt an Avail or EigenDA node and its endpoints to our needs. @thecodingshrimp may add more context. Your definition of custom DA is basically developing a DA from scratch and we were looking for the doc for building one. Appreciate your reply!

[bxpana]

To confirm, you guys planning on adapting an Avail or EigenDA nodes and endpoints for you needs?

[thecodingshrimp]

Hey @bxpana, we're still investigating which DA suits our needs best. But it is likely that we will decide on a DA that you guys support natively and is integrated well in your framework. Note: we will use a private version of these DA solutions.
In the unlikely case that we want to implement our custom DA, the only two functions that we would need to implement are dispatch_blob and get_inclusion_data from the DataAvailabilityClient, am I right?

[Erol-K]

@bxpana To confirm, you guys planning on adapting an Avail or EigenDA nodes and endpoints for you needs?

Correct, our private Avail/EigenDa node that communicates with our private zkstack. Do we have to consider something specific if we continue with this path? Thanks!

[perekopskiy]

Hi @Erol-K, nothing specific, just keep in mind that using private stack means DA layer should be private and node's API should be private/require auth process. Please check "How can I enable private" at the bottom of https://docs.zksync.io/zk-stack/running/validium, it should be useful

[Erol-K]

Hi @perekopskiy thanks for your feedback, appreciated it! I think we got all our answers for now.