Search

Search for projects by name or address

Ecosystems
Ecosystem logo
Built on the ZK Stack badgePart of the Elastic Chain badge

TVS
Activity

TVS by token type

TVS breakdown by token type

ETH & derivatives
34.2%
Stablecoins
14.8%
BTC & derivatives
0.50%
Other
50.4%

TVS by stage

TVS breakdown by stage

Total 7 projects

Stage 0
100% (7)
Stage 1
0.00% (0)
Stage 2
0.00% (0)

DA Layers used

Ethereum3 projects
Avail2 projects
None2 projects

Blobs posted

40.63 MiB


0.86% of total blob size

Live projects count

2023 Mar 24 — 2026 Sep 25

7 Projects
6.93% scaling market share

Projects with TVS > $100M1 projects
Projects with avg UOPS > 11 projects

Ecosystem Token

ZKsync

ZKsync

ZK

The ZK token is a governance token that allows token holders to introduce and vote on protocol upgrades within the Elastic Network.


Price

$0.0139.4%

Market Cap

$139.06 M45.3%

Circulating Supply

10.81 B ZK4.30%

Milestones & Incidents

2023202420252026

2026 Jun 25 • Sophon

Sophon initiates L2 sunset

Sophon announces sunsetting the L2 and stops new deposits.

32 of 32
Learn more

Ecosystem Updates

Explore the latest Ecosystem Updates


#
name
Risks
Proof system
stage
Total value secured
7D%
Past day UOPS
7D%
1
ZKsync Era logo
Risk analysis
Sequencer Failure
Enqueue via L1
State Validation
Validity proofs (ST, SN)
Data Availability
Onchain (SD)
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
Stage 0
Full training wheels

Items missing for Stage 1
  • Compromising ≥75% of the Security Council should be the only way (other than bugs) for a rollup to indefinitely block an L2→L1 message (e.g. a withdrawal) or push an invalid L2→L1 message (e.g. an invalid withdrawal) with a <7d exit window.

    While the Security Council is properly set up and is able to recover from a misbehaving operator, the majority is required, meaning that a compromised quorum-blocking minority can prevent users from exiting. Recovery actions are not straightforward and require complex protocol upgrades.

Please mind, stages do not reflect project security
$274.23 M13.7%
4.46% with additional trust assumptions
0.1840.7%
2
Abstract logo
Risk analysis
Sequencer Failure
Enqueue via L1
State Validation
Validity proofs (ST, SN)
Data Availability
Onchain (SD)
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
Stage 0
Full training wheels

Items missing for Stage 1
  • Compromising ≥75% of the Security Council should be the only way (other than bugs) for a rollup to indefinitely block an L2→L1 message (e.g. a withdrawal) or push an invalid L2→L1 message (e.g. an invalid withdrawal) with a <7d exit window.

    While the Security Council is properly set up and is able to recover from a misbehaving operator, the majority is required, meaning that a compromised quorum-blocking minority can prevent users from exiting. Recovery actions are not straightforward and require complex protocol upgrades.

Please mind, stages do not reflect project security
$57.51 M15.2%
55.8% with additional trust assumptions
3.071.99%
3
Cronos zkEVM logo
Risk analysis
Sequencer Failure
Enqueue via L1
State Validation
Validity proofs (ST, SN)
Data Availability
External
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
n/a
$29.54 M10.6%
11.8% with additional trust assumptions
<0.012.57%
4
ADI Chain logo
Risk analysis
Sequencer Failure
Enqueue via L1
State Validation
Validity proofs (ST, SN)
Data Availability
Onchain (SD)
Exit Window
Emergency: None
Regular: 3d
Proposer Failure
Cannot withdraw
ValidityThis project is based on ZK Stack's code base.
Airbender
Stage 0
Full training wheels

The requirement for available node software is under review
Items missing for Stage 1
  • Compromising ≥75% of the Security Council should be the only way (other than bugs) for a rollup to indefinitely block an L2→L1 message (e.g. a withdrawal) or push an invalid L2→L1 message (e.g. an invalid withdrawal) with a <7d exit window.
Please mind, stages do not reflect project security
$11.61 M5.71%
47.8% with additional trust assumptions
0.1517.2%
5
Sophon logo
Risk analysis
Sequencer Failure
No mechanism
State Validation
Validity proofs (ST, SN)
Data Availability
External
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
Stage 0
Full training wheels

Items missing for Stage 1
  • Compromising ≥75% of the Security Council to push a malicious upgrade, or sequencer+DA-committee collusion to withhold data and finalize invalid state roots, should be the only ways (other than bugs) to steal funds or block withdrawals indefinitely.
Please mind, stages do not reflect project security
$6.00 M11.7%
0.00% with additional trust assumptions
<0.0113.5%
6
Lens logo
Risk analysis
Sequencer Failure
Enqueue via L1
State Validation
Validity proofs (ST, SN)
Data Availability
External
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
Stage 0
Full training wheels

Items missing for Stage 1
  • Compromising ≥75% of the Security Council to push a malicious upgrade, or sequencer+DA-committee collusion to withhold data and finalize invalid state roots, should be the only ways (other than bugs) to steal funds or block withdrawals indefinitely.
Please mind, stages do not reflect project security
$924 K1.86%
0.00% with additional trust assumptions
0.047.01%
7
GRVT logo
Risk analysis
Sequencer Failure
No mechanism
State Validation
Validity proofs (ST, SN)
Data Availability
External
Exit Window
Emergency: None
Regular: 4d 3h
Proposer Failure
Replace proposer
ValidityThis project is based on ZK Stack's code base.
Boojum
n/a
No data