itout

[itout @date_toya]

Paillier暗号を用いたScriptlessなECDSAのMultisigがあったので、それを少し改変したものを書いてみました。
元のものが公開鍵を2者で協力して計算するのに対して、第三者が既知の公開鍵で勝手にMultisigを構成できるのが少し面白い点になっています。
https://t.co/ithTeXu4TP

[Mai🧬zERC20🎭INTMAX @missbitcoin_mai]

zERC20 meetupは6月12日（金）に開催になりました！（11日に希望されてた方すみません、スタッフのスケジュール的にこの日になりました🥹）

お席が30席しかありませんのでご関心のある方はお早めにご登録お願いします！

会場を提供を申し出て下さったCoinpostさんありがとうございます🙏✨

https://t.co/GNTSl40J5T

[itout @date_toya]

クロスチェーン検証の代表的な手法を紹介する記事書いたことあったなと思って掘り出してみたらもう3年以上前なのか
この時はzkEVMがまだ研究段階とかだったなー
https://t.co/giC2FO9r2D

[itout @date_toya]

KelpDAOの件、mainnetの総供給量が増えてないってことは無限ミントではなくて、ブリッジのためにロックされてるトークンがブリッジ先トークンのバーン無しに解放された形ですかね？
その原因がバーン/解放の検証者が1 of 1かつその検証者の鍵が漏洩したっぽいと

[Optimism @Optimism]

We're experimenting with how transactions are ordered on OP Mainnet — for the first time ever.

Stake-based transaction ordering is live on Sepolia today. Stake OP, get top-of-block access.

Here's what's happening and why 🧵

[itout @date_toya]

まだみんな真面目に大学来るから学食が普通に混んでる

[itout @date_toya]

とりあえず論文できて添削待ちなのでしばらくゆっくりできる…

[Kobi Gurkan @kobigurk]

Happy to share Proximity signatures, a note with @angeris!

What if we want to verify signatures on messages that are way too big? And in addition, get some guarantees on them?

Verifiers are then in a problem!

1/8

[itout @date_toya]

LaTeXのコンパイルも出力されたPDFも謎に重いと思ったら、載せてるシーケンス図画像の解像度が軒並み5000×5000とかで笑う
使ってるMermaidエディタがやたら高解像度の画像を出力してたのが原因という

[itout @date_toya]

ColliderScriptの面白ポイント
形式は違うけど本質的には同じ2つの値が等価であることを衝突するハッシュ値を持ってくることで証明する
https://t.co/TsojHYPrJL

[itout @date_toya]

指定された原像に衝突する別の原像を160bitのハッシュ関数で見つけるの、2個はさすがに無理だけど、1個ならできる（ただしBitcoin33時間分のハッシュ計算が必要）っていう発想
あまりにも奇才すぎる

[itout @date_toya]

Bitcoinの変更なしでコベナンツを実現できる代わりに1回80億円かかる、ColliderScriptとかいう頭のおかしい技術があったんですけど、その著者の一人が近い仕組みで量子耐性トランザクションの提案してて熱い
普通のトランザクションに2万円かかるので一般用のものではないけどよくこんなの思いつくなー

[Avihu Levy ✨🐺 @avihu28]

Quantum-Safe Bitcoin Transactions Without Softforks

https://t.co/1lx5waX9VV

[itout @date_toya]

所謂DIDとかVC(Verifiable Credentials)って実際に使われるイメージそんなについてなかったけど、こんなに至る所で北朝鮮工作員の侵入があると割と大事な気もしてくる

[itout @date_toya]

論文一章進んだ！偉い！

[itout @date_toya]

Claude Opus 4.6にBLS12-381プリコンパイルのラッパー書かせたら、コンテキストから推測してG1を署名としてバッチ検証まで実装してくれてとても偉い
その割にリストに特定の要素が少なくとも1つあるか線形探索で確認する処理で、見つけてもループを抜けずに全探索する変な実装してきたりするから不思議

[itout @date_toya]

元々enshrined L2/ZK-EVMで汎用L2が飲まれるみたいな話はあったわけですからどこも全くの無策というわけではないでしょう
これまでそういうの作ってたチームは大変だろうけど、見てる側からするとAztecとかINTMAXみたいな尖ったL2がこれから色々出てきそうで楽しみ

[itout @date_toya]

Optimism Superchain構想が推してたモジュール化とか相互運用性みたいな部分は、L1スケーリングを前提とした環境で求められるL2の独自性とは相性悪そうですしね...
その点はArbitrumとかの方がまだ救われてる印象

[まめだい / mamedai 🐼🏴 @0xmamedai]

うわ、baseがop stackから離脱した…
ちょっと激震かも。

[wilson.base.eth @WilsonCusack]

A new, unified stack for Base Chain

Excited to share that we are evolving our technical roadmap, consisting of our own spec, code, and infra to accelerate the foundation of Base. This shift gives us the autonomy to ship protocol improvements more frequently and focus our resources on scaling to 1 gigagas/s.

What this means for builders:

- Higher Velocity: Targeting 6 hardforks per year to get you new features and fixes faster.
- Massive Scale: Targeting 1 gigagas/s to support high-throughput apps without congestion.
- Extreme Reliability: Targeting 99.99% non-empty blocks and predictable, low fees.
- Simpler Design: A maximally simple spec that’s easier to audit and build on.

Along with this, we will take a more active role in managing our own upgrade schedule and stack: allowing us to build what the ecosystem needs, at the speed it needs, while remaining deeply aligned with Ethereum.

Read the full technical breakdown here: https://t.co/5gVnhgh2Q5

[Leona 極度妄想（しなさい） @leo_hio]

このVitalik案、マジで振り切れてるな。オンラインで期間限定で配るUTXO型のasset（Intmax型といっていい）を扱うストレージをL1に用意する。

これビットコインで例えたら、ライトニングネットワークがL1にビルトインされているような感じの印象だろうな。（Arkのが近いけど）

狂気じみた提案だけれども、できたら他のチェーンは全部一世代前にみえるだろな。達成できたら誰の目から見ても疑う余地のない1番技術の進んだチェーンだ。Vitalikが周りに気を遣わなくなって覚醒してる。

https://t.co/u4ugc81aR8

[itout @date_toya]

enshrined L2とかenshrined ZK-EVMとかの話の段階でただのEVM L2の意義が薄れるみたいなことは言われていたので、方針の大転換みたいな印象はない気もする

[vitalik.eth @VitalikButerin]

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts:

* L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected
* L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026

Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path.

First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum.

This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead.

We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs.

What would I do today if I were an L2?

* Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features
* Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets
* Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?)

From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug.

The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately).

This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: https://t.co/9jy6v1X6Fw and https://t.co/gZmu3YjebM ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add.

This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

[itout @date_toya]

クリプト暴落時の映画見てる率が謎に高い

[itout @date_toya]

crypto × ARG、オンチェーンのコントラクトで賞金とかが確認できて自動分配されたらめちゃくちゃ楽しそうなんですよね