sudo rm -rf --no-preserve-root / (pcaversaccio)

1/ A huge chunk of what Ethereum (mostly - but not only - application layer) is building today is propped up by excuses & massive, hand-waved trust assumptions and VC-driven narrative capture. We need centralised L2s because of "training wheels". We need upgradeable proxies controlled by a few keys held by some foundation or multisig cabal. We need trusted setups, trusted sequencers, trusted committees, trusted councils, trusted whatever the fuck is fashionable this year. We are told we cannot have unconditional & L1-enshrined privacy because regulators might get nervous or throw a tantrum. It is _always_ later. Always soon. Always after we ask for permission from people who fundamentally hate this space. This path turns Ethereum into the fucking soy boy of crypto. Safe. Compliant. Apologetic. Bent over, hoping institutions don't hit it too hard while pretending this is all part of some grand master plan. Guys, this is not how you fucking change the world!

• 1 reply
• 4 recasts
• 19 reactions

the only real _long-term_ market fit IMHO for Ethereum is private & self-sovereign applications. Everything else, including _most_ (not all, to be clear) of DeFi is fundamentally short-term, driven (mostly) by speculation & attracts folks who come fast and leave fast as well however (since rekt many times). Look, as the world moves further into mass surveillance across finance (and nobody can deny this), your identity & whatever you do on the internet, the value of privacy becomes more urgent and more critical. Privacy is the product-market-fit of Ethereum long term.

• 1 reply
• 1 recast
• 17 reactions

so, hmm, we rely on firmware we can't inspect, compilers we don't build, closed-source LLMs, proprietary enclaves, remote updates etc. Each of these layers is a target and more will join in the coming years/decades. In a world this complex (and guys this complexity is our own making!), how do we even verify that we're safe? If you ask me, verification has never been more critical or more impossible.

• 3 replies
• 2 recasts
• 28 reactions

In light of the recent incident at Radiant and the clear challenges of verifying multisig transactions on a Ledger device, I've built a simple Bash script designed to simplify the process. This script generates the domain, message, and Safe transaction hashes, making it easier to cross-check them with the values displayed on your Ledger hardware wallet. All you need to provide are the network name, multisig address, and transaction nonce. It supports all Safe networks, and I hope it will serve as a useful tool to temporarily ease the burden of blind signing verification for multisig transactions. Eventually, make sure to check out the trust assumptions laid out in the README for this script. https://github.com/pcaversaccio/safe-tx-hashes-util

• 17 replies
• 45 recasts
• 82 reactions

We've fucking lost it. Nobody in their right mind wants over 50 rollups and endless layers that take days to bridge back. What the world wants is one goddamn chain that just works, and that should be Ethereum. No one with a shred of sanity wants to switch networks in M***Mask. No one wants the headache of adding a token manually on another chain because the contract address isn't the same. Bridging is a pain in the ass. What people want is to transact value simply and directly, without all this convoluted bullshit!

• 23 replies
• 18 recasts
• 102 reactions

This morning I've been reviewing our last months' SEAL 911 tickets. Guys, it's clear that soon (probably sooner than you think) a large portion of our ecosystem will be running on compromised devices. I mean, man, infostealers are probably the _biggest_ ecosystem problem right now. However, and that's what I want to address here, is that OS design choices like weak data compartmentalisation & permissive default trust models are the _major enablers_, especially on macOS and Windows. Please remember: these OSes weren't built with the strict sandboxing, strong application isolation, or zero-trust principles needed to defend against these today's threats! I understand that shifting most of the space to something like QubesOS isn't realistic, but we must start prioritising security-first OS choices in our ecosystem, not just UX. Honestly, fancy features won't stop your device from being compromised.

• 3 replies
• 7 recasts
• 64 reactions

Vitalik is back writing Vyper code - what a beautiful day https://github.com/ethereum/research/blob/master/sublinear_staking/code.vy

• 3 replies
• 19 recasts
• 70 reactions