Federico Jordan

iOS Engineer  @bitso. Prev @peyatech @olxgrouptech @letgo. 3D design, game programming, infosec, #bitcoin

[Pablo Planovsky @PabloPlanovsky]

Edward Norton hablando solo en el Mundial:

[Alan Riedmaier @AlanRiedmaier]

@amaterasu_jp_33 @JohnGalt_is_www Por lo mismo que con la impresora 3D dijeron que cada uno iba a fabricar sus propios productos, pero nadie hoy lo hace. Por qué? Porque queremos el producto, eficiente, bonito y barato puesto en mi puerta en tiempo record. No quiero renegar.

Llevalo al ambiente corporativo.

[DAN KOE @thedankoe]

https://t.co/9DllJuH2ie

[Federico Jordan @FedeJordan90]

@rauchg Alguien tenía que dar la cara por latinoamérica

[Stan Trenev @sstrenev]

I felt bored and vibe-coded a neobank in a week. The best part? You don’t even realize it runs entirely on crypto rails under the hood.

Main functionalities:

- On/off-ramp fiat to stables via BridgeXYZ
- Send, receive, and request stablecoin payments on Base
- Deploy funds to selected blue-chip DeFi protocols
- Get a free Gnosis Pay crypto debit card

All of this is powered by account abstraction and non-custodial wallets.

Users receive a Privy wallet upon registration and never have to worry about signing transactions or approvals.

Transactions are sponsored and batched via EIP-7702, so no separate token approvals are required either.

In a nutshell: one-click access to stablecoin transactions sent directly to users via email, plus seamless entry into DeFi.

Tech stack:

- BridgeXYZ – on/off-ramp fiat to stables
- Privy – non-custodial wallets
- EIP-7702 – transaction batching and sponsoring
- iOS app built with React Native
- LIFI API – swapping between USDC and EURC
- Resend – email notifications
- DeFi protocols: Aave, Morpho, Compound, and YO
- Gnosis Pay API – virtual crypto debit cards
- NodeJs Backend

Inspired by @alliance's request for startups.

If you want to check it out, let me know so I can add you to TestFlight.

[Valentin Ignatev @valigo]

"I use loops", said Linux Kernel creator Linus Torvalds, when asked about new trends.

"You can't write programs without loops", he added.

[nisedo @nisedo_]

A must read

https://t.co/d4tiRoEvpI

[Peter Steinberger 🦞 @steipete]

Here’s your monthly reminder that you shouldn’t be prompting coding agents anymore.

You should be designing loops that prompt your agents.

[Justin Drake @drakefjustin]

Today a crazy quantum story just got wilder.

On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures.

But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first!

As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise.

Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours.

Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure.

Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice!

The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :)

Part 2: neutral atoms and qday

The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers.

Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low.

Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts.

My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom".

Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions.

So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030.

Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years.

Part 3: post-quantum cryptography

There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation.

These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer.

The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security.

Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.

[Mathias @MathiasChu]

Aprovecho la polémica para compartir un mapa que atesoro: shademap, un mapa que te muestra cómo la luz le da a los edificios. Ideal si querés comprar/alquilar

[Dwarkesh Patel @dwarkesh_sp]

New blackboard lecture w @reinerpope

How do chips actually work – starting with basic logic gates, and working up to why GPUs, TPUs, FPGAs, and the human brain each look the way they do.

0:00:00 – Building a multiply-accumulate from logic gates
0:16:20 – Muxes and the cost of data movement
0:25:59 – How systolic arrays work
0:39:00 – Clock cycles and pipeline registers
0:51:40 – FPGAs vs ASICs
1:03:14 – Cache vs scratchpad
1:07:16 – Why CPU cores are much bigger than GPU cores
1:11:49 – Brains vs chips
1:15:22 – A GPU is just a bunch of tiny TPUs

Look up Dwarkesh Podcast on YouTube/Spotify/etc to watch. Enjoy!

[Florian Roth ⚡️ @cyb3rops]

VSCode

Shift + Command + P (Mac)
Ctrl + Shift + P (Windows/Linux)

Disable Auto Update for All Extensions

[Anatoli Kopadze @AnatoliKopadze]

instead of watching 2 hours of Netflix tonight, watch this Stanford lecture

it's the clearest explanation I've seen of how ChatGPT and Claude actually work

useful whether you've never touched AI in your life or have been using it every day for the past year

I took the key ideas and turned them into a practical guide on how to actually get 100% out of Claude

find it below

[Richie @richiemcilroy]

"Is that code AI generated? If it’s AI generated I don’t want it"

[Rohit Ghumare @ghumare64]

@RoundtableSpace https://t.co/DV12HanJ9a has everything!

[0xMarioNawfal @RoundtableSpace]

Great Resource to Learn Harness Engineering

https://t.co/JXR8k4FFUD

[Avid @Av1dlive]

in 15 minutes, 2 Senior Staff Engineers at Airbnb gave a Live Lecture on Agentic Coding

Airbnb already shipped one of the most ambitious LLM-agent migrations in production.

Tonight two of their senior engineers shows how they actually build with agents in 2026.

Most builders are guessing. These guys ship.

bookmark & watch this.then read the complete article below.

[nader dabit @dabit3]

This is crazy. The hacker installed a dead-man's switch that will wipe your computer if you revoke the GitHub token they stole from you. Revoking the token is what triggers the wipe.

[ℏεsam @Hesamation]

Claude convincing ChatGPT it’s being rude lol

[kache @yacineMTB]

you can outsource your thinking
but you cannot outsource your understanding