TUESDAY, JUN30
1. Hold BTC, pay in dollars, 2. Ardoino on open AI, 3. Build your own signer, 4. Liquid audit fix
From Proto and Bitkey - part of the Bitcoin ecosystem at Block, Inc.
1. breez
Breez has added a feature to its bitcoin payments software development kit that lets wallet users send the dollar-pegged stablecoins USDC and USDT across more than 30 blockchain networks without actually holding any stablecoins themselves, according to Cointelegraph. The mechanism keeps users in bitcoin while letting them pay counterparties who want dollars, with the conversion handled under the hood. For a freedom-tech audience, the development is a notable twist on the stablecoin question: rather than asking bitcoiners to custody dollar tokens issued by centralized firms, it lets them hold only bitcoin and settle in stablecoins only at the moment of payment. That preserves a bitcoin-native balance sheet while bridging to the dollar rails much of the world still prices in. The approach sits alongside a broader wave of SDK-level integrations that abstract away complexity for wallet developers. Whether routing through stablecoins at the point of sale meaningfully reduces exposure to issuer and censorship risk, or simply relocates it, is the question builders will weigh as the feature reaches wallets.2. ardoino
Tether chief executive Paolo Ardoino has warned that large technology companies are mounting what he called a warpath against open-source artificial-intelligence models, using safety as the stated justification while, in his telling, really defending business models threatened by freely available alternatives, in a post on X. The comment lands amid an intensifying debate over whether frontier AI should be tightly controlled by a few well-resourced firms or developed in the open where anyone can inspect, run, and modify the models. For a freedom-tech audience, the framing rhymes with arguments long made about money and software: that appeals to safety and consumer protection can serve to entrench incumbents and foreclose permissionless alternatives. Ardoino, whose company has been funding open AI work, is an interested party rather than a neutral observer, so the claim is best read as advocacy. Still, the open-versus-closed AI fight raises the same concentration-of-power questions that drive bitcoiners toward systems no single company controls. Who gets to build and run intelligence, and on whose terms, is becoming a defining fight.3. chiangmai-signer
SeedSigner amplified a call to build your own open-source bitcoin signer at a July 18 workshop in Chiang Mai, with materials costing under fifty dollars and full user control over the device, in a post on X. The event pitch frames do-it-yourself signing as accessible self-custody rather than a vendor purchase decision. For Bitcoin Park readers tracking hardware sovereignty, the workshop is another datapoint in the SeedSigner ecosystem’s grassroots education model: transparent designs, community builds, and permissionless learning outside corporate wallet onboarding funnels. As protocol politics get louder, hands-on signer builds keep ordinary holders closer to the metal. The approach treats self-custody as a skill to be learned and a device to be understood, not a product to be bought, which is the deeper sovereignty lesson beneath the cheap parts and the soldering iron. Building the tool yourself also removes a supply-chain trust assumption, since you know exactly what went into the device guarding your keys.4. liquid-audit
Wiz of the Mempool Open Source Project disclosed a bug in which new federation wallet addresses from the Elements node were not ingested correctly, which temporarily made it appear on liquid.network that the Liquid federation wallet held less bitcoin than it actually did, in a post on X. He said the team fixed the issue right away and reran a full audit within a day or two to verify balances. Wiz emphasized that the code lives in public repositories, so anyone can verify without trusting his word. For protocol watchers, the episode is a live example of why federated sidechain transparency depends on tooling accuracy, and why open-source audit pipelines matter when billions ride on federation accounting. The fact that the discrepancy was a display-and-ingestion bug rather than missing funds is the reassuring part, and the fact that anyone could check the public code rather than take an operator’s assurance is the deeper point about how trust is meant to work on open systems.Consider subscribing and sharing OP_Daily with your community.