Adrian 💗

Software developer, tweeting about blockchain technologies, AI & VR. Dev & research @l2beat 💗

[L2BEAT 💗 @l2beat]

A perp DEX differs from a CEX if it delivers two things: property rights over your collateral, and verifiable execution.

We spent some time looking into how @Lighter_xyz and @HyperliquidX actually hold up against both. The answer is more nuanced than either camp wants you to believe. 🧵

[Georgios Konstantopoulos @gakonst]

Symbolic Testing in Foundry - forge test --symbolic

Foundry has been used to secure >100B of value in deployed smart contracts. This is achieved through state of the art high performance fuzzing made available to every developer for free.

Going beyond fuzzing, AI empowers us to move towards formally verifying / proving security of our code by writing complete models of the behavior we want faster.

We have finally started to make progress towards symbolic / concolic execution in Foundry.

Try it out!

https://t.co/uMzWfs9dHb

[sergeyshemyakov.gwei, PhD 💗 @sergeyshemyakov]

Does anyone have trusted setup artifacts of @RAILGUN_Project? The IPFS CID QmWAySHYhaZqioKi1ufrPJC1n1ZVtHP2w4hLA9XqqJCFne seems unavailable now.

I need the trusted setup files to reproduce vkeys and verify zk circuit integrity.
@tsu_kareta @mesquka

[sergeyshemyakov.gwei, PhD 💗 @sergeyshemyakov]

Last Saturday I presented at @JoinBrewBerlin conference in @JoinFutura in Berlin.

If you want a sneak peek behind @l2beat latest dashboard and learn:

- how mixers work
- what privacy metrics we show
- how we think about privacy

check out the recording
https://t.co/xahskfVoX5

[L2BEAT 💗 @l2beat]

Our research team came across a @TornadoCash DAO proposal, and we suspect it might be malicious.
We are asking the community to look into this matter, details are below 👇

[sergeyshemyakov.gwei, PhD 💗 @sergeyshemyakov]

1/ A suspicious DAO proposal on Tornado Cash was created ~8hrs ago. Summoning @pcaversaccio (and everyone else curious) for an independent opinion!

Details in the thread below👇

[_gabrielShapir0 @lex_node]

@binji_x @l2beat is the @l2beat for privacy

https://t.co/fba931rSi0

[L2BEAT 💗 @l2beat]

STRK-20 on @Starknet just got added to our Privacy dashboard!

It is a centralized privacy pool with trust assumptions comparable to recent institutional privacy offerings. A single admin account has visibility over all shielded transfers, and users lack transparency regarding if or when their transaction data is disclosed.

[ethresearchbot @ethresearchbot]

New post on https://t.co/j5UaKGaEf3!

Repurposing FOCIL as an L2 forced transaction mechanism

By:
- donnoh

🔗 https://t.co/axFcf8lXiE

Highlights:
- Proposes a forced-transaction path for EVM L2s by “repurposing” FOCIL: an onchain (L1) contract builds an inclusion list that the L2 validity proof/verifier must satisfy, bypassing a censoring sequencer without changing the L2 state transition function or adding new tx types.
- Unlike OP Stack/Arbitrum forced tx designs (which add special unsigned/deposited tx types and reserve block space or bypass base-fee constraints), this approach relies on standard signed transactions plus an inclusion-list validity rule enforced at settlement/proving time.
- To prevent inclusion lists being dominated by invalid transactions (e.g., high maxFeePerGas but wrong nonce/insufficient balance), the contract requires submitters to attach a recent L2 account proof (via eth_getProof) so the contract can do stateful admission checks without storing the whole L2 state on L1.
- Because FOCIL-style inclusion lists don’t directly reveal whether a tx was excluded due to invalidity vs. a full block, the post suggests two cleanup strategies: (1) permissionless pruning using newer account proofs (with a small bond to pay pruners), and/or (2) operator-provided Merkle proofs at settlement to show non-inclusion when block space remained—allowing safe dropping of invalid entries.
- Highlights a usability gap: generating account proofs typically requires access to a full node; the post connects this to VOPS/BALs and notes that adding storage-root updates to block-level access lists (as proposed in EIP-8268) could enable lightweight “accounts-only” nodes that can still produce the proofs needed to submit forced transactions.

ELI5:
Many Ethereum L2s have one “boss” computer (a centralized sequencer) that decides which transactions go in next. If that boss ignores you, you need a “forced include” button. This post shows how to build that button by reusing an Ethereum idea called FOCIL (a required-to-include transaction list), but implemented using an L1 smart contract—so L2s can get censorship resistance without inventing new L2 transaction types or changing the L2 execution rules. It also explains how to avoid spam/DoS by making submitters prove their account has the right nonce and enough funds, and how to remove (prune) transactions later if they become invalid.

[sergeyshemyakov.gwei, PhD 💗 @sergeyshemyakov]

Tomorrow I will be talking about the new L2BEAT Privacy Dashboard in Funkhaus Berlin.
Come learn about moving tokens privately onchain, risks of Tornado Cash, Railgun and Privacy Pools and the fine print nuances of privacy! See you at @JoinBrewBerlin

[L2BEAT 💗 @l2beat]

We’ve expanded the L2BEAT Interoperability Dashboard to support @trondao and @Plasma!

Both are now live and trackable. Let’s dive straight into the numbers from the last 24h 🧵👇

[Base @base]

Enterprise-grade private transactions are live on Base

Introducing Base Privacy: a native and compliant infrastructure for enterprises

Financial institutions can trade, pay, and settle with confidentiality on crypto rails

[L2BEAT 💗 @l2beat]

Set your reminders! ⏰

Tomorrow is Protocol Day at @JoinFutura and our researcher @donnoh_eth is doing double duty: first hosting a panel, then dropping a technical talk.

[OpenAI Developers @OpenAIDevs]

More of Codex is rolling out across Europe this week.

We’re bringing Computer use, the Codex Chrome extension, personalized memory, and Chronicle to Codex users in the EEA, UK, and Switzerland.

https://t.co/tsriEswcyY

[Artificial Analysis @ArtificialAnlys]

We've updated the Artificial Analysis Coding Agent Index, replacing SWE-Bench Pro with Datacurve's DeepSWE benchmark - the swap lifts Codex with GPT-5.5 (xhigh) above Claude Code with Opus 4.8 (max), while the newly released Claude Fable 5 (max) in Claude Code debuts at the top

DeepSWE, built by @datacurve, writes its tasks from scratch rather than adapting them from public GitHub issues or pull requests, so no model has seen the solutions during training. That matters because SWE-Bench Pro, the benchmark it replaces in our Coding Agent Index, had grown gameable, with some models recovering the fix from the repository's commit history instead of solving the task.

The swap reorders the index: Codex with GPT-5.5 (xhigh) rises from 65 to 76, overtaking Claude Code with Opus 4.8 (max) at 73. Claude Code with Fable 5 (max), which enters directly on the refreshed index, leads at 77. SWE-Bench Pro had been flattering some combinations and penalizing others.

More below.

[L2BEAT 💗 @l2beat]

In case you missed it... we’ve had an incredibly useful feature running quietly on L2BEAT for a while now, but we never officially shouted it out.

It's time to finally shine a spotlight on the Updates section.

[vitalik.eth @VitalikButerin]

Looks like the options thing is happening already!

See also: various people thinking through and building different versions of the idea in the thread: https://t.co/gFNEvCbHct

Though I do strongly urge that if any of these get on mainnet quickly, we formally verify it first. I hope @vyperlang and/or https://t.co/OMFlWRqJda folks ( @Fricoben) can help!

(Also, now is a good time to be thinking about robustness-optimized oracles)
https://t.co/j1dxLV4Pn4

[L2BEAT 💗 @l2beat]

Introducing the new State Validation page, which allows you to quickly compare the proof systems of existing projects.

[L2BEAT 💗 @l2beat]

Today is a big day for all @Starknet fans: its proof system is finally 100% reproducible from the sources, verified by L2BEAT ✅

Starknet no longer risks demotion to Stage 0 in 70 days, and the red warning is gone

👇See what we did in this thread👇

[Signal @signalapp]

Our statement on the UK government’s demand that all content on all devices sold or used in the country be scanned, on the presumption of nudity, using a dystopian combination of age verification and content scanning. This proposal will not safeguard children. It endangers us all.

https://t.co/VdWe9uhi8p