I updated my 2023 roadmap diagram to overlay where the items that were there sit in the current Strawmap ( https://t.co/I35mrXutP2 ).
In general, a lot of overlap, but:
* Some things got reshuffled in order (eg. quantum safety up-prioritized)
* Some things deprioritized (eg. VDFs; many EVM improvements)
* Some things replaced with superior constructions (eg. Verkle -> unified BT -> PBT; state expiry -> new state types)
What's most striking, however, is that some completely new things are in the strawmap that are NOT in this diagram, because they were not in the 2023 roadmap at all. These reflect changing priorities.
Notably:
* First-class attention to strong privacy. This covers: keyed nonces and recent roots, aspects of FOCIL, lean privacy pool & wormholes
* Aggressive scaling in the context of post-quantum. This covers: leanSPHINCS signatures and aggregation, zkzk frames (see https://t.co/ibrOpMxMfO )
* Lean-ification of the spec, to assist in formal verification (full FV of everything is only possible because of modern AI)
* Blob and gas futures (this idea just didn't exist back in 2023)
* Native rollups (SNARKs were nowhere near mature enough to even consider this back in 2023)
* A more open design space for the "future of the EVM". zkzk frames already implies that the protocol will expose to users some ISA that's not the EVM - current leading candidates are leanISA and RISC-V. These ISAs are more simple, modern and efficient than the EVM. Once they're there, why not expose them to developers everywhere? (And then, why not turn the EVM into being an IR on top of that ISA, instead of an enshrined feature massively complicating the base protocol?) Though much of the deeper exploration here is too early even for the strawmap.
* New state types are not just a replacement for expiry, they're a fundamentally different paradigm to how Ethereum does scaling
A common theme in scaling, found in both state types and zkzk frames (both new ideas), is that instead of trying to maximally scale ALL ethereum activity, we try to create specialized mechanisms that have more restrictive properties that make them more scaling-friendly, while supporting the heaviest loads incurred by users and applications today (eg. token transfers, swaps) and tomorrow (eg. privacy protocols).
The other common theme is treating STARKs and AI-accelerated FV as first-class objects, that we are okay betting the technical future of Ethereum on. There are recursive STARKs in many layers of the protocol, one particular primitive (the "aggregate to union verified dependencies" primitive) is expected to be used in *three* places in the protocol: EL, CL and DL. This can only be safe with formal verification, which is itself only feasible with modern AI tools.
In general, many steps forward in maturity. And a huge amount of hard work by many dozens of Ethereum researchers and developers on all of these features.
Ethereum will be quantum-safe. Ethereum will put users' privacy first. Ethereum will be secure. Ethereum will be censorship-resistant. Ethereum will be highly performant and scalable while satisfying the above. And Ethereum will be Lean.
Asia will be a major part of Ethereum’s next phase of adoption.
Korea is one of the markets where we see strong potential, and that is why we’re excited to work with @0xundefined_.
They bring deep local market knowledge and relationships across Korea’s financial and digital asset ecosystem. We bring Ethereum-native technical expertise across privacy, tokenization, and financial infrastructure.
Together, we’ll work with Korean institutions on education, workshops, technical frameworks, use cases, and the path from early exploration to PoCs and production systems on Ethereum.
Excited to build more across Asia, starting with Korea. 🇰🇷
ENS complaints are at an all-time high.
Most days barely anyone talks about it anymore. A lot of people have simply lost hope.
Meanwhile, XNS is building what ENS should have been: permanent, Rent free.
@xnsname
Worked with a very cool group of people to create an entirely new experience in world building. Excited for you to play around with it and raise the dead with us.
You can create your own namespace with XNS, and As the owner you’ll earn 10% of all registration fees generated by that namespace..
Make sure it doesn't already exist.
You can check the current list here:
https://t.co/PNXYNLKZGI