ADI

ADI is a Layer 2 token built on zkStack, the framework behind zkSync. Building on established rollup infrastructure means inheriting a well-examined base, and it says nothing about the application or token deployed on top of it.

Validity proofs are a strong settlement property

A zk rollup proves mathematically that its state transitions were computed correctly, rather than assuming validity and allowing challenges. That removes the multi-day withdrawal delay optimistic rollups require, because correctness is proven rather than presumed.

Shared frameworks lower the cost of launching a chain

Deploying on an established rollup framework means inheriting audited proving systems and tooling rather than building them. That is a genuine engineering advantage and it makes launching a chain accessible enough that the framework's quality no longer implies the deployment's.

Base layer security is not application security

Whatever the rollup guarantees about state transitions, funds sit in application contracts. Their audit status, upgradeability and administrative keys are separate questions entirely, and they are where deposits are actually at risk.

What to verify on any Layer 2 token

Who operates the sequencer, whether users can force transaction inclusion if it censors, whether the bridge contract has published audits, and how the token supply is allocated and vested. These determine the practical risk rather than the proving system.

Who it suits

Users active on this specific network who have verified the sequencer, bridge and audit position. The underlying framework's quality does not transfer automatically to what is built with it.