Alex G. ∎

I just hit rank 950 in the #XionExpedition missions on @bonus_block - come join me and let’s climb the ranks together! xion.bonusblock.io/?r=QQX2HZpk

Verifying my Twitter account for my #GalxeID gid:tuAHMHJtZbpG82EvyTxXzb @Galxe galxe.com/id

I'm starting to explore the #XionExpedition missions on @bonus_block - come join me and let’s climb the ranks together! xion.bonusblock.io/?r=QQX2HZpk

I just joined @PostTechSoFi to trade profiles & posts and earn $ETH! 🚀 My codes: 1️⃣ pt-1pexxhnnip 2️⃣ pt-rjohxwo1mw 3️⃣ pt-7m273z9zn4 Check out post.tech and sign up with me today! #PostTech #link425113

I'm helping test @friendtech, the marketplace for your friends on Base 🐰 Get the app and search for my Twitter username to be an early holder of my keys 🤗

We are looking for a VP of Product at @the_matter_labs. Help us build @zksync and bring mass adoption to Ethereum! ➡️ jobs.eu.lever.co/matterlabs/fdf… We’re searching for an visionary technical product leader who will drive our product strategy. Here are some interesting facts about the role: 👇 1) Mission comes first: advancing personal freedom for all. What we’re building is neither a company nor a commercial product – it's a credibly neutral tech and network, owned and governed by the community. Our goal is to create a protocol that turns Ethereum into the limitless Internet of Value. Your alignment with our mission and culture is critical. Please read: ▫️ The ZK Credo: x.com/zksync/status/… ▫️ Matter Labs Team Handbook: notion.so/Matter-Labs-Te… 2) Your job? Craft a product-shipping machine. We want Matter Labs to become the world’s most impactful blockchain technology company. Your job will be to bring in and maintain product and engineering best practices within the team to create a machine that rapidly ships delightful code. 3) You will be working closely with me and the leadership team. At Matter Labs, you’ll enjoy both freedom and ownership. We're looking for someone who can guide us, not the other way around. 4) We are what Peter Thiel calls “definite optimists”. We have a precise vision of the revolutionary future we want to build, supported by a clear technical roadmap, a brilliant team, and a runway long enough to make it happen. 5) We’re a lean and nimble team. We move fast. Embracing Ethereum’s philosophy of subtraction, we’re capping our core team size at 150 people. We want to focus on solving one problem – hyperscaling Ethereum – and do it exceptionally well. Apply below with one click. We’ll respond to every application. jobs.eu.lever.co/matterlabs/fdf…

22 years since 9/11; what did we get? TIPs TSA DHS Real ID TALON NSEERS Black Sites No Fly Lists PATRIOT Act Domestic Spying Militarized Police Proclamation 7463 Free Speech Zones Weakening of FOIA Indefinite Detention Civil Asset Forfeiture Trillions spent on war Military Tribunals Act Warrantless Wiretaps Enhanced Interrogation (torture) Constitution-free zone 100 miles inland of the border, covering 66% of population. Some of you have never known anything different, and that's the dystopian future the government wants. Once those who remember the Before Times have passed, it's even less likely for the citizens to push back.

Zooko doesn't follow me and didn't tag me, so I have to respond via QT instead of reply, here goes: 1. If there is evidence of onchain crime, it makes obvious sense to provably dissociate from it 2. privacy pools still works in shielded pools 3. Zcash "works" full story 🧵👇

Some insight into life on the team @zksync, from @vladbochok1 !

Developers: Earlier today, we completed the Mainnet upgrade for block.timestamp, block.number, and blockhash. This important change allows protocols to leverage faster updates to block info and brings consistency to on-chain & RPC data. Follow @zkSyncDevs to stay up-to-date ⬇️

Gm, @binance!

Great to see this! Welcome to the open-source fam ♥️

I am in favour of this. My feeling is that the name "Data Availability" has caused confusion and "Data Publishing" is clearer. Still open to better names but so far DP seems most descriptive.

What problem does this privacy protocol solve? Building an ethos-compatible privacy protocol that actually works, because it's politically much harder to ban. What does ethos-compatible mean? 1) Compliance is voluntary. Every user decides for themselves what they want to comply with. 2) No transaction data is revealed even if a user decides to comply with their local authorities. How to accomplish this? By understanding legit concerns of the regulators (fighting crime) and actually addressing them in a way that is strongly legally defensible. How not to accomplish this? 1) By completely ignoring the regulators and/or going to jail. 2) By doing nothing but lamenting. But Tornado Cash had a compliance tool? Not really. 1) It wasn't implemented at a protocol layer in a way that would enable regulated entities (e.g. exchanges) recognize certain incoming transactions as "clean". The majority of funds in the TC were provably of illegal origin. This together makes the legal defence against the ban very hard. 2) Even if it was defensible, whoever wanted to comply had to reveal transaction details, which defeated the purpose of the protocol.

Yes! Tornado: clean + dirty money = dirty money. Therefore, DOJ blacklisted the entire TC contract as "dirty". Here, clean money is separated from the dirty money. It's very close to "clean" and "dirty" addresses on Ethereum itself. TC's compliance tool could not do that, because you were only able to reveal the immediate source address, not prove the clean provenance of the incoming funds.

This scheme is genuis. Since the compliance is voluntary, it works for any jurisdiction.

1/ New privacy paper with @VitalikButerin, Jacob Illum (@chainalysis), @mat_nadler, @fschaer! papers.ssrn.com/sol3/papers.cf… We explored new compliance opportunities made possible by privacypools.com, where users can provably dissociate from illicit funds. story below 🧵👇

"How do we incorporate multiple chains in an architecture where they can still seamlessly, trustlessly, and capital efficiently communicate with each other? This is where the hyperchain vision comes in." More on the hyperchain vision from @gluk64 ⬇️ 🧠

Yes, I mentioned @VitalikButerin's post about overloading L1 consensus in my write-up, and I am openly challenging it. BTW, my proposal is inspired by another of his ideas – about the concave vs. convex worldviews: hackernoon.com/is-your-perspe… Taking a 100% distanced approach to governance is convex. I plead for a concave policy of minimal necessary intervention: pre-agreeing on soft-fork as a non-intrusive veto mechanism for governance decisions; only in extreme emergency cases, and only for protocols with systematic significance. Without it, we're doomed to choose between two extremes: 1) Code is law, bug = death. 2) Code doesn't matter, because there exists a finite multisig that can unilaterally override any decision. Everything is ultimately centralized. Neither choice can serve as the foundation of the decentralized Internet of Value. Yes, you can take one protocol (e.g. zkEVM) and enshrine it into L1. But that won't solve our fundamental problem because you can't enshrine everything. A great example is the Parity multisig bug. I doubt that anyone would use a wallet with another multisig having the power to change code. But wouldn't Ethereum as a whole be much better off if Parity used a standard (maybe enshried?) upgradability library which would allow a soft-fork to fix the bug? There would be much less contention about a soft fork in that specific case, given how many people were affected. How much backwind are we getting from the inability of users and institutions to rely on completely immutable code?