
Dr. GoNoGo - Highly caffeinated bonobo & computer brogrammer, unemployed optimizer, prev @wonderland
You are here
Joined April 2010
- Tweets4.3K
- Following1.1K
- Followers1.1K
- Likes4.2K
Simon Something retweeted
Time to talk about this one.
CopyFail (CVE-2026-31431) — a 732-byte Python script that roots every Linux distro shipped since 2017. 🧵
Simon Something retweeted
300+ days? Let’s make this quicker.
interop-sdk is ready to integrate.
Interoperable names will go hard.
interopaddress.com/
Replying to @apoorveth
Interoperable names are going to go so hard. Especially once wallets take 300+ days to implement it. At least then users won't need to go to bridges directly.
Simon Something retweeted
Be sure to visit our amazing diamond sponsor @Wonderland in their gorgeous booth before the end of EthCC[9] 💎
We're so grateful for their support this year!
Simon Something retweeted
Wonderland CTF prizes are in: $30,000 on the line.
$15k, $10k & $5k for the top 3.
Plus a few surprises. May the best teams win.
Simon Something retweeted
The rabbit hole keeps going deeper.
Also sponsoring the Wonderland CTF:
@envio_indexer
@PashovAuditGrp
@therealgregoAI
@rv_inc
Simon Something retweeted
A year ago we started collaborating with the @ethereumfnd on interoperability.
A few weeks ago, alongside @ensdomains, @unruggable_eth, and the EF, we shared Interoperable Addresses.
Today, the team launched the onchain registry that enables names like:
alice.eth@ethereum
Another piece of the interop stack is live 🪄
I have just released bulloak toolchain v2.2.0. A big thanks to @simon_something for his invaluable suggestions. This version has fixed an issue with caching and supports the latest bulloak build.
If you're still on v1, I strongly recommend upgrading to v2. The link 👇
Simon Something retweeted
Sending assets across any chain in the Ethereum ecosystem should be as simple as typing an address and clicking send.
Now it is! Introducing Interoperable Addresses:
Just use alice.eth@<chainName>
Simon Something retweeted
Lmeow, realized this morning that @0xParticle, one of our applied cryptographers, spent the last year writing a full Zero-Knowledge Proofs book in his spare time.
If you’re into ZK, this is genuinely worth reading.
Yes, this is the kind of people you work with at @Wonderland.
Simon Something retweeted
As a crypto CTO, I’m tired of seeing sloppy practices that cost millions.
I came from the army, where mistakes cost lives. I brought that same discipline into crypto.
If you manage user funds and you’re not doing what’s below, act now.
These are the non-negotiables 👇
Simon Something retweeted
Speaking at the World Economic Forum, Spanish PM Pedro Sánchez demands "an end to anonymity on social media"—under the guise of combatting "misinformation" and "hate speech".
"We must... force all these platforms to link every user account to a European digital identity."
Simon Something retweeted
Wonderland is a great team and has been very helpful in the Ethereum ecosystem, including to the EF on interop and Kohaku, and to many Ethereum projects.
My startup, @Wonderland, is hiring 10 Senior Solidity developers.
We work at the cutting edge of crypto. There’s no better place to get exposure to the coolest shit being built in this space.
DM me, you won't regret it!
RTs appreciated for reach.
Simon Something retweeted
This is what @VitalikButerin had to say about @Wonderland ❤️
Fresh off the press.
Simon Something retweeted
The good news? A lot of companies are hiring for their internal security:
- Web3 Security Specialist at @binance (+ they have a lot of similar positions) - binance.com/en/careers/job?i…
- Security Analyst at @Figment_io - job-boards.greenhouse.io/fig…
- Senior Security Engineer at @Immutable - jobs.lever.co/immutable/b094…
- Protocol Security Engineer at @monad - jobs.ashbyhq.com/monad.found…
- Protocol Security Engineer at @the_matter_labs - jobs.ashbyhq.com/matter-labs…
- Security Engineer at @Offchain - jobs.arbitrum.io/companies/o…
- Security Engineer at @paritytech - jobs.ashbyhq.com/parity/058e…
- Staff Product Security Engineer at @phantom - jobs.ashbyhq.com/phantom/7a9…
- Senior Application Security Engineer at @Uniswap - job-boards.greenhouse.io/uni…
- Compiler security engineer at @vyperlang - jobs.cyfrin.io/jobs/compiler…
- Security Engineer at @wonderland - apply.wonderland.xyz/o/secur…
(Feel free to drop your job ads below if its for an internal security position)
Most protocols spend a lot on audits and bug bounties but have zero internal security
Launching whohassecurity.com to highlight the ones that do
Having an internal security team should be in every protocol's New Year's resolutions for 2026
Simon Something retweeted
Most protocols spend a lot on audits and bug bounties but have zero internal security
Launching whohassecurity.com to highlight the ones that do
Having an internal security team should be in every protocol's New Year's resolutions for 2026
Simon Something retweeted
Encrypted messaging, like @signalapp, is critical for preserving our digital privacy. Two important next steps for the space are (i) permissionless account creation and (ii) metadata privacy.
@session_app and @SimpleXChat are two messaging apps pushing these directions forward.
For this reason I've donated 128 ETH to each. Addresses available on their websites if you wish to follow on:
getsession.org/
simplex.chat/
But also, actually download and use them!
Neither of the two are perfect pieces of software, they have a way to go to get to truly optimal user experience and security. Strong metadata privacy requires decentralization, decentralization is hard, users expecting multi-device support makes everything harder. Sybil / DoS resistance, both in the message routing network and on the user side (without forcing phone number dependence) adds further difficulty.
These problems need more eyes on them. I wish all teams working on these important problems best of luck.
Simon Something retweeted
We’re thrilled to stand alongside the Aztec team on what we see as one of the defining missions in all of web3, bringing real privacy to the world.
And we’re backing that conviction with action. Wonderland is investing in the Aztec sale.
Wonderland is joining Aztec as core developers.
After a year collaborating, it’s clear why @wonderland is so in demand.
We're honored they chose to go all in on @aztecnetwork, privacy, and on building something that really matters.
Simon Something retweeted
Here's another French journalist participating in fearmongering about GrapheneOS. That article is not measured. It provided a platform to make both unsubstantiated and provably false claims about GrapheneOS while providing no opportunity to see and respond to those claims.
bsky.app/profile/gabrielthie…
The claims the article platforms are conflating closed source products from European companies infringing on our copyright and trademarks with GrapheneOS. GrapheneOS doesn't have the features they claim it does, isn't distributed in the ways they claim and they don't understand open source software.
GrapheneOS is obtained from grapheneos.org/install/web and grapheneos.org/releases. There are a bunch of legitimate companies in Europe selling devices with real GrapheneOS including NitroKey. We aren't partnered with those companies and don't get funding from it but there's nothing shady about it.
Products using operating systems partially based on our code are not GrapheneOS. There's no such thing as a fake Snapchat app wiping the device in GrapheneOS. It has no remote management or remote wiping built into it. It does not have a subscription fee / licensing system built into it either.
Vast majority of the code for those products comes from elsewhere: Android Open Source Project, Linux kernel, Chromium, LLVM and other projects. Of course the non-profit open source project writing a small portion of the code being used by those companies being targeted rather than IBM, Google, etc.
Both Android and iOS try to defend users from the same attack vectors we do. We developed far better protections against exploits which we release as open source code. Open source means anyone can freely use it for any purpose, exactly like the Android Open Source Project used by GrapheneOS itself.
Open source is why we can build GrapheneOS based on the Android Open Source Project. It doesn't make Linus Torvalds, IBM, Google, etc. responsible for what we do. Similarly, others can make their own software based on GrapheneOS. A fork of GrapheneOS contains a small portion of code written by us.
France supposedly has a right to reply which we intend to exercise to respond at length to these articles containing libel from the French state.
We're going to be ending the small amount of operations we have in France as we don't feel the country is safe for open source privacy projects anymore.
GrapheneOS doesn't host services storing sensitive user data. We have signature verification and downgrade protection for updates to the OS, apps and app store metadata. We're going move our website and discussion server away from OVH. Our update mirrors and authoritative DNS are already elsewhere.
Our discussion forum, Matrix, Mastodon, etc. in OVH Bearharnois can be moved to local or colocated servers in Toronto instead. We can use Netcup (owned by Anexia, both German) as one of the main providers for website/network service instances. The majority of our servers are already not on OVH.
We won't travel to France including avoiding conferences and will avoid having people working in the country too. A simple heuristic for the EU is avoiding countries supporting Chat Control. We genuinely believe we cannot safely operate in France anymore as an open source project privacy project.
Our pinned post on this platform shows a great example of why they're actually upset with us:
xitter.cf/GrapheneOS/status/1887…
It almost makes us willing to contribute to AOSP again to try to wipe out their ability to exploit a subset of unon-GrapheneOS Android devices too. Google is welcome to reach out.
In April 2024, Pixels shipped a partial implementation of our January 2024 proposal for firmware-based reset attack protection. Fastboot mode now zeroes RAM before enabling USB. This successfully wiped out the After First Unlock state exploit capabilities of two commercial exploit tools.
Several other improvements were made based on our January 2024 vulnerability reports and proposals including an implementation of wiping data before rebooting when a wipe is triggered. We shipped an improved version of this for our duress PIN/password feature before the feature shipped for Android.
We made massive improvements in GrapheneOS to defend against these attacks since January 2024.
For ARMv9 devices, we greatly improved our hardware memory tagging implementation in hardened_malloc, deployed it for the Linux kernel allocators and greatly expanded the use of PAC and BTI across the OS.
We replaced our decade old feature for blocking new USB peripherals while locked with a greatly expanded and far more secure feature. The new approach blocks USB-C connections and USB-C data at a hardware level with expanded software-based blocking as a fallback (grapheneos.org/features#usb-…).
We started deploying RANDSTRUCT for the kernel, which will eventually be used to have multiple possible struct memory layouts for each device model chosen randomly at boot. Our work on reducing kernel attack surface also continued. We plan to focus more on Linux kernel security going forward.
Our locked device auto-reboot feature from 2021 was replaced with a more secure approach preventing bypasses via crashes (grapheneos.org/features#auto…). It also avoids chain reboots without introducing a security weakness which makes low timer values such as the minimum 10 minutes far more usable.
We shipped our 2-factor fingerprint unlock feature planned since 2015 (grapheneos.org/features#Two-…). It allows people to avoid reliance on secure element security with a strong passphrase while keeping convenience. Fingerprint + scrambled PIN also defends well against being recorded unlocking.
Several more major improvements specifically against the physical data extraction attack vector are planned. Our next release adds an implementation of zeroing RAM at boot in the kernel to match what fastboot mode does. We also plan to add a toggle for essentially toggling off Device Encrypted data.
Simon Something retweeted
Don’t say we didn’t warn you.
luma.com/58n1gthl
























