Zhe (@linuxcity) header
Zhe (@linuxcity) profile picture

Co-Founder @bitdynamics_me, Solo ETH staker. My staking goal: running 1000 ETH validators solo for others.

Earth
Joined July 2007
Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)Photo by Zhe (@linuxcity)
Zhe retweeted
Not endorsing the conclusions here, but this is worth a read. The financial and institutional connections deserve scrutiny.
87
398
26
3,551
247,707
Jensen Huang should have spent more time studying @nntaleb. Trying to maintain a reputation as a family man and a wholesome guy is what made him fragile. If he instead went down the Elon Musk route and cared nothing for his reputation, he would have been antifragile in this situation. Now he might lose half his shares, his job, and his reputation for acting like the rockstar he was not supposed to be. Elon’s reputation not only survives attacks, criticism and controversy - it becomes stronger by it. Elon is antifragile. Jensen Huang, however, decided to brand himself as a good guy, but only played a part. That’s why he became fragile, and will most likely be asked to stand down.
156
552
115
5,854
354,176
Zhe retweeted
This is why GPUs cost $6,000
607
3,223
590
21,751
2,729,784
Plants vs. Zombies got an AI movie before GTA 6
🤖 Made with AI
591
8,177
523
67,787
2,956,715
🚀 #HackCanton Season 3 is OPEN Build on @CantonNetwork. 5 weeks. Online. Up to $50K in cash + credits. • Sep 17 — Opening • Sep 18–Oct 9 — Build • Oct 9 — Submission • Oct 10 — Closing • Oct 10–18 — Judging • Oct 19 — Finalists • Oct 21 — Grand Final Solo or team. Ready to build? Register now 👇 appsfactory.cc/hackathons
6
5
1
52
1,462
A couple of trends I'm seeing across the industry. Which ones are you observing, that I missed?
217
171
43
2,581
362,140
Zhe retweeted
dude GPT-6 Astra is some kind of turbo-AGI machine god for 3D games. It one-shot this in 45 minutes for hardly a couple % of my quota. I figured out how to get great graphics out of it. The trick is image gen. I'll share the process below.
495
1,252
309
19,128
3,058,782
If you bought $MU everyday at market close and sold at market open, your return would be 138,330,342% If you bought $MU everyday at market open and sold at market close, your return would be -99.2% Almost all of $MU gains have come from overnight moves I am going to set up a trading agent that buys $1000 of $MU everyday right at market close and it will sell it at market open the next day This will be a fun experiment
621
697
189
12,380
3,248,050
Goodbye, Poseidon! An epic 8-year, 8-figure rabbit hole in post-quantum cryptography reaches its dream conclusion. The Ethereum Foundation is abandoning Poseidon for L1, pivoting to SHA or BLAKE. This milestone unlocks ultimate security for lean Ethereum and foreshadows a golden era of hash-based cryptography. Since 2018, the Ethereum Foundation has invested in magic cryptographic bricks, so-called "SNARK-friendly hashes". In 2019, Poseidon was born. It held strong and became the dominant SNARK-friendly hash, securing billions via zkrollups and zkVMs. In a stunning reversal, breakthrough SNARK designs show that SNARK-friendly hashes aren't necessary after all. Off-the-shelf traditional hash functions like SHA2 and BLAKE2s can now match Poseidon in a SNARK. In hindsight the key was not SNARK-friendly hashes, but hash-friendly SNARKs. The secret is doing maths over the smallest prime number: 2. So-called "binary fields" natively speak the language of bits, aligning with the boolean operations inside traditional hashes. This is a stark departure from "prime fields", where awkward large-prime arithmetic makes bit manipulation painfully expensive. We're talking sci-fi cryptography. 1M traditional hash calls proven per second, on a laptop. Just 100x overhead vs native CPU boolean compute. Nobody predicted such performance, not even the handful of binary-field visionaries. Hat tip to the research geniuses: Jim and Ben with Binius in 2023; Ron, Benedikt and William with Flock in June. With SHA2, the lean aesthetic of minimal assumptions reaches its climax. The EF's principled stance on pure hash-based cryptography has aged like fine wine. We now enjoy foundations the world can trust for decades and centuries, foundations worthy of the dream of an internet of value. Speed of deployment is a secondary win. There's no longer a need to wait years for Poseidon cryptanalysis to bake. Emile and Thomas from the EF post-quantum team are moving at breakneck speed with binary fields. The strawmap now points to a production-grade leanVM in 2027, with CL, DL, EL deployments in 2028. As AI becomes exceptional at cryptanalysis, the contrarian bet to avoid riskier structures like lattices and isogenies is visibly paying off. The past weeks have been brutal. Lattice-based "HAWK" and isogeny-based "SQIsign", both signature schemes in NIST's Round 3, have suffered blows. Sources I trust say more blood is coming. On AI, the open autoresearch trend kicked off by ECDSA[.]fail is spreading fast, with amazing outcomes from zk[.]golf and SNARK[.]fast. Days ago SNARK[.]fast crossed 1.8M BLAKE3/sec proven on an M3 Max. Stay tuned for fresh autoresearch challenges dropping tomorrow. Also tomorrow: Ethproofs call #10, dedicated to binary fields. Possibly the most noteworthy Ethproofs call yet. Experts leading the charge will present the future of hash-based SNARKs at 2pm UTC. What an incredible time to be alive. To witness history, DM me for a calendar invite :) Today I can confidently claim that hash-based cryptography has won out for blockchain post-quantum signatures. SNARK succinctness compresses arbitrarily many signatures into one small proof per block. SNARK flexibility yields k-of-n threshold signatures, complex multisigs, and more. Ultimate security. Uncompromising performance. Full programmability. Believe in something. Believe in hashes.
162
356
149
2,048
484,267
For years there has been a narrative that "bitcoin-only" products and services are inherently more secure than multi-coin counterparts due to having a smaller attack surface. I hope it's clear now that you can't judge a product's security posture upon that single point.
48
43
7
599
49,077
Linus Torvalds: “AI is tool and will be used in Linux kernel development, anyone who’s is not happy about it can fork Linux kernel” 🤣
97
461
117
3,542
244,812
Zhe retweeted
🚨 Active supply chain attack on AsyncAPI. Five malicious @​asyncapi packages were published to npm today, shipped through the project's own GitHub Actions trusted publishing pipeline after an attacker poisoned a commit on the next branch. Affected versions: @asyncapi/[email protected] @asyncapi/[email protected] @asyncapi/[email protected] @asyncapi/[email protected] @asyncapi/[email protected] The first three were published within a six-second window at 07:10 UTC. AsyncAPI tooling runs on developer machines and CI runners, so the implant executes directly in build environments. Socket AI Scanner flagged all five releases as confirmed malware. This is a multi-stage botnet loader: • On load, an obfuscated implant spawns a detached, hidden Node.js child process • The child downloads an 8.25 MB encrypted payload (sync.js) from IPFS into a fake "NodeJS" data directory on Windows, macOS, or Linux • HKDF-SHA256 key derivation and AES-256-GCM decryption unpack the final stage • That final stage is Miasma, a 3.09 MB command framework with REST-based C2 plus fallback channels over Nostr, IPFS, Ethereum RPC, and BitTorrent DHT • 12 command types, including ShellExec, file get/put/delete, payload updates, and self-destruct • Persists on Linux via a systemd user service (miasma-monitor.service) The campaign config is labeled "miasma-train-p1" and contains dormant modules for PyPI, RubyGems, and Cargo. npm appears to be phase one. If you installed any affected version, treat the host as potentially compromised. Check for detached Node.js processes with ignored stdio, connections to 85[.]137[.]53[.]71, fake NodeJS directories, and the miasma-monitor service. Pin to known-good versions and audit lockfiles before your next install. Full analysis: socket.dev/blog/asyncapi-sup… Developing story...
2
12
37
60,899
What Muslims did to Yazidis in Iraq was so much worse than what is happening in Gaza. Elderly women buried alive for being too old to be sex slaves. Mothers forced to eat their own babies. Young girls locked in iron cages and burned to death. Yet not a single protest! Everyone who’s now protesting for Gaza was completely silent. Why is that? Unlike the people of Gaza, the Yazidis never started a war!
650
8,269
311
19,096
220,585
How Chat Control Passed
172
1,333
96
4,866
187,453
We're opening the waitlist for our Monetization Gateway, which will allow you to charge for any web page, dataset, API, or MCP tool behind Cloudflare. The charges will settle in stablecoins over the x402 open protocol. cfl.re/4eUFdt6
447
1,508
1,085
12,541
6,104,539
Zhe retweeted
the ENS DAO drama - neutral rundown 🧵 one of ethereum's best-known products is having a rough governance month. here's what happened, and who's on each side. 👇 (i wrote this for myself, so i could stoicly understand all sides before considering taking a position myself. im sharing it for others who also wish to be informed before taking a side.) the setup: - the ENS DAO governs a treasury reported between ~$350M and ~$500M. - the ENS token's circulating market cap is only ~$168M, and ENS is down ~95% from its 2021 peak. - so the money the token controls is worth multiples of all circulating tokens. - that ratio creates a "residual floating value takeover" risk - someone could in principle buy cheap tokens to reach the treasury. (that risk is also the whole justification for having a Security Council.) the trigger: june 19 - Katherine Wu (katherine.eth), COO of ENS Labs, posted a temp check to move day-to-day treasury ops, the ENS token holdings, and the Karpatkey-managed Endowment to a 5-seat Foundation board. - token holders keep on-chain authority over upgrades, pricing, and root key. the delegation move : june 22 - ENS co-founder Nick Johnson (nick.eth) self-delegated ~3.1–3.26M ENS tokens to himself. - that's only ~3% of total supply - but because governance turnout is low, it's ~50% of active voting power - in Lefteris Karapetsas's words: he "delegated ~50% of the voting supply to himself, essentially becoming the DAO." - for the moment, nick.eth could pass or block almost anything. the security council fight: - the DAO's Security Council - a 4-of-8 multisig that can veto malicious proposals - was set to expire July 24, and needed a renewal vote. - nick.eth abstained on the off-chain Snapshot round, then on the binding on-chain vote (concluded june 30) voted his full stack against renewal, sinking it single-handedly. - his stated reason: the current council lacks adequate checks and he wouldn't renew it unreformed. - critics saw something else: with no renewed council, there'd be no body able to veto the Foundation treasury transfer he supports. - hours later, a successor council was proposed: 8 members, veto threshold raised from 4-of-8 to 5-of-8, and members must sign formal contracts with the ENS Foundation. - nick.eth backs it and self-nominated. supporters call it tighter/legally accountable; critics call it a weaker check that's harder to trigger and now contractually bound to the Foundation. the sides side 1 - "governance attack / treasury capture": - Lefteris Karapetsas (@LefterisJP, Rotki founder, Security Council member): "there is no DAO anymore… I am just sad and disappointed." later: the DAO is "dead." - Brantly Millegan (@BrantlyMillegan, Security Council member): "the equivalent of treasury capture by ENS Labs"; pledged to veto if it passes on Labs-aligned votes alone. - netto.eth (@alextnetto, @anticapture lead steward): board is conflicted - "the downfall of ENS." - James (@blockchainjames Fire Eyes): limiting the council's veto strictly to constitutional violations guts the community's main defense against treasury extraction. - Gabriel Shapiro (@lex_node): characterizes it as part of a broader pattern of Ethereum DAOs being quietly "privatized" into foundations while on-chain mechanics stay nominally intact. - Christoph Jentzsch (@ChrJentzsch, wrote the 2016 "The DAO" code): the DAO should wind down and revoke its own upgrade authority. - Simona Pop (@sim_pop): The legitimacy test isn’t whether those exercising power have good intentions (or what they believe are good intentions). It’s whether the same actions would be considered legitimate regardless of who was exercising it! Imagine the exact same situation, the exact same actions but a different person/org doing all this. (veil of ignorance test) If that changes whether the arrangement feels acceptable then the legitimacy is borrowed from the individual. side 2 - "reasonable, even honest, restructuring": - Nick Johnson (@nicksdjohnson): token holders keep ultimate control (upgrades, pricing, root key, removing board members); he wanted council reform, not no council; notes he launched with a <6% allocation and took zero VC; says he'll only oppose council candidates who'd veto proposals that don't violate the Constitution. - Katherine Wu (@katherineykwu): it fixes an operational reality - routine treasury moves were choking on governance overhead, per the DAO's own early-2026 self-review. - Sympathetic analysts (e.g. ainvest): "a governance confession, not a crisis" - an accountable board may beat a decentralized facade that only produces gridlock,. side 3 - "the end-state of every DAO" (commentary more than camp): - aged DAOs drift to concentration, - then "fix" it by returning to the centralized structure they were meant to replace. - the proposal is the symptom doubling as the cure. the through-line everyone agrees on: - low turnout means token-voting already produced extreme concentration - one founder, ~3% of supply, ~50% of the vote. - the fight is whether the Foundation restructure is part of the cure or part of the disease. appendix: the brantly millegan subplot in 2022, Brantly Millegan held four roles in the ENS ecosystem: 1. Director of Operations at True Names Limited (TNL, the company developing ENS), 2. a director of the ENS Foundation, 3. a community-working-group steward, 4. and the single largest DAO delegate. in 2022, a 2016 tweet resurfaced with views many read as anti-LGBTQ; he declined to retract. what followed was actually three separate removals proposals (not one clean firing as is sometimes told): - Community steward: the community stewards voted him out (4 of 5 stewards voted; majority to remove) - a stewards' vote, not a DAO-wide token vote. - TNL Director of Operations: TNL terminated his contract, announced Feb 7, 2022 by Nick.eth; per ENS's own forum summary the decision "was made by Nick" (company management), not by a DAO vote. this termination presumably canceled Brantleys ENS token vest, which likely may have been significant. - ENS Foundation directorship DAO vote (EP6.1): this was the one true DAO-wide token vote - and it was contentious. Millegan's own large delegated voting power (thousands of small delegators, ~10% of active votes) actually helped shield his Foundation seat, prompting members to argue whether the token-weighted result "is not indicative of the ENS ecosystem's wishes" and to warn about "the irony of a decentralized service centralizing around the voice of one person." fast-forward back to 2022: - Millegan is now one of the loudest voices defending the DAO against Nick.eth, sitting on the Security Council ready to veto what he calls Labs' "treasury capture." - the man Nick.eth helped remove in 2022 is now the check on Nick.eth power in 2026 - and the 2022 "centralizing around one voice" warning reads very differently now that one person holds ~50% of the vote in 2026. - as of July 3rd 2026, brantley has taken his .eth off and is leaving the ENS ecosystem. why some re-litigate it: the 2026 and 2026 fights show ENS "governance" resolving high-stakes fights through concentrated power and informal pressure, with Nick.eth central to both, and cancel culture/culture wars looming ominously in the background. the counter-view: it's a category error - a values-based staff removal (governed by an employment contract at a centralized company) and a treasury-structure fight share only the word "governance" - and re-litigating brantly is old grievance riding new drama. the brantly precedent is part of why some read this as a legitimacy problem, not merely an operational one. --- DYOR. best effort attempt. not financial advice. i dont have a position, nor do i plan to take one. this is not my fight - i'm just mapping the territory. if i got something wrong, missed, or mischaracterized something @ reply it. but don't project your weird ass shit on me. Sources: Crypto Briefing, The Defiant, Cryptopolitan, ainvest, ETH Daily, Toobit, CoinAlertNews (The Block/CoinCentral), ENS DAO governance forum. Numbers vary by source: treasury ~$350M–$500M; market cap ~$168M; Johnson's stake ~3% of supply / ~50% active power / ~80% of votes cast.
27
32
5
199
17,537
In order to understand what this means you need to know that Brantly was the main reason ENS got so popular back in 2021-2022. The same people who are now stealing the $500m canceled him and fired him even after all he did for ENS. Yet he did the unthinkable and kept working on ENS until today even after having been treated the way he was. Imagine the frustration of Labs. You fire the guy, you mount a canceling campaign against him ... and yet he does not stop working on the ecosystem. What this firing and canceling did not do, Nick and Labs managed to finally achieve today. In killing ENS by capturing the DAO and stealing its treasury there is no ecosystem to build on anymore. A naming system that people don't use is worthless. Shame it has come to that. And despite all that, Brantly and the team shows integrity again here by declining the $1.2m grant from the DAO to keep building on the ecosystem. As there is no ecosystem to build on anymore. They could have just taken it and slow rugged, but no they are people of integrity. I applaud Brantly and his team for doing so. The downside that's $1.2m more for Nick and Labs to steal through their "independent" foundation ...
the .eth comes off, the end of a chapter for me I have decided to move on from ENS, given recent events and other reasons. I'm grateful for my time with ENS and I wish everyone well going forward This includes winding down @ethidorg. I and my incredible teammates are open to new opportunities, DMs are welcome. My team has been amazing! Any of them would make a great addition to your team: @0xthrpw @encrypteddegen @sat_eth @jalilwahdat @quantumly 🔥 Re our projects like @grailsmarket, @ensmarketbot, @efp, etc: Thank you to all of our users, we appreciate you! Most of these projects will sunset over the next few weeks (tho code remains open source), more information will be posted later Godspeed everyone 🤝
38
57
7
505
48,082
CL clients are now shipping this natively. Would love to bring it to the Gnosis<>Ethereum bridge ASAP and hope @ethlabs_org can play a role in bringing this to the much larger ecosystem around Ethereum. xitter.gq/abcoathup/status/20721…
.@_julianma Gnosis are up for using FCR when there are 3 CL clients supporting it. ethresear.ch/t/confirmation-… FCR FAQ says it is being actively developed (fastconfirm.it/#faq)
2
4
1
41
3,672
We are cooked. China's Alibaba just revealed Wan Streamer. AI agents can now see you, hear you, and talk back on video in real time. This is not voice mode anymore 🤯
207
449
147
3,406
506,754
One of my 4am tweets mentions nonce reuse. I was speaking casually bc I was flabbergasted by just how fucking stupid this is. And nonce reuse is historically the stupidest thing so they got crossed in my heads. I got the other one right, so I'll repeat it now: These guys rolled their own crypto so fucking hard that anyone could get your private key from public information. Cardano should stop obsessing over whether this is a Cardano hack and realize that THIS IS INSANE. Fucking up the nonces is common with ECDSA. It is NOT EdDSA/Ed25519. This shit was intentionally DESIGNED to eliminate the footguns that are common with EDCSA. It took WORK for the developers of this wallet to accomplish this. Using the standard crypto libs—which are used by all wallets in a sane universe—would NOT result in this issue. If you are building a wallet and cant get the bare minimum correct, you deserve to die a violent and bloody death. NO ONE should not expect someone who cannot even walk to be able to run, jump, skip, hop, etc. And ALL of those skills are necessary when building a wallet in this adversarial ass space. This must be the end of Emurgo/SecondFi/Yoroi. If you forgive and forget, you are sealing your own fate and being willfully fucking retarded.
SecondFi security issue wasn't a nonce reuse, or a weak key, but a public nonce used to sign keys. The Ed25519 standard defines how you are supposed to generate nonces, using a secret prefix. SecondFi didn't have a secret prefix at all, meaning anyone could derive the nonce by just seeing a signed transaction. Rolling your own crypto code is dangerous, I'm guessing the wallet wasn't audited, resulting in this problem going undetected. Read more at Tibane: tibane.net/research/secondfi…
13
20
3
155
44,083