UXとセキュリティのトレードオフ jamalavedra.com/blog/auth-jw…

5/29にGoogle Cloud Data & AI Summit'26 Spring に『2,000 万人の熱狂をインサイトに変える: BigQuery ML で実現する「自律型」インテリジェンス・パイプラインの全貌』というタイトルで登壇します！AI x ディメンショナルモデリングの話をするので気になる人はみてみてね。 cloudonair.withgoogle.com/ev…

日本を代表するエンタメ企業3社様にご出資いただけたことを、心より光栄に思うとともに、深く感謝申し上げます。 一方個人としては、自身の力不足や未熟さを常に痛感する日々です。 掲げた大義である"ファン国家"の実装に向け、一歩づつ誠実に努力していく所存です。

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: ethresear.ch/t/combining-pre… and ethresear.ch/t/synchronous-c… ). 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.

docs.cloud.google.com/servic… GCPのservice extensions、LBに拡張ロジックをカスタムで追加できるので便利そう。 wasm moduleとして実行される（plugin）とserviceを建てるパターン（callout）の2種類がある。 envoyのproxy wasm, ext_authz, ext_proc周りが関連している

herp.careers/v1/gaudiy/d3EXf… もし興味ある方いたら、プロダクトデザイナーの募集してるので連絡いただけるとありがたいです mm

✧･ﾟ #GauDev Advent Calendar 2025｜DAY25🔔･ﾟ✧ 最終日はVPoE @r34b26 による、自身が影響を受けたひとや作品から現在地を見つめた等身大の記事です📍これまでの葛藤と、これからの覚悟を語ります。 --- スタートアップ8年目の足りなさ｜kodai3 #アドベントカレンダー note.com/kodai3/n/nb12e12d62…

[New Article🚀] We’ve published a deep dive into Probabilistic Programming and MIT’s Gen. We analyze how Gen enables "programmable inference"—automating mathematical heavy lifting while balancing expressive modeling with the performance of hand-tuned algorithms.

✧･ﾟ #GauDev Advent Calendar 2025｜DAY22✏️ ･ﾟ✧ プロダクトエンジニアの @strawberry4062 がReact Native のリッチエディタ検討過程と実装を紹介しました📱 --- React Native でリッチエディタどうする？Lexical WebView 実装とカスタムノードの流用という選択肢｜sho zenn.dev/shoo/articles/f0e68…

> ”Cookieを使ってログインセッションを保持する”しくみ、あれが一般的に認証って言われてるせいじゃないかと思ったりします。 > こいつ、OAuthと同じで、途中で認証もしてるけど、全体で見ると認可のしくみじゃねーか的な なるほどなー腹落ちした ritou.hatenablog.com/entry/2…

🎄Gaudiy Advent Calendar 2025 DAY20🎄 ホストクラブとスタートアップの組織課題構造が類似している、と感じた @hassey_11 が、独自の目線で組織の要点を考察したnoteです。ご一読いただくと、いつもと違う角度から組織を眺められると思います。 #Gaudiyアドカレ2025 note.com/hasssey_11/n/n8e59a…

✧･ﾟ #GauDev Advent Calendar 2025｜DAY20🔖 ･ﾟ✧ エンジニアの ryio1010によるClaude Code Plugin活用事例です⚽️チーム単位で自動的にコード品質を保つ仕組みは広く参考になりそうです✍ --- Claude Code PluginでClaudeでの開発をポータブルな共有知にする｜ryio1010 zenn.dev/gaudiy_blog/article…

✧･ﾟ #GauDev Advent Calendar 2025｜DAY19📹 ･ﾟ✧ エンジニアの @AndooBomber が、RealtimeKitの使い方をデモ付きで紹介しました🐻現在のBeta版はCloudflare Dashboardから試せます🙆 --- Go Reactで Cloudflare RealtimeKit のビデオ通話アプリを作る｜andoobomber zenn.dev/gaudiy_blog/article…

✧･ﾟ #GauDev Advent Calendar 2025｜DAY18💨 ･ﾟ✧ エンジニアのYutaroが、マルチクラウド構成におけるリアルタイム分析用データパイプラインの基礎設計について綴りました✍️ --- Aurora for MySQL を GCP に準リアルタイムで同期する｜Yutaro zenn.dev/gaudiy_blog/article…

記事を書きました zenn.dev/gaudiy_blog/article…

✧･ﾟ #GauDev Advent Calendar 2025｜DAY17👻 ･ﾟ✧ 棋士もといエンジニアの @rail44 が課題感を持って個人開発したAIエージェントの紹介と所感を語ります🎯 --- LSPを喋るAIエージェントで、定型コード生成を少し楽にしたかった｜rail44 zenn.dev/gaudiy_blog/article…

これ勉強会で聞いたけど、2025年の流行り！！って感じで面白かった。。。！

✧･ﾟ #GauDev Advent Calendar 2025｜DAY16❄️･ﾟ✧ BC Eng.Yamashitaが暗号通貨市場とStory Protocolの戦略について分析しました🔍 -- 2025年の市況でうまくいったトークンプロジェクトはなにをしていたのか？― IP Strategy にみる‘越境的トークン財務’の構造by Gaudiy Lab medium.com/gaudiy-web3-lab-j…

🎄Gaudiy Advent Calendar 2025 DAY13🎄 なぜこんなにも仕事をしてしまうのか。仕事が楽しいのか。 ワークイズライフなタイプのエンジニア、 @sho0910K が、自分の分析にトライした記事です。ぜひご一読ください。 #Gaudiyアドカレ2025 note.com/strawberry4062/n/n3…