cass

Sr Web Dev (6yrs: TS, Node, React, Rust, C#).
locked in - dm for inquries if u need TEK built.

[vitalik.eth @VitalikButerin]

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.

[cass @0xCassandraX]

The algebra is sound, if you view the ecosystem purely as a distribution layer, not a security layer.

The $5M issuance to stakers is an internal transfer, not sustainable revenue. If the actual fee-generating volume is only $500k, then the security of the chain is being subsidized by temporary token supply dilution.

[cass @0xCassandraX]

Coming from a background in Web2 distributed consensus and high-availability architecture, the Web3 interpretation of 'community building' is fascinating, if you're willing to ignore the code.

It feels less like Building and more like the synchronized execution of industrial-scale copy-paste operations.
99% of current memecoins are generated from a few highly recycled OpenZeppelin contract templates and standard initialization scripts.

You’re not getting new code, you’re getting a minor parameter change and a fresh narrative polish.

I’m a technical newcomer with serious ambition, not looking to build another polished copy of a copy.

I want to deploy resilient, unique logic.
In most projects, the exit liquidity is the only part of the system that’s truly unique

[cass @0xCassandraX]

@RoarWeb3 CcxrwyTGnpwDtvysTZV3typfVDgR5Yf1RGtsmFQp9Zvw

[cass @0xCassandraX]

@boringcompany Pun intended, but 3,750 lb blocks with millimeter precision is still cleaner than 99% of the code deployed on Solana today

[cass @0xCassandraX]

Finally someone says it.

Persistent pseudonymity is a myth if your adversary has a basic LLM and access to your request timings.
We learned this in Web2 years ago.

ZK API usage credits for spam prevention are the only way mixnets survive without getting blackholed like Tor exit nodes.

Keep pushing the frontier, V.

[cass @0xCassandraX]

Everyone is wondering why $PEPEAI just dumped 90% in two minutes.
It wasn’t a random sell-off; it was a coordinated bundle.

The deployer funded 18 fresh wallets via FixedFloat exactly 3 hours before launch. They sniped 62% of the supply in the exact same block the liquidity was added.

Here is the transaction map. Stop letting these teams use you as exit liquidity. 📉🔍