Sunrise is Solana’s asset gateway, incubated by Wormhole Labs. Canonical issuance, deep liquidity, and full ecosystem distribution from day one. Crypto assets, tokenized stocks, commodities, and RWAs. No fragmented liquidity. No competing wrapped versions. 👇

I updated my 2023 roadmap diagram to overlay where the items that were there sit in the current Strawmap ( ). 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 ) * 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.

New issue of Burn Notice #5# 🔥 Two disclosure programs went dark in the last week. Zcash Community Grants closed its vulnerability bounty program, and THORChain is in an open dispute with a researcher over a retired one, both pointing at the volume of AI-generated reports. I know exactly what that volume does to a program, the days lost reading plausible nonsense to find the one real report underneath. The instinct to close the program is something I could understand but is never a valid response. The cost of finding a bug in old, forgotten code is dropping fast, because decompilation is good now and models are cheap, and the paid channel that routes an honest finding back to you is the part getting cut at the same moment. This was the week Aztec Connect lost $2.19M on a contract nobody could pause and Verus fell to a bridge-failure class that Wormhole and Nomad already paid for in 2022. You can read more about what happened in the last week of crypto security in the newest issue of Burn Notice down below.

lowercase snarks Words like laser, scuba, radar began uppercase. LASER — Light Amplification by Stimulated Emission of Radiation SCUBA — Self-Contained Underwater Breathing Apparatus RADAR — RAdio Detection And Ranging When a technology matures and becomes reliable, trusted, commoditised, it earns the lowercase. Lean Ethereum is a bet on snarks, not Succinct Non-interactive ARguments of Knowledge. Post-quantum security. Provable soundness. End-to-end formal verification. Deep cryptanalysis. Real-time proving. zkVM programmability. Simplicity and elegance. All essential for the lowercase. All inevitable. Ethereum L1 has 10y uptime and $1T secured with hashes and signatures, our cryptographic workhorses. I believe in 100y uptime and $1Q secured with snarks, our cryptographic jet engines. * L1 scale — 10K TPS gigagas scale with real-time zkEVMs * L1 security — post-quantum security with snarked signatures * L1 privacy — Zcash-grade stealth with wormholes (eg EIP-7503) Shipping snarks is a cryptographic Manhattan Project, one the EF is investing tens of millions into: * verified-zkevm[.]org — formal verification * poseidon-initiative[.]info — deep cryptanalysis * ethproofs[.]org — real-time proving * proximityprize[.]org — provable soundness * zkevm.ethereum[.]foundation — enshrinement * pse[.]dev — privacy Step by step, the EF is evolving into a snark-first org: * cryptography team — driving soundness and cryptanalysis * snarkification team — driving formal verification * zkEVM team — driving protocol integration * Ethproofs team — driving real-time proving * PSE team — driving privacy * PQ consensus team — soon™ Believe in something magical. Believe in lowercase snarks.