sudo rm -rf --no-preserve-root / pfp

sudo rm -rf --no-preserve-root /

@pcaversaccio

164 Following
3185 Followers
sudo rm -rf --no-preserve-root / pfp
9 replies
7 recasts
64 reactions
sudo rm -rf --no-preserve-root / pfp
4 replies
1 recast
27 reactions
sudo rm -rf --no-preserve-root / pfp
3 replies
2 recasts
28 reactions
sudo rm -rf --no-preserve-root / pfp
1/ time for a quick vibes check on where our industry's at security-wise; well, folks, guess what, 95% of last months' SEAL 911 tickets were the same shitshows on repeat: folks running sketchy code some rando DMed them (stop cloning & running GH repos you got from some random dude who asks for your "help"), hopping on Zoom calls where scammers walk them through (effectively) self-pwning (dude, believe me you don't need to patch your zoom or google meet) their own machines, teams getting nuked because they thought hiring bargain-bin devs from North Korea was a great idea, or some skiddies calling up victims pretending to be Coinbase support (always Coinbase, like 90% of the time and the rest is Ledger) and walking off with their funds. On top of that, there's the usual: someone falling in love with a random Tinder match and getting rinsed by a textbook Sha Zhu Pan play, and of course, the ever-reliable dev who commits their .env file with private keys straight to GitHub, NPM, etc.
2 replies
1 recast
22 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
2 recasts
18 reactions
sudo rm -rf --no-preserve-root / pfp
5 replies
1 recast
24 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
1 recast
23 reactions
sudo rm -rf --no-preserve-root / pfp
7 replies
7 recasts
53 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
0 recast
26 reactions
sudo rm -rf --no-preserve-root / pfp
"Make Ethereum Cypherpunk Again" isn't simply a slogan for me β€” it's a statement of intent. This isn't branding. It's resistance. This isn't about playing nice. It's about reclaiming Ethereum's soul! Look it's very simple: Ethereum must provide privacy _unconditionally_. Today, it operates in a partial, opt-in model, forcing users to jump through hoops just to conceal their financial lives. That's not sovereignty β€” it's submission. Enough compromises. We need privacy by default. Over the past weeks, I've written a potential path forward β€” a vision for Ethereum as a maximally private, self-sovereign financial system. Read it. Challenge it. Improve it. Let's co-create it. Make Ethereum Cypherpunk Again. https://hackmd.io/@pcaversaccio/ethereum-privacy-the-road-to-self-sovereignty
2 replies
4 recasts
47 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
2 recasts
8 reactions
sudo rm -rf --no-preserve-root / pfp
Dropping some thoughts as this concerns me a lot lately: - What happens when a DPRK-backed persona slips into Ledger, Trezor, MetaMask, etc.? - What happens when client teams get compromised from within, turning trusted core devs into silent attack vectors? - What happens if the Kim boys start tampering with the cryptographic libraries we all rely on? (we don't know if this already happened btw...) So far, the attacks have targeted individual projects. The next phase? My guess is a full-scale takeover of the infra that holds our ecosystem together. Look, it's pretty simple: the threat model isn't just shiftingβ€”it's escalating. Every move you make without paranoia is an opening for state-sponsored actors to dig in deeper. If you're not fucking questioning everything, you're already playing their game. This industry's long-term survival depends on its foundational pillars operating in a constant state of paranoia. Like it or not.
1 reply
2 recasts
12 reactions
sudo rm -rf --no-preserve-root / pfp
EOF: When Complexity Outweighs Necessity https://hackmd.io/@pcaversaccio/eof-when-complexity-outweighs-necessity A lot of time and energy went into this new deep dive on EOF. We break down its supposed benefits and argue they're more "nice-to-haves" than essential upgrades. Instead of adding complexity, we highlight cleaner, less disruptive solutions that achieve the same goals. EOF's objectives are solidβ€”but there's a smarter way to get there. I would like to highlight that the authors and contributors of this post represent the full EVM stackβ€”from VM and formal specification maintainers to compiler engineers, application developers, and library creators. Please reflect on this guys. If you got feedback, let us know here: https://ethereum-magicians.org/t/ethereum-is-turning-into-a-labyrinth-of-unnecessary-complexity-with-eof-lets-reconsider-eof/23136 https://x.com/pcaversaccio/status/1900200732000759892
2 replies
12 recasts
65 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
0 recast
13 reactions
sudo rm -rf --no-preserve-root / pfp
3 replies
10 recasts
60 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
1 recast
9 reactions
sudo rm -rf --no-preserve-root / pfp
People keep asking me since days how to secure their systems and what the best strategy is. I will be very honest with you all as I'm always. If you want real security (and there will be never 100% security), it's not (just) about toolsβ€”it's about fucking mindset. At least 80% of it is pure paranoia. You and your team (can be a small DeFi project, can be a large CEX, ...) need to be paranoid as fuck. Drill it into them. Make it second nature. That's how you cut down risk, big time. The human factor is always the weakest linkβ€”no tech can _fully_ fix human fuck-ups. Sure, we'll kill blind signing, we'll upgrade our tools, but people will always be the problem. The only way to fix that? Train them to be fucking paranoid. There are no fucking shortcuts. If you have 900 employees, it's the leader's job to make sure all 900 are paranoid as fuck. You'll say that doesn't scale? Maybe notβ€”but if u don't do it, you're effectively gambling with everything. And when shit goes wrong, the price u pay will be brutal.
2 replies
0 recast
10 reactions
sudo rm -rf --no-preserve-root / pfp
3 replies
9 recasts
63 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
10 recasts
29 reactions
sudo rm -rf --no-preserve-root / pfp
1 reply
1 recast
18 reactions