l2beat / l2beat

L2BEAT is an analytics and research website about Ethereum layer two (L2) scaling solutions.

L2BEAT 💓

L2BEAT (Layer 2 Beat) is a website dedicated to providing research and statistics about the very exciting layer 2 technology on Ethereum.

You can visit the site yourself at https://www.l2beat.com/.

Contributing

We welcome and encourage contributions. To learn about the project structure and contributions please read CONTRIBUTING.md.

🔍 Here is also a visual step-by-step guide for creating a Pull Request - link

License

We believe in knowledge sharing and open access. Our code is and will remain open source with the permissive MIT license.

Versioning and publishing (tooling)

Some of the sub-packages are published to NPM. We use a tool called changesets to manage versioning, cross-dependency versioning and publishing new versions to NPM. When you make a change, before mergin to master:

• run yarn changeset and mark the packages you wish to publish, select what kind of a change it is (major,minor,patch) and provide the summary of the changes

When you want to publish all previous changes to NPM:

• now run yarn changeset version, this will change the generated .changeset/file.md into an entry into CHANGELOG.md and package.json in changed packages

After your PR with changed CHANGELOG.md and package.json is merged into main, a CI step will run which will try to publish all change changes.

l2beat's Issues

Add Layer2.Finance Rollup

https://blog.celer.network/2021/04/22/the-layer2-finance-v0-1-mainnet-launches-democratize-defi-simple-and-zero-fees/

Add zkSwap

Original PR was merged here: https://github.com/krzkaczor/l2beat/pull/32 and later reverted.

We can't add it to l2beat unless the code is verified on etherscan. Once it's don't we are happy to add it.

Group the projects by L2

Currently the projects list seems to be mixing L2s (Optimism, zkSync, etc.) and L2 projects (dYdX and ImmutableX). Instead I suggest that the projects be grouped by L2, like in the following "mockup":

	NAME	VALUE LOCKED	MARKET SHARE	TECH	1 DAY %
1.	Loopring	$200.42M	60.37%	zk-rollup	+8.72%
2.	Optimism	$106.47M	32.07%		+9.84%
	Synthetix	$106.47M	32.07%	optimistic rollup	+9.84%
3.	StarkEx	$15.29M	4.61%		+4.30%
	DeversiFi	$??.??M	?.??%	validium	+?.??%
	dYdX	$14.73M	4.44%	zk-rollup	+4.60%
	ImmutableX	$561.32K	0.17%	zk-rollup	-7.97%
4.	zkSync	$9.24M	2.78%	zk-rollup	+3.57%
5.	Aztec	$534.08K	0.16%		+6.41%
	zk.money	$534.08K	0.16%	zk-rollup	+6.41%
6.	Fuel	$4.22	0.00%	optimistic rollup	-0.17%

NB: Despite not having the DeversiFi numbers, I added it as an example that tech can vary for the same L2.

I guess you could also add "validium, zk-rollup" to the StarkEx row, but I'm not sure whether or not that would improve readability of the list:

	NAME	VALUE LOCKED	MARKET SHARE	TECH	1 DAY %
...
3.	StarkEx	$15.29M	4.61%	validium, zk-rollup	+4.30%

Add missing Optimism bridges

Here's a token list with bridges extensions: https://github.com/ethereum-optimism/frontends/blob/master/packages/gateway.optimism.io/src/tokenLists/optimism.tokenlist.json

For most tokens, it should be enough to track the balance of the L1 bridge (optimismBridgeAddress on chainId = 1). In some cases like DAI, funds are escrowed in a separate contract: (0x467194771dAe2967Aef3ECbEDD3Bf9a310C76C65 in DAI's case).

Upgradability of Polygon Hermez is potentially inaccurate

A question was raised on Polygon's Discord server, to which one of the responses from the team was:
https://discord.com/channels/635865020172861441/910852199905624124/914840921814732851

According to the response that I've received for my initial question, the delay variable for the following smart contract is responsible for the upgradability delay:

https://etherscan.io/address/0xf7b20368Fe3Da5CD40EA43d61F52B23145544Ec3#readContract

604800 / 86400 = 7

If this is the case, the Upgradeability of Polygon Hermez needs to be changed from 'Yes' to '7 days delay'.

Move to a server backend

Replace the current backend with a server that exposes data as an endpoint

Update classification to some projects (zkRollups vs Validium)

Clearly differentiate between zkRollups and Validium architectures:

• ImmutableX is Validium not zkRollup
• zkSwap is likely to be Validium as well
• add DeversiFi (which is a Validium)
  Update "Learn about Layer2" with reference to articles explaining Rollups vs Validium, etc...

List tokens that are held/supported by the bridge in the Rollup details

It would be nice to list tokens that are held by bridge/deposit contracts as they are currently defined in the config

Add a section describing L2BEAT to the main page

This should help with SEO keywords.

Automatically add descriptions to bridge contracts in contract list

Clearly differentiate between intent and implementation risk on the summary page

Right now it's not visually clear that, for example Optimism is using Fraud Proofs, or that it is possible, when Operator is down for users to submit state batch and relay L2 -> L1 message themselves. Maybe the text for State validation should say "Fraud proofs" with red colour and hint "Currently disabled". Similarly the "Operator Down" - can be explained that it is possbile, however right now only Sequencer and Relayer can push tx on L1 and relay them

Make the table sortable

Hey, it would be cool if the table colums could be sortable.

Automatically fetch recent news

use Arbitrum token list json for tokens on Arbitrum

https://bridge.arbitrum.io/token-list-42161.json (which we host) has all of the tokens bridged onto Arbitrum; if you dynamically fetched the list from there (instead of hardcoding it) we would never have to bother you about updating it :)

Add Unverified Smart Contracts warning to the summary page

Unverified Smart Contracts should be considered a major no-no in our space. Nobody except from in-the-know devs and testers should ever use contracts that are unverified. If the Rollup is using even a single unverified smart contract, we should display the big red warning in the summary page to attract user (and developers team) attention

Fuel "Current level of decentralization" incorrect

The "Current level of decentralization" for Fuel is incorrectly described as "Low" for the following reasons.

Test deployment on mainnet?
no verified source on etherscan

1. Fuel was the first optimistic rollup to be deployed to mainnet, and was deployed in 2020.
2. The source code can be deterministically compiled and verified against the bytecode on the Ethereum blockchain. Verifying code through a centralized block explorer does not decentralized make. We provide a helper script here: https://github.com/FuelLabs/fuel/blob/2ca18a536dfa8717e743138a4463347b3f2574dd/package.json#L30 that can be used with just a bit of elbow grease.

Last 2 reference links on optimism page lead to 404s

These links are no longer valid: https://github.com/l2beat/l2beat/blob/master/packages/config/src/projects/optimism.ts#L156-L165

Add zkSwap

https://twitter.com/ZKSwapOfficial

Add other EVM based chains and state how they are different

Add other EVM based chains and state how they are different. e.g. Fantom, AVAX, BSC, HECO etc.

Upgrade Optimism contracts after the Nov 2021 regenesis and network upgrade

https://twitter.com/optimismPBC/status/1458953238867165192?s=20

Explain the difference between L1 and L2

There is a lot of confusion in the community about what should be called an L2. The intention of l2beat.com is to provide transparent and verifiable info about the state of "L2" for Ethereum L1 chain. Other blockchains (e.g. Solana, Avalanche, Fantom, BSC, Polychain, etc...) are L1s. The main page of l2beat.com should explain the approach and the difference clearly

Add more Starkware based projects

DeversiFi https://etherscan.io/address/0x5d22045DAcEAB03B158031eCB7D9d06Fad24609b
ImmutableX https://etherscan.io/address/0x5FDCCA53617f4d2b9134B29090C87D01058e27e9
dYdX https://etherscan.io/address/0xD54f502e184B6B739d7D27a6410a67dc462D69c8

When switching to risk view add ?view=risk to url

Fix Synthetix Optimism bridge

Synthetix Optimism bridge has migrated to a new version - data pipeline should be fixed to reflect the migration and report SNX locked in the bridge properly again

Add arbitrum

As far as I can tell this is the bridge: https://etherscan.io/address/0x86E525A3565235b2bb934df43E01c8B092c03756

(according to: https://github.com/OffchainLabs/arbitrum/pull/1207/files#diff-2da1fbae6049ec2e07ed7f62a55ae7f4e565dd09e98d108b4ad0a6ed57e24917)

There are no funds stored there yet. Once they control some funds we can start tracking it.

Possible outdated contract in Aztec configuration

the page for Aztec lists two different versions of the TurboVerifier contract

• under Smart Contracts, links to 0x7379…A2ba which has an unverified dependency. this lines up with the risk described in the risks sections: the source code of unverified contracts contains malicious code (CRITICAL).

• under References, links to 0xbc87.... this looks like a newer version of TurboVerifier, which does not have the unverified dependency issue.

chart code

Hey, I find our chart on L2Beat quite beautiful and I also noticed that it's using svg. I'm the author of an SVG line chart library: https://github.com/rugpullindex/svg-line-chart I use it to instantly give users a chart upon page load. And looking at yours, I was wondering what library you're using or if it's your implementation.

I'm interested in reading the code. Maybe there's even a chance to collab on a chart lib?

Arbitrum "Permissionless" and "Force TX mechanism" descriptions

The key here is that for both of these, the sequencer can be avoided entirely.
I.e., Force TX mechanism currently reads

• "Sequencer can be forced to append a txn to the rollup"
  This actually isn't true, but there is a force tx mechanism; a user posts their transaction directly on chain, and eventually it will be made available for validators to include in assertions (no sequencer involvement).

Likewise, permissionless reads

• "Only the sequencer can produce blocks
  Any body can be a validator and make assertions (i.e., propose state updates to Arbitrum). The Sequencer only has a special privilege to propose fast soft-confirmed updates before things hit the L1 (i.e., before an assertion is made). I think I'd argue that this effectively makes Arbitrum itself a "Permissionless? Yes", tho this is debatable, since the sequencer itself is a permissioned entity.

(As I've said elsewhere, this is by far the best L2 tracker I've seen — thanks for putting it together!)

Add x-axis labels to the chart

Add HBT (Hubiits) token for Nahmii.

Nahmii has some value locked in HBT tokens. However this token has the same symbol as the Habitat token. This requires a rework of how we identify tokens.

Prove dYdX is a rollup

There were some concerns raised on Twitter. Find out where the data is stored on chain.

Make the "Log" vs. "Linear" selection for the graph axis persistent

A month or two ago, L2beat added a selection button to enable a Logarithmic scale on the y-axis. This is super useful. Thanks.

But as it stands, the web app resets the axis view to Linear every time the page is opened, or refreshed.

This forces the user to have to manually reselect the "Log" view each time if they prefer logarithmic scales.

(personal opinion: log scales are vastly better than linear scales for properly analyzing exponential growth, which a very great deal of blockchain adoption data is. E.g., growth in overall L2 TVL in the recent week/month; or the growth of Arbitrum L2 in any reasonable time period now.)
But hey, let's make it user-selectable, and persistent.

Could you consider adding a way to store the user choice used on the L2beat.com website to be persistent? A non-tracking cookie? Or something else?

zkSync risk upgradability period

Per https://medium.com/matter-labs/keeping-funds-safe-a-3-factor-approach-to-security-in-zksync-2-0-a70b0f53f360#e655 the upgradibility poeriod is 4 weeks not 2 weeks.

Problem: Arbitrum - Description

No longer developer whitelist only! Open to public now as "beta"

Update TVL every hour

With the exponential growth of L2, it'd be awesome to see the TVL change hour-by-hour.

Enable per branch frontend builds

add renBTC to Aztec bridge

https://etherscan.io/address/0x737901bea3eeb88459df9ef1BE8fF3Ae1B42A2ba

List explorers in Project page

Would be nice to show a list of related Explorers in Project in a nutshell area

ex:
optimism https://mainnet-l2-explorer.surge.sh
zksync https://zkscan.io/explorer
fuel https://mainnet.fuel.sh/network

Layer2.finance TVL reported incorrectly

Layer2.finance batches deposits in one place and then uses these funds to invest in various DeFi protocols. That's why watching TVL only on the bridge contract ends up greatly underestimating TVL.

CC: @Dominator008, do you have any library that can help us with this?

Allow switch between USD or ETH denominated TVL

As TVL in USD varies depending on the coin price (in USD), sometimes a better metric is to use ETH as quote currency. This is especially true for Rollups that take only ETH (like ImmutibleX). OTOH dYdX takes only USDC as a deposit, so USD is a better quote currency. More generic Rollups that take many tokens may benefit further from token breakdown, but initially switch between USD/ETH should add a lot of insight

Problem: Aztec - Contracts

Thanks for the great work bringing transparency to the L2 ecosystem. One note: On Aztec, the site currently specifies that the source code for the VerificationKeys contract is not public. This is verified on Etherscan here:

https://etherscan.io/address/0xDCC80dB987bf63f01b7bafCED6230DE5002eF874#code#F5#L1

Thanks

Joe

Add DAI Gateway to Arbitrum

DAI on Arbitrum is using custom gateway:

https://etherscan.io/address/0xA10c7CE4b876998858b1a9E12b10092229539400

Change the Classification of ZKSwap from Validium to ZK Rollup

Hi! ZKSwap is a project based on ZK Rollup solutions. Please help change the tech classification. Thank you! Here is the link to our contract: https://etherscan.io/address/0x8eca806aecc86ce90da803b080ca4e3a9b8097ad

Switch from coinpaprika to coingecko for datapipeline

• Coinpaprika misses some tokens
• There are "holes" in data

Add Hermez rollup

Bridge: https://etherscan.io/address/0xa68d85df56e733a06443306a095646317b5fa633 (~200k USD)

Add email notifications on CI cron job failures

📌 L2BEAT Roadmap 09.2021

This document outlines our focused tasks for L2BEAT starting September 2021. It minimally indicates intent to investigate tasks or contribute to an implementation. Nothing is set in stone, but we will strive to complete these tasks in a reasonable timeframe.

Architecture changes

• Move to a server backend (CURRENTLY IN PROGRESS)
• Update stats every hour
• Automatically fetch recent news

Frontend improvements

• Store chart state in the URL
• Add x-axis labels to the chart
• Make the table sortable
• Enable per branch frontend builds

Research

• Prove dYdX is a rollup
• Investigate Aztec smart contracts

Add adnotation about the current Optimism mainnet launch safeguards

• no way to use Fraud Proof verifier making this effectively PoA sidechain rather than proper rollup
• enqueuing transactions via L1 currently disabled
• deployment on L2 only whitelisted smart contracts (currently only Synthetix)

Store chart state in the URL

When looking at different tokens add ?token=XXX to the url

Update project links to look similar to details on wikipedia