just deployed , a website to easily check how much you have to wait to include a blacklisted tx with the current % of censoring nodes or a custom amount
a weekend project by
@emilianobonassi
and me ๐๏ธ
.
@Taikoxyz
currently pays an insane onchain cost of almost $1M per **week** even with blobs, and with only ~358K txs, or around ~$2.50 per L2 tx
for comparison, every project except Scroll pays <$60K per week
The Polygon vs ZKsync drama is so tiring. Please copy each other. I beg you. After reading the code of all major systems, I guarantee that we would have saved millions of hours if teams just looked at each other code instead of reinventing the same thing over and over but worse
Unfortunately this is the case. Almost all L2s are still centralized and can pull the plug and turn off the chain at any moment.
All, except
@MetisL2
, the real
#decentralized
#Layer2
.
@donnoh_eth
Nice picture! Did you draw it yourself?
Or did you copy-paste from someone?
Is this source reliable?
Did it warn you that any Layer 2 at the moment can pull the plug and turn off their chain?
That almost any
#Layer2
can be switched off at any moment on the request of any party
TLDR on
@redstonexyz
: OP stack chain with offchain DA with no attestations, but with DA challenges. They claim this mechanism is a "Plasma" implying that the system is as secure as a rollup, but it's trivial for the sequencer to outspend honest challengers and steal funds.
Today weโre excited to announce L5s on Conduit
With L5s, weโre skipping ahead to the next breakthrough in blockchain scaling โฉ
L5s are chains that settle on an L4, which settle on an L3, which settle on an L2, which settle on Ethereum L1
Reminder that
@LineaBuild
can finalize state roots without verifying ZK proofs, meaning that it can potentially finalize invalid state transitions, which is what happened with their Alpha v2 release.
Tx:
Celestia explained from an Ethereum alignment perspective in 6 steps:
1. letโs build a secure DA layer for Validiums
2. every external DA acts as a DAC with an honest majority assumption, letโs try adding economic guarantees
3. data unavailability is not provable externally, but
new article just dropped:
table of contents:
- scalability bottlenecks
- the (proto-)blobspace
- high level implementation
- from proto-danksharding to full danksharding
- concerns
- appendix: why are polynomials so useful?
random dump of excalidraw diagrams that are too pretty to be left unseen
1. arbitrum finality <> cost optimization strategy
2. zksync era 4844 impl
3. the many ways alt-DA can screw you up
4. โจsemanticsโจ
quick blogpost (4min read) on the differences between live forced tx mechanisms and based sequencing as a preview to the soon to be published 30min article by
@jon_charb
One of the most important discussions on Ethereum security just dropped on the eth research forum:
โSticking to 8192 signatures per slot post-SSF: how and whyโ by vbuterin
In the midst of
@L2DAYSxyz
preparations, weโve just rolled out another Quality of Life update on our website: new filters that will make your exploration even more insightful! ๐๐ก
Just finished writing the short paper (13 pages) version of my bachelor's thesis for DLT 2023 (5th Distributed Ledger Technology Workshop), that will take place in Bologna on May 25-26. You can find it here:
In the past two days many have discussed that, since there are no fraud proofs, Blobstream wouldn't have added any security to
@MantaNetwork
.
Let me explain why this is not true ๐
Exciting opportunity at L2BEAT! ๐
We're seeking an L2 Researcher who will collaborate daily with our top-tier Ethereum experts, placing you at the heart of the latest developments in this field!
Apply here ๐
๐ Your Role:
- Investigate and analyze
Finality is probably one of the most challenging metric that we track on
@l2beat
: it requires tracking contracts, permissions, the projectโs derivation spec and the L2 node software in general
๐ Introducing BYOR (Build Your Own Rollup) ๐
We're beyond thrilled to unveil our new tool: BYOR - a gateway to sovereign rollups, stripped down to the core for a better understanding of the rollup magic! โจ
things to keep in mind:
- Ethereum DA is trustless, for EigenDA you need to trust a quorum of the operators
- # of stake does not increase security, the amount of independent operators does
- proof of custody has little to do with DA proofs, DA faults are non attributable!
Intro to EigenDA: Hyperscale DA for Rollups
This post represents our 1st public, long-form content about EigenDA - what it is, how it works, what benefits it offers to rollups. There's too much to summarize fully, so please read at the link below!
1/5
with only 2 days left, here's my application for RPGF:
even if i don't make the 17 ballots threshold (now at 7), i really appreciate people voting for me, it's really amazing to see people finding my content useful :) thanks!
a common narrative is that zkRUs are secured by math while ORUs are secured by economic incentives, and so are much weaker
@arbitrum
โs BoLD proves this wrong: even if a malicious actor has infinite money to burn, the protocol always resolves correctly within some time bound
Today,
@RedstoneXYZ
Mainnet is officially live and part of the Superchain ๐ด๐ชจ
Joining the Superchain means scalability, low fees, and contributing revenue to the Optimism Collective to power open source development.
TLDR: itโs not EigenDA, itโs not even a fork of EigenDA, itโs not restaking either โ you need to stake $MNT with a proof of custody mechanism, except the mechanism is not live and neither is the staking
Turns out this part is wrong ๐ if a block is not available, the node doesn't wait for it to become available because the sequencer also specifies the block height where the blob is posted. If the blob isn't there, the commitment is just skipped. Let's go through the steps:
What happens if the Sequencer publishes a tx commitment that is not available on Celestia? Blocks cannot be derived and the chain halts, blocking all activity on the rollup. Take a moment to appreciate how this scenario is not possible with rollups posting full data.
hereโs axelrod, a cairo contract to create and manage iterated prisonerโs dilemma tournaments built by
@_derked
and me :)
it implements:
- matchmaking logic
- custom tables
- history of matches
- a template for Finite State Machine strategies
The Stages Framework was introduced on
@l2beat
in June 2023 and since then no rollup has moved up in stages yet. We can discuss semantics how much we want but ultimately this is what really matters.
Letโs make Ethereum cypherpunk again.
Fourth, continue improving on security.
We need to raise our standards. By the end of the year, I think we should only refer to rollups that are at least stage 1 as "rollups".
Moving to stage 2 (fully trusting code) is the next step and will require moving carefully.
.
@NoirLang
is such a cool language. You know that something is good when you use it even if theyโre not a sponsor.
And if youโre curious about our project: :)
So much fun on a zkHack this weekend. Our zkMNIST team managed to win the
@NethermindEth
zkML track and a โCoolest project deployed on
@zksync
โ track. Great job team, it was a pleasure to hack with you guys!
@dystopiabreaker
> canโt think of a single time iโve ever used an immutable append-only data structure that can only ever grow its memory usage
> appends the tweet on a data structure that can only grow its memory usage
anyone working on rollups should take a moment to deeply understand this take and why itโs only possible on a fully functional system.
on why the 75% threshold is a big deal, we have some in-depth rationale here:
@ArthurB
No multisig can achieve the property "you need 75% dishonest to steal the money, and you need 75% dishonest to freeze the money". A multisig can only achieve (p, 100% -p)
since
@arbitrum
specifies its challenge window in blocks rather than time, and assumes block times to be 13.2s, the interval was reduced from 7d to ~6d and 9h after the merge due to the new 12s block times
.
@arbitrum
trying to catch up with yesterdayโs downtime
top row: # batch submission per hour, increasing
bottom row: time intervals between batch submissions, decreasing after yesterdayโs spike
@0xMert_
also friendly reminder that conduit chains are all upgradable by the same multisig (includes zora, aevo, hypr, orderly, ancient, lyra, mode, pgn, parallel, metal)
Polygon zkEVM Mainnnet Beta faced an issue with its sequencer due to an L1 reorg. We are working on fully resolving the issue and will follow up with a detailed post-mortem.
This only impacts Polygon zkEVM (which is the only rollup) and does not impact Polygon PoS, Polygon CDK,
L2Warsaw by
@l2beat
has been amazing! really proud of the team for organizing such great talks with fantastic speakers
canโt wait for L2Days in Istanbul
@EFDevconnect
๐
.
@Taikoxyz
could have done the best marketing move out there by making sequencing permissionless before the airdrop to then brag how much profitable being a sequencer is and how they had zero downtime
oh well
i take this back. looks like bonds are necessary to prevent exhaustion attacks. might feel pretty and write an article about it
not all fraud proof systems are created equal
a common narrative is that zkRUs are secured by math while ORUs are secured by economic incentives, and so are much weaker
@arbitrum
โs BoLD proves this wrong: even if a malicious actor has infinite money to burn, the protocol always resolves correctly within some time bound
@0xMarcB
my hot take here is that all optimiums (maybe with the exception of Nova) currently live on
@l2beat
are much less secure than Polygon PoS bridge
but itโs still useful to distinguish between sidechains (two consensus) and optimiums/validiums (one consensus) security-wise
just deployed on
@BuildOnBase
, the project that i built around 2 years to learn about solidity
-> fully onchain text NFTs supporting plaintext, markdown and even HTML (with full unicode support too)
coming back to this to give some concrete numbers: next gen BoLD protocol by
@arbitrum
expects a correct root to be confirmed in around 45 moves (or 89 including update moves) implying 1
to 3 months to settle on Arbitrum One
How do challenge periods for fraud proof-based L3s work? You have to assume the worst case scenario - L2 sequencer censorship. In which case, each step in the interactive dispute needs to be forced through the L1 (which requires a โ24 hour delay). Unless the process requires < 7