
Open-Source PM @spiral_xyz. Building Open Money & Open Intelligence
Florida
Joined January 2012
- Tweets5.2K
- Following867
- Followers5.5K
- Likes15.9K
Bitcoin is now on by default at Square checkouts across the U.S.
Sellers don't have to apply. Square switched it on for every eligible business, whether the owner has ever thought about bitcoin or not.
The customer scans a QR code with any Lightning wallet and the payment settles in seconds. The seller gets dollars by default or can choose to keep the bitcoin, and there are no chargebacks. Sellers can also auto-convert up to 50% of their daily card sales into bitcoin.
The limits: $600 max per payment, $20,000 a day, and sellers in New York are left out.
The fee is 0% through Dec. 31, then a flat 1%. A card tap on Square's free plan costs the merchant 2.6% plus 15 cents.
Conor Okus retweeted
Announcing a major milestone achieved by my team @GoogleDeepMind: we have proven key security properties of the machine code underlying the Signal messaging protocol. This is the first time the actual production code of a widely deployed protocol has been formally verified – by any method, with or without AI – and at this depth.
More than a research breakthrough, it’s a prime example of how frontier AI can be a force multiplier to counter the speed and scale of modern cyber threats.
Formal verification offers a higher standard of security; however, it’s extremely complex and time consuming, which is why in many cases it’s considered to be impractical. Similar efforts could take teams decades of combined effort. We did it in a month’s time.
Using AlphaProof Code, Google DeepMind's new agentic framework for formal verification that runs on LLMs including Gemini Carbon, we verified the Signal protocol down to the actual code running on devices. This milestone lays the groundwork for a future in which vital systems, from medical device firmware to power grid software, ship with mathematical proof that their protections work.
Reaching that future will take continued research from our community. In that spirit, we're open-sourcing our formal specifications and verification artifacts so others can build on this work.
On a personal note, this moment is of deep significance to me. I started my own research journey more than two decades ago as an intern working on checking the consistency of complex software systems. Seeing this grand challenge made practical with modern AI is extraordinary.
I'm extremely proud of my team members: Swarat Chaudhuri, Andrew Ferraiuolo, Anton Kovsharov, Tej Chajed, Sam Schlesinger, Karn Seth, Jonathan Katz, and Charles Sutton for taking on this grand challenge and delivering, and grateful to the Signal team for their partnership.
deepmind.google/blog/formal-…
Conor Okus retweeted
Bitcoin Lightning payments are now part of x402, contributed by new x402 Foundation member Block.
Servers can now list Lightning in a 402 response, alongside the networks x402 already supports.
Learn more about the standard and get involved: x402.org
Conor Okus retweeted
Bitcoin payments don’t have a technology problem. They have a reason-to-use-them problem. Last week, we asked the community how to change that. Find our summary here: spiralxyz.substack.com/p/val…
Conor Okus retweeted
This is what we want to push for!
Withdrawals to $Cashtag as low as 1 sat <$0.01 with no fees 💚 @CashApp
Conor Okus retweeted
Builder Miami Recap from tonight.
@conorokus and I co-hosted a round table discussion with a room full of AI and bitcoin builders talking personal agents, open models and bitcoin payments, and the questions that matter, who your agent works for, what owning your AI means, and where bitcoin earns its place.
Until next time!
Special thanks to @coinward and @BitcoinGrove for the space!
buildermiami.ai
🤖 Made with AI
If you're interested in moonshot ideas the community has imagined for bitcoin payments, we've collected the most interesting ones in our GitHub discussion: github.com/spiralxyz/bitcoin…. It's an ongoing conversation and new ideas are still coming in, so jump in, react to your favourites, and add your own.
.@jack thinks bitcoin payment adoption isn’t where it should be. We want your ideas on how @Blocks, Spiral, and you can increase adoption within 5 years. Our trajectory needs changing. Here’s more on our thinking. Now we want yours: github.com/spiralxyz/bitcoin… View article
it's a bit hard to know what to build next or even why to build at all right now. but we musn't stop.
what to build?
the answer i think involves: big ambition, science, data, robots, value networks & storytelling
and why?
as ever, to build the world you want to see
read on:
Some coping strategies for builders who are feeling bummed out by the unrelenting acceleration of AI. spiralxyz.substack.com/p/bui…
Conor Okus retweeted
.@jack thinks bitcoin payment adoption isn’t where it should be. We want your ideas on how @Blocks, Spiral, and you can increase adoption within 5 years. Our trajectory needs changing. Here’s more on our thinking. Now we want yours: github.com/spiralxyz/bitcoin… View article
Conor Okus retweeted
Renato Britto (@0xsatsfy) is working full time on rust-bitcoin: shipping the 1.0 crates, leading units-first work, reviewing, and migrating BDK and others off 0.32. Before stable, he tries to break it with fuzzers, mutants, provers, and LLM agents, then fixes what fails.
Conor Okus retweeted
Spiral’s @moneyball is speaking today at AGNTCon + MCPcon in San Jose about @goose_oss’s evolution into an open-source agentic SDK.
10:35AM in room 230C
In a prior life at @jpmorgan, I was the tech lead building out their digital asset trading infrastructure on Ethereum tech.
The system went to prod and processed literally trillions of dollars in repo trades: tokenized US dollar deposits (the cash leg) vs. tokenized US Treasuries (the collateral leg).
Even though it was a bank blockchain, we still built the whole stack: token contracts, trade contracts, consensus, full nodes, private key management, atomic swaps, administrative controls, point-and-click web apps, role-based permissions, etc.
The hardest part was the integration with the legacy systems: (1) the dollar clearing on JPMC's general ledger and (2) the Treasury movements over SWIFT messages.
I got to see firsthand where the blockchain rubber meets the banking road. It ain't pretty. Operationally we did double the work, so at times it felt pointless.
Still, there is money to be made by making capital markets faster and more accessible, so tokenization will definitely happen, in some form or another.
A lot of banks like being slow and cumbersome: that's their moat n' float! The challenge, as @malekanoms notes, is that these banks are very competitive with each other, and they care about who owns the rails.
One funny thing about doing this in the early 2020s was that interest rates were so low that even the interest on a billion-dollar repo trade was laughably small. Times have certainly changed.
I also came away with another grim conclusion: banks are effectively a fourth branch of the US government. They exist at the mercy of the state; expect a Chokepoint v3.0, 4.0, 5.2.1.
The work was fascinating, but I wanted to work on bitcoin, the future of money. I pitched JP Morgan on building a bitcoin custody service. I asked them to give me a team to build it.
"This will make you a billion dollars," I told them. But of course they weren't interested ... come on Jamie! 😅
So I left to work on bitcoin and build @stablechannels, and I haven't looked back.
It is true that tokenized deposits will only flow between whitelisted wallets that are already customers of the relevant bank. However they will be very useful as the cash leg of atomic swaps for tokenized assets (for instance Treasuries and equities to facilitate repos and stock loans). To say that tokenized deposits are purely performative is intellectually dishonest.
Yes, a stablecoin that holds only treasury repo and short duration bills or even central bank money with everything held on-chain would be a more useful and robust cash leg (other than the fact that it doesn’t pay interest!). Of course that doesn’t exist. JPMD and other money center bank deposits will be viewed as lower risk than stablecoins in their current state by institutions and will likely be the go-to solution for repo and stock loan. It’s possible an orchestration layer will be built to facilitate the preferences of different institutions for different deposits and a stablecoin could be part of that. Will be interesting to see how it evolves.
Conor Okus retweeted
Bitcoin finally gets a fact-checker. @ProofOfKeags is working on BTC-verified, which formally verifies bitcoin’s protocol rules. His new fuzzing harness links the formal model to libbitcoinkernel so the two can be checked against each other. Next up: modeling script semantics.
Conor Okus retweeted
Kulpreet Singh (@jungly) is building p2poolv2, a decentralized mining pool. Pools are one of bitcoin’s last big points of centralization, and p2poolv2 nixes the operator entirely, letting miners coordinate peer to peer and make payouts without middlemen.
Conor Okus retweeted
Patrick Dugan (@duganist) is building UTXORef so two people can bet on price and let bitcoin settle up, making it impossible for friends to pretend they never made the bet. He’s also on draft three of a paper on the capital limits of Lightning, Ark, and ZK batched liquidity.
Conor Okus retweeted
.@PresidioBitcoin’s resident polymath and compulsive Google Docs comment dropper @_austin_f is helping champion Goose, GDK, and Buzz. With this grant, he’ll onboard bitcoin and FOSS teams, develop a self-paced GDK Builder Course, and add Buzz features like operational agents.
Conor Okus retweeted
Loupe findings have been landing in Bitcoin Core. During this cycle, five PRs landed: three have been merged, two are under review. Below is a thread on what each one caught and which Core dev implemented which fix.
Conor Okus retweeted
New vertical: AI Caramba lets the goose team open up about anything AI. In this first edition, @dosinga explains how goose replaced the agent loop with a state machine that can be turned off anywhere and resumed like nothing happened. Where does it go in between? Hell if we know.
Here's the Stable Channels Lightning Server dashboard UX 👇 built on @lightningdevkit by @benthecarman, @_tnull @Biresh_Biswas et al. (node IDs/numbers changed)
Little ⓘ buttons explain Lightning jargon throughout. We hope to bring it to Umbrel ASAP when LDK Server ships!




























