Pinned Tweet
After 13 years contributing to the OpenWISP community, collecting feedback, taking notes, and researching, I’ve distilled my vision into the Roadmap to 2030. 🚀Scalability, universal protocols, and easier deployment ahead. openwisp.org/blog/roadmap-to…
Venezuela's script
>be Lula
>get convicted of corruption
>get sentenced to 12 years
>get released by the STF on procedural errors
>never actually acquitted lmao
>beat Jair Bolsonaro in 2022
>Jair gets thrown into jail over an alleged coup attempt
>Congress votes to cut his sentence
>Lula vetoes it
>four years later, face his son
>during a debate, threaten to also lock him up if he loses the election
>election day
>former private lawyer, now STF judge, extends voting by 2 hours nationwide
>request came from Lula's own coalition
>win by 4 million votes in a runoff with no paper trail
>next day, Moraes orders the losing candidate to surrender his passports
>victory speech: "we're going to regulate social media"
>"democracy" lmao
>RIP Brazil
I felt like this today @_pandafy_
Federico Capoano retweeted
This guy is either trolling or he genuinely does not understand quantum computing. ECDSA does not break because AI read some math papers and GPUs exist. A known break requires a fault-tolerant quantum computer running Shor's algorithm, which we do not have. To break Ethereum ECDSA, you need hundreds of thousands of physical qubits that are low-noise, controllable, connected, error-corrected, cooled, calibrated, decoded, and operated as roughly 1,200 to 1,500 logical qubits (500,000 physical qubits for error correction) for a huge Shor computation.
The missing piece is not one clever AI-discovered trick. It is an entire fault-tolerant quantum computing stack that has not been built yet. If he is claiming ECDSA falls before Q-day on GPU clusters, he is implying a classical Shor-level break of elliptic curve discrete log. Show the attack, the complexity, the benchmark, or even a toy result. Otherwise "security researcher" is doing a lot of work in his bio.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
Java is like $XRP, corporate shill destined to oblivion
Federico Capoano retweeted
Wrapped up GSoC 2026 with @openWISP. This is what I've been working on all summer.
Big thanks to @nemesifier, @_pandafy_ and Oliver Kraitschy for mentoring me through it. Learned more from your reviews than I expected to.
#GSoC2026 #OpenWISP #OpenSource
Upgrading #OpenWrt firmware across an entire fleet of network devices is about to get much easier with Persistent & Scheduled Mass Upgrades in OpenWISP! ⚡ openwisp.org/blog/gsoc-2026-…
#GSoC #OpenWISP #OpenSource #NetworkAutomation #NetworkManagement
Upgrading #OpenWrt firmware across an entire fleet of network devices is about to get much easier with Persistent & Scheduled Mass Upgrades in OpenWISP! ⚡ openwisp.org/blog/gsoc-2026-…
#GSoC #OpenWISP #OpenSource #NetworkAutomation #NetworkManagement
Ever had to run shell commands across an entire fleet of #OpenWrt devices?
The new Mass Commands feature of OpenWISP is going to make this very easy!
openwisp.org/blog/gsoc-2026-…
#GSoC #OpenSource #NetworkManagement #NetworkAutomation
Federico Capoano retweeted
Finally finally I have completed my Google summer of code 2026 as a contributor am so glad this happened. I still remember i was in my first year when i saw @kunalstwt video about open source progams like GSOC and others and since then I wanted to participate and contribute.
Finally I was able to do it in my 4th year of engineering. Had lot of learning during this period specially the intensive PR review cycle with @nemesifier I am glad that we test and review the code manually in this world of AI slop everywhere. I did used AI but resposibly where i know what each moving part is doing.
The point of concern for me initially was that this GSOC project has failed twice in past by previous GSOC mentees... but I just kept going piece by piece with guidance of maintainers and here we are.
DONE AND DUSTED!!
for more technical info about my project read the blog - lnkd.in/dg3BbByT
#InfluxDB 2 and #Elasticsearch will soon be supported in #OpenWISP Monitoring for time-series data storage!
Read more: openwisp.org/blog/gsoc-2026-…
Proud to have been part of this Free Software Victory after a decade preventing Radio Lockdown!
fsfe.org/news/2026/news-2026…
OpenWISP 26.09 is out!
openwisp.org/blog/openwisp-v…
Improved geographic and indoor maps, real-time feedback for mass firmware upgrades, automatic WHOIS data and estimated locations, and loads of other improvements!
Federico Capoano retweeted
The results from the 2026 Django Developers Survey are in! Learn the latest on how people are developing and deploying their Django apps from the published results here: lp.jetbrains.com/django-deve…
#django #jetbrains
Federico Capoano retweeted
everyone is running into a wall with agentic engineering right now
you don’t hear people talking about it because
1. they profit from selling you “solutions”
2. they want to look smarter than others
so let me be the whistleblower - the wall is called “how does it feel”. agents can’t do it
they can walk right past the ugliest UI or the most obvious bug and don’t say a thing unless that’s what you asked
they can take many screenshots and burn through my tokens but they can’t tell me if my landing page animation looks cool
they can click through my app but they won’t feel the dopamine hit when i physically drag my finger on the touch screen and feel the command dial flow with me in @theSSHHIP
this wall is structural. it’s actually load-bearing 😉
because of this wall, we can’t really throw a ton of agents at any problem that depends on “how does it feel” without constantly stopping for human feedback and steering
if you just let the agents keep running without human input, then your codebase will have more and more things that “don’t feel right”
you can avoid the wall by working on non-human problems, like pure math and a lot of scientific research
but the moment you want to build something useful for humans, this wall is there
if you see people pretend they have automated software factories running thousands of agents working all the time, don’t be afraid. don’t feel FOMO, because the only thing those factories shipped are the factories themselves, with human help































