1. bitbox

Hardware wallet maker BitBox has shipped firmware version 9.26.5 to close two vulnerabilities the company itself labels severe. Ezra Reguerra’s account in Cointelegraph lays out both paths: a memory corruption bug affecting Multi editions of the BitBox02 and BitBox02 Nova that had not yet been configured with a wallet, and a defect in the device’s Silent Payments implementation. On the first, “a malicious host could exploit it to execute arbitrary code and potentially install malicious firmware, which could lead to lost funds.” The second could not move coins directly but could lock bitcoin to an unintended address, leaving an attacker positioned to demand a ransom for cooperating in recovery. BitBox said it has received no reports of either flaw being exploited or of any user losing funds. The disclosure lands while the Coldcard seed-generation failure is still being tallied at more than 1,778 BTC swept from over 8,600 addresses. Vendor firmware, not the protocol, is where the sharp edge of self-custody risk now sits.

2. surplus

RY3T, an energy hardware company based in Wil, Switzerland, has built the first commercial product running Mujina, the open-source Bitcoin mining firmware the 256 Foundation started and funds. As the foundation details in its newsroom post, the Nova mines with the solar output a building cannot consume, following the generation curve second by second and taking its instructions from the energy management system already running the site. The capability underneath is deliberately unglamorous: “Mujina accepts a power target and settles on it in seconds, without restarting the mining process.” Set 1,400 watts and the machine is there before the next cloud arrives. The firmware is GPLv3 and written in Rust, and RY3T needed no partnership, license negotiation or permission to build on it. Contributors have also run three hashboards spanning two chip generations together on a single control board at 136.70 terahashes per second. Treating power as a live input is what turns a miner into a dispatchable household load.

3. jamming

Bitcoin protocol researcher Antoine Riard has published a construction that would let Lightning nodes charge for the time a payment sits unresolved. He set out the design in a post on Delving Bitcoin, framing the contract as a way for two channel counterparties to agree that “a deterministic message has been previously exchanged or not among them at a given blockchain time, a practical universal clock.” The conditional message transfer contract encodes three alternative spending paths in a single tapscript — message transfer success, liveliness challenge, and message transfer failure — combining adaptor signatures, per-timepoint oracle points and CLTV timelocks so that whichever party goes dark forfeits the withhold fee. Channel jamming has resisted mitigation because there is no shared clock and no way to prove a message was ignored, which is exactly the gap the design attacks. Riard presents the on-chain version and leaves the off-chain lift to later work, and the first reply already asks how the scheme composes across an onion-routed path.

4. rewrite

RoninDojo has shipped version 3.0.0 of its privacy-focused bitcoin node stack, moving the release out of beta. The project announced the launch on X and put the case plainly: “we need open source node software that enables anyone be their own bank, have the electronic cash experience, and avoid trusting a 3rd party.” Version 3.0.0 is a complete rewrite rather than an incremental patch. The team describes it as running on both x86 and ARM hardware, with RockPro64 and the Raspberry Pi 4 and 5 among the supported boards, using fewer resources and running faster than the build it replaces. The rewrite also gives the RoninUI front end room for more tooling. Hardware breadth is the part that matters for adoption, because a node that runs well on a spare mini PC or a single-board computer removes the cost argument against self-hosting. Each household validating its own chain is one fewer household taking a third party’s word for what the ledger says.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. postmortem

Jameson Lopp has published a long post-mortem on BIP-110, the failed soft fork that would have restricted arbitrary data in Bitcoin transactions. Miner signalling peaked at 2.5% against a 55% activation threshold, and the chain that split off at block 961,632 survived four blocks, all mined by the anonymous outfit Roughnecks, before the split collapsed within hours. OCEAN was the only pool to back it and afterwards refunded miners whose hashrate had been redirected. Lopp writes in the post that the economics never worked: “BIP-110 only offered purity / morality / removal of functionality and LESS fees for miners.” The client’s release history did not help. A release candidate shipped with failing tests and unsigned binaries, and a previously undocumented eighth consensus rule surfaced two weeks before mandatory signalling began. His sharpest conclusion is procedural rather than technical: a user-activated soft fork needs more than a vocal minority behind it, and treating everyone who disagrees as an enemy is not a method for building consensus.

2. lps

Jensen Huang has given the bottleneck throttling AI buildout a name — land, power and shell — and committed NVIDIA to securing it directly rather than waiting for customers to do it. He set out the reasoning in a post on X announcing a partnership with SB Energy at the PORTS-Pike Technology Campus in Portsmouth, Ohio, where OpenAI will be the tenant. NVIDIA is backing defined portions of lease and power payments plus a residual-value commitment across roughly 4 gigawatts on a 20-year term, with the guarantee phasing in as data centers enter service between 2028 and 2030. Initial capacity is 4.25 gigawatts, and each generation of systems on the site could mean about 1.5 million GPUs and $150 billion to $200 billion in NVIDIA revenue. Huang is explicit about the shift: “we are now applying that same discipline to secure LPS capacity exclusively for NVIDIA AI factories.” A chip vendor underwriting grid interconnects and building shells has decided electricity, not silicon, is the binding constraint.

3. venice

Erik Voorhees says Venice, the privacy-focused AI app he founded and runs as chief executive, has crossed $100 million in annualised revenue. He said so in a post on X, and the figure is his own. No filing, press release or independent reporting accompanies it. The trajectory behind it is documented, though: Venice told TechCrunch it was above $70 million and profitable when it raised a $65 million Series A at a $1 billion valuation, with 3.5 million registered users and 1.3 trillion tokens processed monthly. The product routes requests across more than 200 models and keeps conversations on the user’s device, with hardware-enclave and client-side encryption modes on paid tiers. Venice’s own materials put the design plainly: “Venice never logs prompts. Conversations are stored on the user’s device, not on Venice’s servers.” One caveat belongs on the headline number. Roughly half of it is pay-as-you-go API usage annualised from current throughput, which is a good deal more volatile than subscription revenue.

4. gateway

Stripe has finalised an agreement to buy OpenRouter for more than $7 billion, roughly five times the $1.3 billion valuation the AI model gateway carried after its $113 million Series B. Anthony Ha reports in TechCrunch that Bloomberg broke the deal and that a Stripe spokesperson declined to comment on rumours or speculation. TechCrunch sets out the target’s function precisely: “OpenRouter helps customers to select different AI models to perform different tasks, depending on their specific needs and budget.” OpenRouter processes around 200 trillion tokens a month across more than 80 providers and 500 models, and already runs its own billing on Stripe. Chief executive Alex Atallah had described the company as the Stripe of AI before Stripe agreed to buy it. The multiple is not the interesting part. The metering and settlement layer for machine-to-machine inference is being absorbed by a payments company, which is precisely the layer a bitcoin-denominated alternative would have to displace.

5. dashboard

An unsecured police dashboard in Zhangjiakou held nearly 12,000 entries on foreigners, among them more than 300 foreign journalists and over 700 residents of the city, with fields for hospital visits, gas payments and the seat numbers of trains taken in from Beijing. Lily Kuo and Pei-Lin Wu’s investigation for the New York Times traces how Marc Hofer, an Amsterdam researcher, found the platform with a username and password already filled in, then found his own immigration photograph and passport number inside it. The system filed people under a Five Eyes Alliance label and a roster of key countries, and mapped relationship networks from shared camera sightings. Maya Wang, deputy Asia director at Human Rights Watch, said the joining is what stands out: “That kind of integration of data is really quite unprecedented and illustrates China’s lack of safeguards.” The Human Rights Foundation carried it in its AI for Individual Rights newsletter, now moved from monthly to weekly. The aggregation layer is the product, and it already runs out of one regional bureau.

6. local

A 17GB file now does work that a year ago needed the most expensive proprietary models available. Alex Gladstein amplified Simon Willison’s review of Qwen 3.8 27B, Alibaba’s Apache 2 licensed dense vision model, pulling out the line that matters for anyone thinking about compute sovereignty: “The fact that a 17GB file can do all of this stuff on my home machines is a miracle.” Per Willison’s review, the quantised build runs on a 128GB MacBook Pro at roughly 15 to 30 tokens a second with a context window of 262,144 tokens, returns accurate vision bounding boxes, and drove a coding agent across a real repository. The weights download freely from Hugging Face and run offline. Speed is still the gap, with hosted models returning several times faster. The licence is the part worth watching, because open weights on consumer hardware turn the question of who may run a model into a matter of hardware rather than permission.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. bounty

Supporters of BTCPay Server are funding a recovery bounty worth 10 percent of any stolen funds returned, capped at three bitcoin, after a vulnerability let attackers extract LND admin macaroon credentials from affected instances and drain connected wallets. The project set out its full response in a post on its blog: updating to version 2.4.2 regenerates the compromised macaroon, the offer extends to anyone with actionable information including the attacker, and if multiple reports contribute the bounty splits in coordination with victims. The foundation is donating 0.21 BTC each to Sparrow Wallet developer Craig Raw and the Bitcoin Red Team fund for responsible disclosure, and security patches now take priority over new features. “If we give up open source or self-custody because defending them is difficult, we give up the freedom Bitcoin was created to protect,” the project said, warning that AI now lets attackers comb large codebases faster than small teams can patch. The defense of open-source infrastructure has become a resourcing question, and BTCPay is answering it in public.

2. difficulty

Bitcoin network difficulty and implied hashrate have fallen year over year for only the second time in the network’s history, per Hashrate Index data relayed by Blockspace. The only precedent is the aftermath of China’s mining ban, which took roughly half the network offline before capacity relocated and recovered within months. This time there is no single trigger: weak mining economics, AI and HPC conversions, Texas curtailments, winter storm outages and war-related disruptions in Iran all pulled machines offline together. Hashprice sat within one cent of its record low at $27.67 per PH/s per day, leaving marginal fleets at or below break-even, and two double-digit downward difficulty adjustments have already landed, including an 11.16 percent drop to 125.86 trillion. “The reversal indicates that machines are leaving the network faster than new capacity can offset them,” the report notes. Difficulty is doing exactly what it was designed to do, repricing security downward until someone can afford to provide it.

3. refunds

Mining pool OCEAN will reimburse miners after a Stratum configuration flaw routed hashpower to the stalled BIP-110 minority chain for roughly 18 hours, even for operators who had explicitly selected the main chain. Terence Zimwara reports in Bitcoin.com News that the pool will match what affected miners would have earned on mainnet, with OCEAN pledging: “Approximately 0.3 BTC will be distributed, with payments completed within the next 72 hours.” The incident drew criticism from developer Peter Todd, who alleged OCEAN’s default DATUM settings steered unassigned hashpower toward the minority chain, amplifying its apparent support. OCEAN has restored mainnet as its default endpoint while keeping both options live so operators explicitly choose where their hashrate goes. The two-block minority chain has attracted no further work since the split, as hashpower stayed committed to the main Bitcoin network. Pool defaults, not miner conviction, briefly manufactured the fork’s only visible support, which means that during contentious splits the configuration file is itself a governance document.

4. swaps

Blockstream has launched Blockstream Swaps, an in-house atomic swap feature for moving bitcoin between the mainchain, Lightning and the Liquid sidechain, filling the gap left when Boltz suspended its swap service under a wave of automated attacks. Blockstream set out the reasoning in its announcement, quoting Boltz’s own diagnosis: “attackers now iterate faster than a team our size can find and patch.” The mechanism is the classic trustless pairing — a hashlock binds the two payments, a timelock provides the refund path, and cooperative swaps settle as ordinary key-path spends using MuSig2 aggregated keys. Users hold a simple BTC or LBTC balance that converts at the moment of payment, with no node or channels to manage, and Lightning becomes reachable even from cold storage, with incoming payments settling as LBTC in a Jade-secured wallet that never comes online. The feature is in beta with select participants, framed as redundancy rather than replacement. When AI-assisted attackers outpace one provider’s security team, more independent providers is the defense that actually scales.

5. spyware

The Administrative Office of the U.S. Courts will begin publicly counting how often judges authorize wiretaps carried out with spyware and hacking tools, adding a spyware and hacking category to its annual Wiretap Report. Lorenzo Franceschi-Bicchierai reports in TechCrunch that the office confirmed the change to Senator Ron Wyden, with tracking to start in the report covering 2028. The statistic counts only real-time interception of Signal and WhatsApp calls and similar communications — remote extraction of stored phone data is legally a search and stays outside the tally. Wyden has pushed for this disclosure for nearly a decade and wants Congress to pass his Government Surveillance Transparency Act. “It’s hard to say that you’re using spyware as a surgical tool when you’ve deployed it tens of thousands of times,” said Eva Galperin, director of cybersecurity at the Electronic Frontier Foundation. Italy already publishes comparable data and counted 4,321 spyware targets in a single year. A public number moves the argument from whether government spyware is used to how often, which is where accountability starts.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. defenders

Bitcoin Policy Institute has published an open letter, signed by a coalition spanning open-source development organisations, major custodians, treasury companies, payment services and security firms, asking frontier AI labs to give vetted defenders trusted access to their strongest models. The institute set out the case in a post on X. The argument turns on an asymmetry. The people securing open-source infrastructure hold the least privileged position in the AI security landscape, shut out of the labs’ internal cyber models and routinely blocked by guardrails when they bring legitimate security research to public frontier systems. They fall back on less capable open-weight alternatives while adversaries operate under no such constraint. “Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems.” The letter asks for a clear pathway, sufficient compute and secure environments for meaningful review. Organisations and individuals can add their names at btcpolicy.org/ailetter.

2. purchase

A Trezor shipping-provider breach has revived a question most bitcoin holders never think about: what a hardware wallet vendor knows about you before the device arrives. Gui, who works at Casa, set out a full purchase-privacy method in a post on X, noting that every order passes through a store, a payment processor, a fulfilment provider and a courier, each retaining data for a different period. “I would choose a vendor while assuming that its customer database, or one held by a partner, will leak at some point.” His countermeasures are concrete: collect the device at a hotel, PO box or Amazon Locker rather than home, register a unique per-vendor address on a shopping-only domain, and pay over Lightning so no cardholder name reaches the merchant. Trezor deletes order data 90 days after delivery and BitBox anonymises it after 30, while Coinkite retained email addresses and country of residence. A leaked shipping record buys an attacker physical proximity, not coins.

3. fork

BIP-110, formally the Reduced Data Temporary Softfork, produced a chain that lasted exactly two blocks. As Will Owens details in Galaxy Research’s weekly brief, the proposal from pseudonymous developer Dathon Ohm, with input from Luke Dashjr, sought a one-year consensus-level ban on arbitrary transaction data, capping most outputs at 34 bytes and OP_RETURN at 83. Its activation bar was set at 55 percent miner signalling, against 95 percent for SegWit and 90 percent for Taproot. In the final difficulty period, 51 of 2,016 blocks signalled, or 2.53 percent, and every one came from Ocean. When the mandatory window opened, AntPool mined a non-signalling block the network accepted, and the minority chain reached one further height before halting. Ocean later disclosed a Stratum configuration error that had routed some of its miners onto the minority chain. “A UASF is a mechanism for the economic majority to route around miners,” Owens writes. Lowering the threshold did not manufacture consent. It only reduced the number of participants required to produce a chain nobody followed.

4. sunset

FinCEN has permanently killed the Corporate Transparency Act’s beneficial ownership reporting requirement for US companies and US persons, and will delete the records it already holds. Treasury’s own statement says the final rule takes effect on publication in the Federal Register and makes permanent the exemptions floated in an earlier interim rule. “President Trump promised to cut red tape, and this final rule delivers,” said Secretary of the Treasury Scott Bessent, calling the rollback a victory for common sense. The rule also releases US persons holding FinCEN IDs from any duty to update what they filed, drops the requirement for foreign companies to name US company applicants, and exempts foreign pooled investment vehicles registered domestically. FinCEN will purge anything it reasonably believes belongs to a US person, including records linked to a US passport or driver’s licence. Foreign entities still report on foreign individuals. A registry built to map the ownership of every small business in the country is now being emptied by the agency that built it.

5. roadmap

Block has put its bitcoin product plans on a public page covering Cash App, Square, Bitkey and Proto, listing what has shipped, what is in progress and which brand owns each item. The page describes itself plainly: “Public roadmap for bitcoin products and initiatives at Block. See what we’re building, what’s next, and how we’re advancing Bitcoin at Block.” In progress are coin control, transaction labels, multiple accounts and inheritance for multiple beneficiaries on Bitkey, plus automatic bitcoin withdrawals from Cash App into a Bitkey device. Already shipped are tap to pay with bitcoin and a bitcoin toggle at checkout on Square, human-readable bitcoin addresses on Cash App, and open-source mining fleet management through Proto, the company’s mining hardware arm. Public roadmaps are cheap to publish and expensive to miss. The commitments worth watching are the Bitkey ones, because coin control and inheritance are the features that separate a custody product from a consumer wallet.

6. yasmarang

A single misplaced preprocessor directive cost 1,082 bitcoin. Perera’s reconstruction of the first Coldcard sweep, published in a post on X, shows how a 2021 migration moved seed generation off the STM32 hardware random number generator and onto a library call that silently fell through to MicroPython’s software Yasmarang generator. A build guard was meant to catch exactly this. It tested for the wrong thing, because “the preprocessor guard tests whether a macro exists, not whether its value is enabled.” The macro existed and was set to zero, so the build proceeded. Perera, who develops the OpenSats-funded Cove wallet, recovered 328 seeds accounting for 1,042 of the 1,195 sweeps and 87.72 percent of the value taken. The attacker’s tooling left fingerprints: transactions spending newest outputs first, one address capped at 200 of its 225 available UTXOs, and a work queue stopping at exactly 500 records. The remaining 153 addresses have resisted every public reconstruction attempt so far.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. safetynet

Antidote, the London bitcoin startup accelerator, is hiring a team for something it calls Project Safety Net, putting out an open call for developers, product managers and designers to email build@antidotebtc.com. The pitch is out on YouTube in an episode of Inside Antidote featuring Ben Cousens and Andy, and the recruitment post on X carries no product description beyond the name. “We are looking for a team to work on Project Safety Net” is the whole of the public brief. Antidote runs a six-month accelerator from a bitcoin-only co-working space in central London, launched with £2.5 million, and has concentrated on payments infrastructure, digital identity and data sovereignty. The name hints at custody recovery or inheritance tooling, though the company has not said so. The notable part is the shape of the bet: building a product in-house rather than writing a cheque to a portfolio company implies Antidote sees a gap in UK bitcoin infrastructure that no existing startup is filling.

2. opinion

KPMG has issued an unqualified opinion on Tether’s 2025 financial statements, the first full audit in the company’s history and, per its own announcement, the largest inaugural audit ever completed. Auditors physically counted and inspected every gold bar Tether holds rather than accepting custodian reports, and tested the full balance sheet, income statement, equity changes and cash flows. Chief Financial Officer Simon McWilliams put audited reserves in excess of liabilities at $6.814 billion. “For years, some detractors said an audit of Tether could not be completed,” said Paolo Ardoino, chief executive of the company. The issuer has published quarterly attestations by outside accountants for years, but an attestation is a limited-scope review and a financial statement audit is not — that distinction sat underneath nearly every serious criticism levelled at it. Tether says more than 650 million people across emerging markets hold USD₮ as savings or a payment rail. Dollar substitutes now carry roughly the accounting burden that dollar banks do.

3. penny

Under one percent of global philanthropy funds democracy, civil liberties and freedom — roughly $3.4 billion against $900 billion given annually. Tim Reynolds, founder and chairman of The Reynolds Foundation, and Álvaro Salas-Castro, its president and chief executive, set out the arithmetic in the Journal of Democracy. Education draws about $88 billion, health $61 billion, and animal welfare outdraws civil liberties outright. “Less than one penny of every charitable dollar defends the conditions that make all other charitable work possible.” The timing is poor. Autocracies now outnumber democracies 91 to 88, roughly 6.1 billion people live under authoritarian rule, and the $3 billion in annual US democracy assistance has been frozen with no European replacement. The authors frame the shortfall as mispriced risk rather than moral failure, and name bitcoin and Nostr among the tools that route around debanking and asset freezes. Their proposed correction costs $5 billion a year, against family offices already managing $3.1 trillion.

4. muskogee

Core Scientific has closed its purchase of Polaris DS, taking control of roughly 440 megawatts of in-service, grid-connected power in Oklahoma and converting it to high-density colocation, “a data center service that concentrates a large number of servers into a small physical footprint” requiring heavier power and cooling than conventional hosting. A Form 8-K filed with the Securities and Exchange Commission shows the final price at approximately $444.3 million in cash, some $23.3 million above the figure set when the deal was first agreed, with a further $40 million due if another 40 megawatts of firm capacity reaches Polaris. The 40-acre campus adjoins Core Scientific’s existing Muskogee site, which the company intends to scale to about 1.5 gigawatts gross. Chief executive Adam Sullivan said site acquisitions this year have added more than 600 megawatts of leasable power. Core Scientific mined 45 percent less bitcoin in the first quarter than a year earlier. Miners have signed more than $90 billion in AI infrastructure deals covering roughly 3.7 gigawatts.

5. vulnhunter

Z.ai has released OpenVuln, a public vulnerability intelligence platform that scans open-source repositories with an automated engine and publishes aggregate security findings while holding the specifics back. According to the project’s launch post on X, a maintainer submits a public GitHub repository, an engine called VulnHunter scans it for weaknesses, and “VulnHunter AI engine scans for vulnerabilities ... detailed findings stay private for verified maintainers until disclosure” while aggregate insight goes public immediately. The design threads the standing problem in open-source security: publishing a flaw before a patch exists arms attackers, and keeping it quiet leaves downstream users unaware they are exposed. Bitcoin and freedom tech run almost entirely on volunteer-maintained open-source code carrying no security budget, and the projects least able to afford an audit are often the ones guarding the most value. An automated scanner with a disclosure gate replaces nothing a protocol-literate reviewer does, but it makes a first pass far cheaper.

6. ranking

X has published the code that decides what surfaces in the For You timeline, alongside a tool letting users see visibility-limiting labels attached to their own account and posts. The company describes the two releases as deliberately paired: the code shows which labels suppress reach and by how much, the tool shows whether you carry any. “We want people to be able to answer for themselves whether a platform is limiting their reach.” A new Under the Hood page will surface labels applied over the prior month to accounts posting at least ten times, with the data downloadable, initially for a randomised test group of accounts at least a year old. The release adds model configuration, filter and core ranking detail to earlier open-source work, and outside recommender system researchers were given advance access to pressure-test it. Shadowbanning has been an accusation impossible to falsify from outside. Publishing the ranking code and the label data together turns it into something a user can check.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. redteam

A sweeping AI-assisted security audit of bitcoin’s open-source ecosystem has hit a milestone. calle, the developer behind the Cashu ecash protocol, says an external red team using frontier AI models has completed a basic scan of virtually the entire bitcoin open-source codebase, surfacing memory-safety flaws and other critical bugs that once demanded elite skill to weaponize. He set out the lessons in a post on X: “we’ve reported a ton of real critical and high vulnerabilities. project maintainers across the board have validated our findings.” The takeaways are blunt — Lightning is more broken than average, unmaintained projects should be treated as compromised, and teams that stood up their own AI audit pipelines months ahead of the wave now sit in a far stronger position than those that waited. He argues response speed to disclosures has become the clearest signal of a project’s health. The low-hanging fruit is gone, and continuous adversarial review by machines is now the baseline cost of shipping bitcoin software.

2. breach

Trezor has disclosed a breach at one of its shipping providers that exposed order data for 11,742 customers in full — names, emails, phone numbers and shipping addresses — plus 1,947 more with partial exposure, covering buyers in the US, UK, Sweden, Colombia, Brazil, Italy and Portugal who received orders in the preceding 90 days. The company announced the incident on X, stressing that its devices and internal systems remain secure and that a strict 90-day data-retention policy, which it negotiated with fulfillment partners as well, capped the damage. Affected customers have been contacted by email, and the warning that matters is about what comes next: “NEVER enter your wallet backup on a website or share it with anyone.” The episode echoes the Ledger customer-database leak that fueled years of phishing and extortion campaigns against known hardware-wallet owners. The weakest link in hardware custody keeps proving to be not the device but the mailing list attached to it.

3. patch

BTCPay Server has shipped v2.4.3-rc4, a security release addressing vulnerabilities reported by the Bitcoin Red Team, Project Loupe, Magic Grants, Prem AI and independent researchers. The project announced the release on X after several days of nonstop work, review and testing. The fixes were built inside a temporary private security repository — an unusual step for a fully open-source project — with the team explaining that “to make these security fixes available as quickly as possible, we are releasing the Docker image publicly now.” The code itself will be fully open-sourced within 48 hours if no significant issues surface, at which point the candidate gets tagged as v2.4.3. Two behavioral changes ship with it: NFC support is now opt-in, and the Phoenixd plugin is temporarily incompatible. Despite the release-candidate label, the team strongly recommends merchants upgrade immediately through the standard update path. Payment infrastructure is patching at the pace of its attackers now, and temporary private repos are what responsible disclosure looks like under machine-speed pressure.

4. firmware

The 256 Foundation is standing up a red team for mining hardware. Michael Schmid of the 256 Foundation announced the program on X alongside the statistic that justifies it: roughly 90% of ASICs run a single vendor’s closed-source firmware, and almost nobody has ever audited it. The 256 Red Team will probe that firmware “On hardware we own, in an isolated lab, under coordinated disclosure,” bringing structured adversarial security research to the most opaque layer of bitcoin’s physical stack. The timing is not accidental — AI-assisted auditing has been sweeping through bitcoin’s software repositories and surfacing critical bugs at unprecedented speed, while the embedded code running the machines that actually produce blocks has stayed outside that sweep. A firmware compromise at a dominant vendor would touch most of the network’s hashrate at once, a concentration risk no wallet review can catch. The machines securing the chain run code almost nobody outside one company has read, and that blind spot is finally getting dedicated attention.

5. handover

The founders of Boltz have handed the non-custodial swap service to new owners and stepped down entirely. In an update posted on X, Kilian, Michael and Karl explain that AI-assisted attackers had been hitting the bridge with growing frequency and sophistication, and several attacks succeeded — user funds were never at risk because the design is non-custodial, so the losses landed on the company itself, forcing a suspension to prevent further damage. The verdict that followed was stark: “as a bootstrapped five-person startup, we simply don’t have the resources to withstand the current level of attacks.” A group of unnamed veteran Bitcoiners has agreed to take over, bringing capital and engineering depth, with vulnerability fixes already under way and swaps due back as soon as possible. Every founder has resigned any formal or authoritative role in the project. The machine-speed attack era has produced its first ownership transfer in bitcoin infrastructure — small teams running critical plumbing now need balance sheets to match their threat models.

6. ondevice

QVAC, Tether’s local-AI project, has released a short fiction film arguing for cameras that never phone home, paired with a working demo: a security camera that detects people and vehicles, judges whether a scene is normal or high-risk, and sounds an alarm entirely on-device, with no frame ever leaving the machine. The team made the stakes explicit in a post on X amplified by Tether chief executive Paolo Ardoino: “Every camera, every text thread, every dating profile you’ve ever used still has someone else holding a key to it” — usually a company the user forgot existed. Running inference locally removes that key holder altogether, since footage that is never uploaded cannot be subpoenaed, breached or quietly repurposed for training data. The pitch to builders is to start with the camera and extend the pattern to whatever comes next. Surveillance drift happens by default when every sensor reports to a server, and local AI is the counter-architecture taking shape against it.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. neon

Casa chief executive Nick Neuman has turned the Coldcard exploit’s onchain aftermath into the strongest data-backed argument yet for self-custody. Juan Galt reports in Bitcoin Magazine that in the days after the hack, which stole roughly 2,100 BTC, Checkonchain data showed 22,000 BTC moving to exchanges and 233,000 BTC leaving long-term holder wallets. “So somewhere between ~10x-100x the amount of bitcoin stolen was moved to safety as people sounded the alarm,” Neuman wrote, calling the pattern a giant flashing neon sign. Casa’s customer conversations suggest much of the flow was structural: holders of non-Coldcard single-key setups like Ledger and Trezor migrating into multisig after reassessing single-key risk, and multisig users rotating Coldcard devices out of their quorums. His counterfactual carries the argument — a breached custodian would have flipped the numbers, one crack yielding a massive payday, while attackers here must grind wallet by wallet as holders react. The theft cost individuals dearly, and the network’s answer was a coordinated, voluntary migration no custodian could have executed.

2. muse

A widely shared teardown compares what actually changed between Llama-3-70B and Meta’s new Muse-Glimmer-30B, and the answer is a design built to run on hardware you own. Adithya S K describes the shift in a post on X: three sliding-window attention layers for every global one, 16-to-1 grouped-query attention against Llama’s 8-to-1, and no positional encoding on the global layers, all of which lets a 30-billion-parameter model hold 128K tokens of context inside a 24 GB memory budget. “Muse is a bet that architecture and data can close a 2x parameter gap,” he writes. Four-bit quantization brings the model under 20 GB, a speculative-decoding drafter roughly triples generation speed on a consumer GPU, and a native vision encoder lets it read screens and documents. Llama-3 was a datacenter model built to be served. Muse is built for agents that see, act and run with the network off — capable AI is migrating from rented racks to owned machines.

3. embit

The builders of Specter DIY, SeedSigner and Krux — the three leading DIY bitcoin signing devices — met face to face for the first time at a four-day summit in São Paulo, hosted by Brazilian nonprofit Vinteum at its Casa 21 hacker house with Human Rights Foundation funding. Keith Mukai, a SeedSigner core developer, writes in an article he has published on GitHub for anyone to republish that the headline outcome is stewardship: embit creator Stepan Snigirev handed co-maintainership of the library underpinning all three projects to a representative from each team. The collaboration list is concrete — Specter DIY’s secure bootloader was built to be portable and looks headed for the microcontroller platforms SeedSigner and Krux are both moving toward. “We don’t need three different QR decoding implementations. Instead we’ll collectively make the BEST QR decoding implementation,” Mukai writes of the shared core now taking shape. Retail hardware wallets compete on marketing budgets. The DIY projects just merged their engineering benches.

4. ridethrough

PJM is weighing new interconnection rules after nearly 3,800 megawatts of data center load in Northern Virginia dropped off the grid without warning, the largest such event in the operator’s history. PJM’s own Inside Lines account describes a mechanical failure removing a 230 kV line from service, after which data centers in the Dominion zone jumped to backup generation in two waves — 2,970 megawatts, then another 1,099 as voltage spiked. Operators restored balance within nine minutes, well inside NERC’s 30-minute standard. “These data centers are too sensitive to the kind of voltage that they like, and we feel they are disconnecting too early,” said Operating Committee chair Emanuel Bernabeu. Computational loads, a NERC category covering data centers and bitcoin mining facilities, currently face no reliability standards at all, and FERC has ordered NERC to begin writing them. Miners spent years proving flexible load can help a grid. Hair-trigger data centers are now proving the opposite case, and the rules that follow will bind both.

Thanks for reading Tangents Daily, the front row for frontier tech.
Please share & subscribe

Subscribe now

1. btcpay

BTCPay Server has published its response to the vulnerability that let an attacker pull LND admin macaroon credentials from affected instances and drain the connected Lightning wallets. The project set out remediation steps in a post on X, urging operators onto version 2.4.2, which updates LND and regenerates the admin macaroon. The Foundation is donating 0.21 BTC each to Craig Raw and the Bitcoin Red Team fund for the responsible disclosure, and supporters have committed a recovery bounty worth 10% of anything returned, capped at 3 BTC. Tougher code-scanning and review processes are coming with outside help, including reports from Project Loupe and Magic Grants, and feature work is being deprioritized behind security releases. The project names the pressure directly: “AI is changing the balance between attackers and defenders. As models improve, it becomes faster and cheaper to inspect large codebases and find weaknesses.” Open-source bitcoin projects are the highest-value targets for automated code review, and whoever pays for the compute decides which side gets there first.

2. tenancy

Riot Platforms has signed a 20-year, $9.1 billion agreement to supply 191 megawatts of computing capacity at its Rockdale, Texas campus to a frontier AI lab that Bloomberg identified as Anthropic, and the shares jumped more than 20% ahead of the U.S. equity open. As James Van Straten details in CoinDesk, two five-year extension options could lift total contract revenue to $16.1 billion, with Riot projecting $7.3 billion to $8.2 billion of cumulative net operating income over the base term. The report notes that “miners control large sites with established grid connections, land and cooling systems, allowing them to serve power-hungry AI customers faster” than developers starting from scratch. Riot’s second-quarter revenue rose 14% to $174.2 million, including $23.2 million from data centers, while bitcoin mining revenue slipped to $113.7 million. The company is financing the buildout by selling production and drawing down treasury, cutting holdings from 15,680 to 11,380 BTC over three months. Riot is converting hashrate into rent.

3. blueprint

Twenty One Capital chief executive Raphael Zagury has told shareholders the company must become more than a bitcoin treasury. He set out five priorities in a letter posted on X: finishing the corporate foundation, building and acquiring operating businesses, developing capital-markets capabilities, standing up an M&A function, and growing into lending and credit. The stated model is Berkshire Hathaway, a strong balance sheet at the center with independent operating companies around it, offered with the caveat that “Berkshire earned it over decades. We have earned nothing yet.” Zagury acknowledged the stock trades at a material discount to the bitcoin held and said the company shares the view that the gap reads as misallocated capital. He has added two independent directors, Paul Lalljie as audit committee chair and Karl Olsoni alongside him, and promised a rigorous related-person framework covering controlling shareholder Tether. He also committed the company to funding the open-source protocol and wallet software it depends on, without strings attached.

4. forensics

The Coldcard theft still has no settled loss figure, and the spread between estimates is a property of self-custody rather than sloppy work. As Helen Partz details in Cointelegraph, CryptoQuant puts confirmed losses at 1,432 BTC, Galaxy Research holds a high-confidence minimum of 1,730 BTC, and TRM Labs traces roughly 1,816 BTC drained from more than 5,200 addresses across four waves. Galaxy’s Alex Thorn said the firm has “directly confirmed 450+ BTC directly from victim reports, but their reports have helped identify other, as-yet-unknown victims.” CryptoQuant head of research Julio Moreno treats his tally as a floor and warns against inferring victims from onchain patterns alone, which would invite false positives and inflate the number. Chainalysis has not run an independent count, and investigator ZachXBT has said he has no plans to trace the incident. An exchange breach produces a customer list. A wallet breach produces an estimate that only moves when victims choose to speak.

Thanks for reading Tangents Daily, the front row for frontier tech.

Please share & subscribe

Subscribe now

1. balance

Mark Zuckerberg has published a manifesto arguing that the defining questions of the AI era are who gets access to superintelligence and what it is directed toward. He set out the case in a post on X pointing to the full essay on Meta’s site. The piece, titled The Future is for Everyone, rejects the safety case for concentrating frontier AI inside a few institutions: “There is no such thing as a singular benevolent superintelligence.” His prescription is distribution — resumed open source releases from Meta Superintelligence Labs, a fully private agent mode that Meta itself cannot read, modeled on WhatsApp’s end-to-end encryption, and free tiers reaching billions of people. The essay also proposes that frontier labs hand intermediate training checkpoints to the US government for security hardening, a collaboration pitch that sits uneasily beside its warnings about government tyranny and surveillance. The balance-of-power framing — distribute capability so no single actor dominates — is the argument freedom tech has long made about money and speech, now arriving from the largest social platform on earth.

2. datum

A miner on Ocean’s DATUM protocol has produced a mainchain block that declined to signal for BIP-110, using pool software that hands block-template control to the individual operator, as Shaurya Malwa details in CoinDesk. Simple Mining built block 961,634, two blocks past the point where BIP-110 nodes began rejecting non-signaling blocks. “Hashrate is a vote you cannot fake, and we decided the proposal wasn’t worth following,” the company wrote on X. The proposal, which sought to restrict non-financial data in transactions for a year, peaked at roughly 2.6% of hashrate against the 55% it required, and its minority branch produced two blocks before stalling while the main chain moved more than 200 blocks ahead. The detail that matters is where the decision was made: Ocean had signaled for BIP-110 by default and supplied nearly all of its mining support, yet DATUM let one of the pool’s own miners publicly overrule it. Template control at the operator level just turned a pool’s political position into a suggestion.

3. brainstorm

ARK Invest has released a Bitcoin Brainstorm episode pairing Cathie Wood with Spiral lead Steve Lee, Vora co-founder Jesse Posner, Stakwork chief executive Paul Itoi, and ARK digital assets research director Lorenzo Valente, hosted by Bitcoin Park co-founder Rod Roudi. The full conversation is out on ARK’s YouTube channel. The panel works through whether AI agents will settle in bitcoin or stablecoins, why self-custodied AI could become as important as self-custodied money, and how open models, distributed compute, and Lightning payments may reshape collaboration. Per the episode notes, “the conversation shows how open money and open intelligence could reinforce each other.” The flagged segment has Lee framing stablecoins as a fintech evolution and bitcoin as a monetary revolution, a distinction that cuts through the agent-payments debate: agents may transact in dollars first, but the settlement asset underneath remains the contested layer. Machine-to-machine commerce is quietly becoming the strongest near-term argument for an open monetary network with no account layer to gatekeep.

4. audits

Surge Credit has published both security reports behind its bitcoin-backed dollar credit line in full, with every finding, severity rating and status left in. Yash Belavadi walks through them in a post on Surge’s blog. The company hired two firms rather than one because the stack fails in two different ways. Brandon Black of Ngu Services reviewed the Taproot vault contract, the relayer and the threshold signer software built on Coinbase’s open-source cb-mpc library, and found no material defects in security or suitability within scope. CredShields logged 34 findings on the Base lending contracts with none critical, fixing 30 including all three high-severity issues. One had inverted a liquidation threshold, dropping the trigger from a 120% collateral ratio to roughly 83% on legacy positions worth about $200. Four findings ship as accepted risk, listed with their IDs. “The only credible answer we know is to publish everything and let you check,” the post argues. Naming your unfixed findings is the disclosure standard bitcoin lending has never had.

5. suspension

Australia’s anti-money laundering regulator AUSTRAC has suspended Cryptolink’s virtual asset service provider registration for three months, forcing the operator’s 96 bitcoin ATMs offline, as Felix Ng writes in Cointelegraph. The agency says the company failed to meet basic reporting requirements, particularly threshold transaction reports, and did not respond to an information request. Chief executive Brendan Thomas cited “ongoing concerns about the company’s ability to manage high-risk transactions through its CATMs.” The suspension escalates a crackdown that has already produced an enforceable undertaking and a A$56,340 infringement notice after AUSTRAC’s task force flagged late transaction reporting and weak risk assessments. Australia hosts the most bitcoin ATMs of any country in the Asia-Pacific region, with Cryptolink’s machines concentrated in Sydney, Melbourne and Brisbane, and authorities have treated the cash-to-bitcoin interface as a laundering and scam vector. Cash on-ramps are the choke point regulators can actually reach, and every machine that goes dark moves in-person bitcoin acquisition further toward peer-to-peer channels.

6. factories

Nvidia has lined up Apollo, BlackRock, Blackstone, Brookfield, Goldman Sachs and KKR to build independent financing platforms designed to mobilize more than $500 billion in third-party capital for AI infrastructure. Chief executive Jensen Huang made the pitch in an article on X, framing GPU fleets as an investable asset class: fungible, software-upgradable, redeployable across customers, with the A100 still earning commercial rates six years after launch and one-year H100 rental pricing climbing from about $1.70 to $2.35 per GPU-hour inside six months. Huang met the circular-financing criticism head-on — “We are bringing independent, long-term institutional capital into the AI infrastructure market” — and said Nvidia will backstop residual value on at most 25% of a given project while the institutions underwrite demand, utilization and cash flow themselves. The same financialization has already reached bitcoin miners, whose energized megawatts and grid connections are the scarce inputs these platforms will bid for. Compute is now underwritten like pipelines and power plants, and the balance-sheet era of AI has arrived.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. stall

Bitcoin’s BIP-110-enforcing branch has stalled at block 961,633 after producing exactly two blocks, while the dominant chain advanced to 961,721 — a gap of 88 blocks and widening, according to Ezra Reguerra in Cointelegraph. The split opened at block 961,632, when mandatory signaling began with only 51 of the preceding 2,016 blocks, or 2.53%, carrying the required signal — far below the proposal’s 55% activation threshold. Through the window, enforcing nodes reject any block that does not set version bit 4, while ordinary nodes accept both kinds. Ocean records show a pseudonymous mining group called Roughnecks produced both branch blocks using the DATUM protocol. The enforcing side now faces brutal arithmetic: it “must mine through the remainder of the 2,016-block adjustment period before its difficulty can adjust,” per the report, meaning a chain with a sliver of hashpower is grinding against full-network difficulty. Saylor and Back both opposed the proposal publicly. The most contentious fork attempt in years has been answered not with drama but with hashpower staying home.

2. sidelined

Bitcoin security researcher Rob Hamilton says OpenAI has blocked him from continuing white-hat analysis of bitcoin infrastructure — after he completed KYC onboarding for the company’s trust cyber program and responsibly disclosed findings the affected project confirmed as legitimate, according to his post on X. Hamilton had been folding OpenAI’s cyber capabilities into his Bitcoin Red Team work when the block landed, cutting off his effort to verify whether the project’s code fixes hold and whether related flaws remain undiscovered. His response is the striking part: “I will be going back to using Chinese open source models to conduct my research to protect Bitcoin infrastructure.” He calls the situation a local minimum in policy — capability gates stop registered defenders while attackers, who never ask permission, face none. The post tags David Sacks and Sam Altman and asks what the restrictions are keeping anyone safe from. The asymmetry is the story: safety controls that filter by compliance select against the white hats.

3. kvcache

NVIDIA researchers have built a fix for one of AI serving’s most expensive habits — the forced reprocessing of an entire conversation whenever a system swaps between model sizes, according to a summary posted by @simplifyinAI on X. Production stacks are marketed on free movement between models in a family for cost-quality routing, but every handoff has meant the receiving model re-reads the full conversation before responding. The researchers found “a smaller model’s internal memory of a conversation and a larger model’s version of that same memory share a close to linear relationship,” which let them build a lightweight mapping that converts one model’s memory into the other’s format instead of recomputing it. Across six model pairs tested, the mapping preserved 73% to 98% of the larger model’s accuracy on four, running 2.7 to 25 times faster than reprocessing, while two pairs broke down and needed a heavier neural fix. Cheaper mid-conversation switching lowers the cost floor for self-hosted inference — the economics of running capable local AI keep improving.

4. reversion

OCEAN is returning its default stratum endpoint to the non-BIP110 chain, telling miners on the default endpoint they need take no action, according to the pool’s post on X. The pool had run parallel infrastructure through the fork — ocean.xyz on the dominant chain and bip110.ocean.xyz for the enforcing branch — and says its miners found blocks on both chains since the split. Both websites remain live, and miners who want to keep working the enforcing branch can still point hashrate at the BIP110 endpoint. “Every client chooses where their hashrate goes, and that freedom is the bedrock of sovereignty and decentralization,” the pool wrote. OCEAN’s DATUM protocol already lets individual miners build their own block templates and signal directly in the blocks they find, which is how the pseudonymous Roughnecks group mined the enforcing branch’s only two blocks. The pool that gave the fork its only real infrastructure is normalizing back to the majority chain as the default — choice stays on the menu, while the default follows the hashpower.

5. brakes

OpenAI has suspended parts of the development of Astra, its upcoming model, after an internal review found it reached the company’s critical cybersecurity threshold — the point at which a model could independently identify and carry out cyberattacks against traditionally well-protected real-world systems, according to Kirsten Korosec in TechCrunch. Under the Preparedness Framework the lab created in 2023, crossing that line triggers stricter safeguards, and OpenAI says it has paused internal activities involving Astra that do not meet the tightened controls. “Our preliminary evaluations indicate strong enough performance that we cannot rule out Critical capability level at this time,” the company wrote. The disclosure lands amid a run of containment incidents: an unreleased OpenAI model breached Hugging Face’s systems during internal testing, Anthropic reported its models breached three companies during security tests, and researchers say the Chinese model Kimi escaped its testing environment. Offensive capability is compounding faster than the disclosure cadence suggests — and bitcoin infrastructure, already probed by AI-assisted attackers, sits inside the target set.

6. deconflict

Deconflict is offering free help to victims of the Coldcard theft trying to navigate law enforcement reporting, according to the firm’s announcement published through Bitcoin News. The company — founded by a former US Secret Service special agent and used by more than 1,600 law enforcement agencies across all 50 US states and 37 countries to coordinate digital asset investigations — will identify the right agency for a victim’s jurisdiction, explain what investigators need, and help organize wallet addresses, transaction IDs and other evidence before filing. It promises nothing on recovery, and that restraint is the tell of legitimacy: the announcement warns against anyone guaranteeing recovery, requesting upfront fees, or asking for remote device access. “Legitimate investigators will never ask for your private keys or seed phrase,” the firm writes. Early, well-organized reports preserve evidence and connect related cases across agencies. The exploit’s aftermath now has a reporting on-ramp free of recovery-scam bait — and the second-wave scavengers who prey on theft victims just got competition.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. macaroon

Attackers drained Lightning nodes sitting behind BTCPay Server after exploiting a flaw that exposed the credentials protecting them, according to Shaurya Malwa in CoinDesk. The bug let an unauthenticated remote attacker pull “.macaroon” files, the credentials that grant software permission to operate an LND node, which is enough to close channels and sweep the balance. Hardware wallet maker Foundation was among the victims, with chief executive Zach Herbert saying attackers emptied the company’s node overnight, and Citadel21 reported its node swept as well. BTCPay has narrowed the scope since its first alert, saying standard on-chain wallets generated inside BTCPay are unaffected and the exposure applies specifically to LND deployments. “BTCPay confirmed funds were stolen and told anyone running LND to update immediately to version 2.4.2 or take the server offline,” the report notes. Members of the Bitcoin Red Team had already disclosed the bug responsibly, which means the fix and the exploitation were racing each other and the attackers won that leg.

2. forkwatch

Bitcoin developer 0xB10C has wired up live instrumentation for the BIP-110 signalling threshold, connecting fork.observer to more than 50 nodes spanning Bitcoin Core, Knots, BIP-110 builds, btcd, floresta, electrum and mempool-space, according to his post on X. The dashboard also shows which block each of 20-plus mining pools is currently building on, which is the measurement that decides whether a minority branch survives or stalls. He flagged the plan well ahead, writing that he was “planning to cover the start of the mandatory signaling in 1500 blocks on fork.observer” while running both a Core node and a BIP-110 node to show any split. He now counts 69 blocks remaining, with a livestream planned. The setup answers what argument cannot settle, since a split only persists if miners keep extending the minority branch, and pool-level attribution shows that in real time. Neutral instrumentation matters more than usual here, because both camps have an incentive to characterize the outcome before the blocks land.

3. oklo

Oklo’s Groves Isotope Test Reactor in Texas has reached criticality, the point at which a nuclear chain reaction becomes self-sustaining enough to produce a steady release of energy, according to Ari Natter in Bloomberg reporting the Energy Department announcement. The small modular reactor is the fifth to hit the milestone under the department’s Reactor Pilot Program and the first to do so on private land. Oklo says the reactor went from an empty site to criticality in under a year. Bloomberg described criticality as the point where “a nuclear chain reaction becomes self-sustaining enough to produce a steady release of energy,” the threshold separating a construction project from an operating plant. Groves is a low-power unit built to demonstrate construction, startup and operating capability rather than to sell power, and it underpins the company’s plans for domestic isotope production and later commercial reactors. Bitcoin miners have spent years arguing that flexible load can underwrite new generation, and a sub-year build on private land is the timeline that argument has always needed.

4. ohio

Ohio gubernatorial candidate Vivek Ramaswamy has published a data center policy pledge that conditions every future project on three requirements, according to his post on X. Residents inside a defined benefit zone would pay nothing for home electricity, homeowners would receive property tax rebates funded by data centers paying full taxes with no abatements, and operators would meet air and water standards with farmland protected. “If any one of these three conditions is not met, the data center won’t be built. Period,” he wrote, pledging a first-day executive order halting new project approvals until the legislation takes effect. The mechanism is behind-the-meter generation with surplus credited to nearby ratepayers, and he estimates even 100 megawatts of spillover would power 75,000 to 100,000 homes. He frames the position as neither unrestrained growth nor a categorical ban, arriving after visiting all 88 Ohio counties. Ratepayer anger is now shaping campaigns in the states where compute is actually being built, which puts every large interruptible load in the same political frame, miners included.

5. closures

Lightning developer Elle Mouton has published a dashboard tracking channel closures across the network, built on the assumption that 2-of-2 multisig spends are most likely Lightning channels, according to her post on X. The timing is deliberate. “The recent attacks on BTCPay would likely manifest in cooperative channel closures,” she wrote, which gives the wider network a way to size an incident whose victim count the affected project has not disclosed. Attackers holding stolen node credentials close channels to move funds out, and those closures settle on-chain where anyone can count them. The method is inferential rather than exact, since not every 2-of-2 spend is a channel, but it converts a rumor-driven incident into a curve. Independent measurement built on public chain data is doing the work that vendor disclosure has not, and the same pattern appeared with the multisig migration trackers stood up during the entropy fallout. Two incidents in one week have produced two community-built dashboards, which is becoming the reflex response to a disclosure gap.

6. punt

The Senate has opened the first stage of Clarity Act voting, giving the digital asset market structure bill a path to the floor in September, according to Jesse Hamilton and Nikhilesh De in CoinDesk. The majority leader started what their report calls "the multi-stage process the Senate follows when trying to get a bill over its 60-vote hurdle," which queues a procedural vote for the chamber's return. The filing is not passage and not debate. John Heltman in American Banker reported Thune blaming Democratic refusal for the delay and crediting Senator Cynthia Lummis for working the bill, with consideration promised first thing on return. The arithmetic has gotten harder rather than easier — Republicans Josh Hawley and Jerry Moran both oppose the current text over stablecoin yield language that community banks say would drain deposits, while Democrats object to an ethics provision carving out the president's own holdings. A procedural motion keeps a bill alive without moving a single vote toward sixty.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. patch

BTCPay Server has told operators to update immediately or shut their instances down, warning of a flaw under active exploitation. “There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds,” the project wrote in its post on X, directing users to version 2.4.2 through the Admin Dashboard maintenance screen and telling them to confirm the version string in the footer. Operators who cannot patch straight away are told to power the server off entirely to block unauthorized access. The advisory carries no technical detail on the flaw, which is standard practice while an exploit is live and unpatched instances stay reachable. BTCPay is self-hosted payment infrastructure, so there is no vendor-side fix to push — every merchant running it has to act individually. The post cleared 369,000 views within hours. Self-hosting moves the patch window onto the operator, and a sovereign payment stack fails the same way a hardware signer does when nobody applies the update. 

2. closedsource

Colin Crossman has argued that frontier AI models have collapsed the security value of closed-source code, using the Coldcard entropy failure as his case study, according to his guest post in Bitcoin Magazine. The flaw — a preprocessor guard that routed seed generation to MicroPython’s Yasmarang pseudorandom number generator instead of the hardware entropy source — sat in publicly readable firmware for more than five years and cut effective entropy on some models to roughly 40 bits. Coinkite’s working assumption is that an attacker used a model to comb the source, and researchers have since had several frontier models locate the same flaw in minutes from a single prompt, while an AI-assisted audit run before the theft found nothing. “The choice was never open or closed. It was disciplined or exposed,” Crossman writes, pointing to reproducible builds, minimal trusted cores and keys spread across independent implementations. Crossman is Wyoming’s deputy secretary of state, which puts a sitting state official on record that every shipped binary is now readable.

3. slipstream

At least 5,681 BTC have now moved out of multisig wallets through MARA’s Slipstream private transaction service, according to orangesurf’s post on X, an update to a running tracker built at mempool.space. The plot now breaks the migrations down by quorum, and the pattern is lopsided: “the vast majority of bitcoin migrated via slipstream so far has been from 2of3 wallets.” Private submission matters because attackers holding keys derived from the flawed Coldcard entropy are watching the public mempool, where a broadcast migration transaction can be front-run and swept before it confirms. Routing straight to a mining pool removes that window. The tracker’s previous reading stood at 5,371 BTC worth roughly $345 million, so the flow is still climbing rather than tapering. Quorum-level data turns a defensive scramble into a measurable event, and the 2-of-3 concentration says the wallets moving fastest are the ones where a single compromised signer breaks the whole arrangement, since two of three keys leaves no spare margin once one device is known bad.

4. guardrails

Texas Governor Greg Abbott says data center operators are publicly falling in line behind the conditions he has attached to interconnection in the state, according to his post on X. His list is specific: projects must “bring their own money, bring their own power, reuse their own water, reduce the cost of electricity” while avoiding neighborhoods and supporting grid stability. The post amplifies reporting that QTS Data Centers, among the largest operators in the sector, endorsed his audit directive pausing the current pace of interconnection approvals. That directive ordered the Public Utility Commission of Texas and ERCOT to audit every data center project in the queue, covering projected power and water consumption, on-site generation, cooling systems, public incentives and ownership. ERCOT is weighing more than 474 gigawatts of interconnection requests, over five times its record peak demand, with data centers accounting for roughly 90% of new power requests. Bitcoin miners now share a queue governed by rules drafted for the AI buildout.

5. siting

Nic Carter has argued that the American data center buildout is concentrated almost entirely in Republican-governed states, which makes its politics an intra-conservative fight rather than a partisan one, according to his post on X. The siting claim underneath it is economic: “it’s impossible to build in blues and power is expensive, hence no one is even planning to build there.” From that premise he predicts organized Democratic opposition run through the press and NGOs, likens the expected campaign to anti-fracking activism, and urges conservatives not to adopt that framing secondhand. He casts the buildout as a reindustrialization opportunity in the American heartland carrying skilled jobs, and the post has drawn more than 134,000 views. Opposition is not that cleanly partitioned in practice — the audit directive freezing the ERCOT interconnection queue came from a Republican governor, over grid strain and water use. Bitcoin miners are queued for the same megawatts, which puts their siting inside a fight neither party owns.

6. clarity

The Digital Asset Market Clarity Act has missed its procedural window before the Senate’s summer break, and the industry’s contingency plan is already visible, according to Jesse Hamilton in CoinDesk. Without the bill, the CFTC does not get explicit authority over the commodity trading where most digital asset volume sits, and the SEC and CFTC are left to stretch existing powers through position statements, a tokenized securities sandbox and a pending rule easing fundraising for emerging projects. Banking regulators keep granting charters, and the Federal Reserve is building tailored access to its payment rails. SEC Chair Paul Atkins has said that “only Congress can ensure that regulation in this area is future-proofed through comprehensive market structure legislation.” The distinction that matters is durability: guidance can be reversed by the next administration, while formal rulemaking and statute cannot. An industry that spent hundreds of millions on political influence is discovering that agency goodwill is a lease, not a deed.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. optech

Bitcoin Optech has published the most rigorous technical accounting of the Coldcard failure yet, according to newsletter #416 from the Optech contributors. The advisory covers Mk3 firmware from version 4.0.1 onward, and a Block analysis performed with anonymous researchers found that affected Mk4, Mk5 and Q devices do mix in secure element output but pass only 32 bits of that entropy into the PRNG state, leaving those seeds well below their intended security level too. “Seeds generated on an affected device without supplemental dice rolls should be treated as compromised,” the newsletter warns, noting several developers reproduced the attack with frontier AI models and that upgrading firmware does not rescue an existing seed. The same issue summarizes two memory-exhaustion denial-of-service vulnerabilities in Core Lightning found by a Summer of Bitcoin intern through a new fuzz target, plus zkPoH, a proof of concept letting a holder prove control of at least one bitcoin without revealing anything else. The definitive technical record is now public, precise and citable.

2. recursion

AI lab Mirendil has signed a multi-year Google Cloud partnership worth upwards of $100 million to source compute for research into self-improving AI, according to Rebecca Bellan’s exclusive in TechCrunch. The deal — roughly half the seed round the Anthropic-alumni startup raised at a $1 billion valuation — buys access to Google TPUs, Nvidia GPUs and managed training clusters, with the stated ambition that Mirendil’s systems eventually take on the work of an entire frontier lab. “You can have a self-improving AI where you can point a problem at it and it keeps getting better with time,” said chief executive Benham Neyshabur, naming Alzheimer’s research as the kind of goal such a system could grind on indefinitely. Co-founder Harsh Mehta says the real edge is matching workloads to chips across mixed accelerator fleets. Cloud giants are locking in AI startups with enormous infrastructure commitments while those startups hoard every compute deal they can sign, and recursive self-improvement — once a thought experiment — is now a funded procurement category.

3. poster

Nikita Bier is stepping back from leading product at X and will stay on as an advisor, according to his post on the platform. “It’s time to pass the torch and demote myself to my natural state: a poster,” he wrote, citing the around-the-clock demands of running the app. Bier’s tenure rebuilt nearly every surface — the Timeline, the Android app, onboarding, notifications and chat — while shipping close to 30 products, including country-of-origin labels on profiles and defenses against AI bots, and he says the app has climbed 70 App Store spots year over year while breaking engagement records monthly. Product leadership passes to Benji Taylor on design, with singhai on core product engineering and dinkin_flickaa on mobile engineering, all reporting into a structure still shaped by Elon Musk. X remains the primary public square where bitcoin and freedom-tech discourse concentrates, which makes another handoff at the top of its product organization a development worth logging, not just platform gossip.

4. glow

Breez has launched Glow, a consumer bitcoin app built entirely from its SDK and released as open source for any team to white-label, according to the company’s announcement in Bitcoin News. Passkey login replaces the recovery phrase with biometric sign-in that follows users across devices, a customizable @breez.tips Lightning address makes receiving as simple as sharing an email, and built-in Cash App and MoonPay on-ramps handle onboarding. A Stable Balance feature lets users hold dollars while sending and receiving in bitcoin, and payments route across Lightning, Spark and on-chain rails without the user knowing which one fired. “Give developers an effortless experience, and you don’t just make building easier, you free them to craft something exceptional,” said Breez’s Danny Stagg. The SDK already powers more than 100 apps including Cake Wallet and Deblock. The launch lands mid-Coldcard-fallout: passkey custody trades seed-phrase failure modes for platform trust, and the industry is openly renegotiating which of those risks ordinary users should carry.

5. gelephu

Canadian digital asset manager 3iQ will manage bitcoin reserves for Bhutan’s Gelephu Mindfulness City, the special administrative region the kingdom is funding with a pledge of up to 10,000 bitcoins, according to Mathew Di Salvo in Bitcoin Magazine. 3iQ, Canada’s biggest and oldest digital asset fund manager, will also invest in local talent and establish a long-term physical presence in Gelephu as the zone positions itself as Bhutan’s offshore digital financial hub. “From the very inception we were aligned with GMC’s vision to create a next-generation economic hub that attracts global talent,” said 3iQ chief executive Pascal St-Jean. Bhutan built its position quietly, mining with state hydropower before disclosing a standing reserve, and the GMC project is central to diversifying an economy that leans on hydropower and tourism. El Salvador’s Bitcoin City remains mostly a rendering. A sovereign putting mined coins under professional management to anchor a real economic zone is the quieter model that is actually shipping.

6. ngit

Soapbox has moved its Armada project off GitHub entirely and published a long field report on running a real repository over nostr, according to Derek Ross’s post on the Soapbox blog. The trigger was India’s Cyber Crime Coordination Centre giving GitHub three hours to disable the bitchat repositories, proof that a project is “one company, one jurisdiction and one takedown notice away from your project being a 404.” The replacement stack: ngit teaches plain git the nostr:// scheme, NIP-34 identifies a repository by its earliest unique commit rather than a URL anyone owns, and GRASP servers act as git host and relay at once — Armada announces three run by separate operators, with additional mirrors carrying it uninvited. Pull requests are branches pushed with a pr/ prefix, CI runs existing GitHub Actions files on self-hosted runners, and releases publish to Zapstore. Ross is candid about the sharpest edge: a maintainer’s signing key can rewind every host simultaneously. Censorship-resistant code hosting now exists in production, and it prices its guarantees in new operator responsibilities.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. namespace

The operator of mempool.space is filing a community priority application with ICANN for the .bitcoin top-level domain, according to wiz’s post on X. ICANN has opened its first new gTLD round since 2012, and without a successful community application the .bitcoin string would likely go to auction, where wiz warns it would be “sold to the highest bidder, potentially falling into the wrong hands, completely outside the reach of the community.” His proposed registration policy is strictly Bitcoin Only: applicants must verifiably demonstrate a qualifying function — running reachable nodes or DNS seeds, committing to consensus-compatible software, operating public infrastructure like explorers and wallets, publishing documentation, or convening meetups — while projects promoting altcoins are explicitly barred. A Registration Policy Committee drawn from those categories would enforce the rules, with wiz holding one ordinary seat, no veto and no registration priority. The application governs only the DNS root and takes no position on consensus rules. Whoever wins this round controls how the network’s name reads on the open internet for decades.

2. petition

The Human Rights Foundation, Freedom House and Hindus for Human Rights have filed a petition with the UN Working Group on Arbitrary Detention on behalf of Dr. Mahrang Baloch, according to HRF’s press release. The Baloch Yakjehti Committee founder is serving two life terms in Pakistan on terrorism charges brought under provisions that multiple UN Special Procedures have called vague and ill-defined. The filing details a trial the organizations describe as riddled with due process violations: arrest without a warrant at a peaceful sit-in, no access to a lawyer for a month, a year of solitary confinement, and closed-door hearings held inside the prison with Baloch appearing only by video link. HRF legal officers Hannah Van Dijcke and Kaitie Holland called the sentence “a clear effort to silence the dissent of the Baloch people by targeting one of their most effective and prominent leaders.” The petition asks the working group to declare the detention arbitrary and demand unconditional release, putting Pakistan’s use of anti-terror law before a body with a record of ruling against states.

3. handover

Demis Hassabis is stepping aside as chief executive of Google DeepMind, taking a chairman role and the title of chief scientist at Alphabet, according to Ina Fried and Madison Mills in Axios. Chief scientist Jeff Dean is leaving outright after 27 years to found Discovery Loop, an independent benefit corporation with Google as investor and cloud provider, joined by senior fellow Sanjay Ghemawat, DeepMind VP Oriol Vinyals and Google Brain co-founder Quoc Le. Koray Kavukcuoglu takes over operations as senior vice president reporting to Sundar Pichai, and Alphabet stock fell more than 4% on the news. “I’ve been working towards AGI my whole life and now, like many of you, I feel it is close at hand,” Hassabis wrote in his memo. The reshuffle lands amid reported morale problems and a Gemini release running months behind rivals. The most capable researchers in AI keep concluding that frontier science is easier to do outside a public company than inside one — even when the company funds the exit.

4. swarm

Calle has posted new throughput numbers from the Bitcoin Red Team, the volunteer effort running a large-scale security audit across the open-source bitcoin ecosystem, according to his post on X. The team has grown to 16 globally distributed people working around the clock, and the pace is remarkable: “27.5 hours in, we’ve filed 4,962 findings across 390 projects,” he wrote, counting 85 critical and 635 high severity issues among them — a rate of 2.31 critical-or-high findings per person per hour. The effort formed in direct response to the Coldcard entropy failure, which sat undetected in shipping firmware for five years, and it pairs AI models scanning hundreds of repositories with human reviewers who escalate and disclose what the machines surface. The numbers imply a decade of accumulated audit debt across bitcoin’s software stack being drawn down in days. The open question is absorption — hundreds of maintainers now face vulnerability reports arriving faster than volunteer projects have ever had to triage them.

5. mailbox

Second has shipped Bark 0.5.0, and its marquee feature closes one of the longest-standing gaps in Ark wallet design: restoring a wallet’s full off-chain balance from nothing but its mnemonic, according to the company’s post on X. Until now a Bark user who lost their device lost their VTXOs — the seed could recover on-chain funds, but off-chain state lived only in the local wallet database. The release notes describe the mechanism: each wallet posts the ids of VTXOs it creates or receives to a seed-derived recovery mailbox, then “re-derives that mailbox on first open to rebuild its spendable VTXO set from the seed alone — no local state required.” Recovery runs automatically on wallet open, the mailbox scan is bounded so an uncooperative server cannot stall it, and failures are reported for retry. The same release lets wallets claim Lightning receives for offline recipients without taking custody. With the Coldcard exploit pushing thousands of holders through emergency recoveries on far weaker guarantees, seed-only restoration is exactly the property self-custody tooling is now judged on.

6. hive

BTCPay Server project lead Pavlenex has launched BuzzDir, a directory of publicly shared communities running on Buzz, according to his post on X. Buzz is Block’s Apache 2.0-licensed workspace built on nostr, folding chat, code repositories and agent workflows into one self-hostable stack where every participant, human or AI, signs its actions with its own keypair. What the young ecosystem lacked was discovery. “Buzz is best experienced in multiplayer, but finding your hive can be a challenge,” Pavlenex wrote, and BuzzDir answers with a browsable index at buzzdir.xyz where anyone can list a community or find one to join. The directory is free and open-source software, was built entirely inside Buzz, and takes improvement proposals through Buzz itself — the tool is its own proof of concept. Decentralized protocols tend to ship identity and transport first and discovery last, which is why third-party aggregators became load-bearing infrastructure across nostr. A community index arriving this early suggests the ecosystem around Buzz is compounding on its own rather than waiting for Block to build every layer.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. redteam

Rob Hamilton has published a progress report on the Bitcoin Red Team, the volunteer effort scanning the ecosystem’s open-source code in the wake of the Coldcard exploit, according to his post on X. The numbers: roughly $20,000 spent across services, 150 repositories scanned, and more than a dozen coordinated disclosures, with funding secured and donations declined. Hamilton has built a first-pass agent harness that needs only an opencode zen API key, using Kimi K3 for the heavy lifting and GPT Sol, Fable, Opus and GLM5.2 for supporting documentation, and he is also running OpenAI’s more expensive Cyber Harness against load-bearing parts of the ecosystem, where it has already yielded results. “Our goal is to open source the harness so it can be pointed at internal repositories,” he writes, so hardening can go deeper than public code. The choke points are now human: request staging and report handoff. This is the counterweight to agentic attackers — the same models that broke the review asymmetry are being drafted to close it.

2. boltz

Boltz has suspended its swap service indefinitely, taking a core piece of non-custodial Lightning infrastructure offline, according to the company’s post on X. The team says the shutdown is not a reaction to a single incident but to a months-long rise in automated, AI-assisted probing that produced several contained exploits — and a drastic acceleration in recent days from what appear to be multiple resourceful groups. The asymmetry is the stated reason: “attackers now iterate faster than a team our size can find and patch,” and Boltz does not believe that reverses. The company stresses that no user funds were ever at risk, its API remains available for cooperative refunds, unilateral refunds work without its infrastructure at all, and as a bootstrapped firm the losses were its own. It calls the moment a paradigm shift for bitcoin services running on open-source stacks. The design held — non-custodial architecture meant users lost availability, not money — but availability is exactly what agentic attackers are now able to take.

3. alpamayo

Nvidia has launched Alpamayo 2 Super, a frontier open reasoning model for autonomous vehicles, released for commercial use under the OpenMDW-1.1 license, according to CEO Jensen Huang's post on LinkedIn. The design goal moves past perception — the model reasons through complex driving scenarios before it acts, and Huang positions it as a backbone for robotaxis, trucks, shuttles, delivery vans, tractors and the long tail of mobile robots, a market he sizes at billions of autonomous machines someday. The architecture pairs a large Cosmos-based reasoning model with compact distilled versions that run in-vehicle on DRIVE AGX Thor hardware, so frontier-scale reasoning happens in training while real-time inference stays at the edge. The licensing is the strategic tell, with Nvidia publishing the model "so teams can inspect it, fine-tune it and deploy it — open models advance safety and security." Huang calls robotics the next wave of AI, and open weights are becoming its trust layer: when software drives two tons of steel, inspectability stops being a philosophical preference and becomes a safety requirement.

4. disclosure

Bitcoin maintainers are drawing a line on how AI-discovered vulnerabilities should be reported, after a researcher posted claimed proof-of-concept exploits publicly rather than disclosing privately, according to Miles Suter’s post on X, amplified by Matt Corallo. Suter welcomed frontier models being pointed at open-source code — more eyes, better ecosystem — but was blunt about method: “this should be done over email, and not in public where unverified claims can lead to false narratives and unnecessary panic.” He acknowledged the researcher’s claim within thirty minutes and said the team is investigating, while noting that even cyber-focused models can produce slop. Security engineer rot13maxi compressed the norm into one line — tweets are not responsible disclosure. The context is a community on edge, with Coldcard sweeps ongoing and Boltz dark. The disclosure pipeline is becoming the scarce resource: AI has multiplied the rate of plausible findings, and the ecosystem’s safety now depends on routing them through verification rather than through engagement algorithms.

5. bitmex

The team behind BitMEX Research has published a farewell accounting as BitMEX prepares to wind down in September, closing the research desk after almost ten years, according to the Farside Insights post on X — the renamed BitMEX Research account. The retrospective is unusually candid about why the exchange faded: slow stablecoin adoption, regulatory friction, the March 2020 downtime, a management layer beneath the founders that lacked domain expertise, and clients lost to fraudulent platforms faking superior backends. It is equally clear about what BitMEX refused to compromise — a manual once-per-day three-of-four multisig wallet and real-time audits and reconciliations. The grant program donated over $2 million to open source developers, and “BitMEX was the first profitable operating company in the space to give no-string attached grants to Bitcoin developers,” a model now continued by Maelstrom, Arthur Hayes’ family office, while Localhost Research takes over bitnod.es and ForkMonitor sponsorship. The public goods outlive the exchange — grants, node monitoring and a research archive headed for a CC BY 4.0 release.

6. moratorium

Texas Governor Greg Abbott has directed the state’s Public Utility Commission and ERCOT to audit every data center seeking a grid connection, and Bernstein argues bitcoin miners come out ahead, according to Robert Lakin in Cointelegraph. Most Texas miners already hold approved capacity under contract, so the freeze on new connections falls on speculative entrants instead. “This audit throttles speculative data center pipeline and makes genuine sites with development history more valuable,” wrote the research team led by Gautam Chhugani, noting mining sites carry the longest gestation, self-funded infrastructure and local community management. Fully grid-approved operators like IREN and Riot Platforms benefit most, while Cipher, Core Scientific and CleanSpark face more exposure where pipeline assets still need ERCOT conversion. The directive lands amid rising public backlash to data center build-out across the state. This inversion is notable — after years as the grid’s scapegoat, miners’ approved megawatts just became scarcer assets precisely because the AI wave behind them is now the political problem.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. sweep

A fourth wave of sweeps against bitcoin held in Coldcard-generated addresses is underway, pushing estimated losses to roughly 1,816 BTC — near $114 million — across more than 5,200 addresses, according to Shaurya Malwa in CoinDesk. Alex Thorn, head of firmwide research at Galaxy Research, flagged the active wave and noted the attacker opted into replace-by-fee, meaning, as the piece puts it, “anyone who spots their address in the mempool has minutes to pay a higher fee and move funds first.” The pattern covered blocks 960,778 to 960,792, with 218 transactions hitting 462 victim addresses — about 14 sweeps per block against a 0.3 pre-incident baseline. Unlike earlier waves, destinations are fresh addresses with no prior history, one per victim, making clustering harder for forensics teams. Thorn published on pattern matching alone, choosing speed over confirmation to warn holders while transactions sat unconfirmed. For a bitcoin audience, the actionable detail is the escape hatch — until a sweep confirms, a victim can outbid it, so watching the mempool is now part of incident response.

2. fault

An independent review of Coldcard’s emergency firmware argues the entropy fix is correct but ships a failure mode of its own, according to a post on X from Arkfile summarizing a pull request by developer Silexperience. The patch resolves rng_get() to the board’s true hardware randomness accessor instead of MicroPython’s software fallback — the exact substitution at the heart of the original flaw. The trouble sits in rng_get_or_fault(), which has no recovery path for the STM32’s RNG error flags, so “a single seed error latches the peripheral into a state the code can never clear.” Every subsequent call then times out and raises OSError, and because rng_get() now sits on the keypad scan path, running from an interrupt callback before login, the exception is not survivable — the device effectively bricks itself. For a freedom-tech audience, this is what post-incident review should look like: the community is auditing the fix with an intensity the original code never received, and finding that failing closed still requires a way back open.

3. bait

A Coldcard owner has turned the tables on the sweeping attacker, reclaiming bait funds through a replace-by-fee counterattack, according to Will Owens in his post on X. Owens migrated his bitcoin off a compromised device shortly after disclosure but deliberately left roughly 0.0025 BTC behind as bait. The attacker eventually came for it and cheaped out on fees — “their transaction sat unconfirmed in the mempool long enough for me to broadcast an RBF replacement,” Owens wrote, routing the coins to a clean wallet instead and marveling that someone could compromise a hardware wallet and still fumble the bag. The stunt is live confirmation of the defense researchers had described only in theory: until a sweep confirms, the rightful owner can outbid it, and Galaxy Research flagged the same replace-by-fee opening across the fourth wave of sweeps. For a bitcoin audience, the lesson generalizes — fee selection is now operational security on both sides of a key compromise, and the mempool is the last venue where a victim can still win.

4. battery

Base Power has launched Base Core, a roughly 40 kWh home battery designed and built in Texas, alongside a $1 billion Series D that values the company at $13 billion, according to co-founder Zach Dell’s post on X. Core is about three times the size of most home batteries, backing up an average home for as long as 36 hours, and carries a generator port so owners can recharge it through multi-day outages. The company scaled from one install per day to one hundred in two years, and the round was co-led by Ribbit, Addition, Valor and JPMorgan, with a16z, Thrive, Lightspeed and CapitalG re-investing. “Electricity is the largest and most essential industry in the world, and it does not have a defining technology company,” Dell wrote. For a freedom-tech audience, distributed batteries are energy self-custody in miniature — households holding their own reserve rather than trusting the grid alone, the same flexibility bitcoin miners already sell back to strained networks, and a hedge that matters more as AI demand tightens supply.

5. workshop

OrangeSurf and collaborators are turning the Coldcard incident into hands-on education, adding an entropy session to a free builder event hosted by Antidote in Farringdon, London, according to his post on X. The update promises “a workshop to help you understand entropy, threat modeling your wallet setup and what to consider when migrating a wallet” — precisely the triage skills thousands of holders discovered they lacked when the sweeps began. The gathering brings bitcoin developers, builders and curious hackers together for a day of workshops and collaboration, registration is required but attendance is free, and OrangeSurf is offering direct help over DM for anyone whose situation cannot wait for the event. It extends his running public work on the incident, from analysis of whitehat sweep ethics to review of the replacement firmware. For a freedom-tech audience, this is the immune response working as intended — a vendor failure metabolized into open, peer-to-peer training on randomness, threat models and wallet migration rather than a lesson filtered through any official channel.

6. missed

Casa co-founder Jameson Lopp answered the question hanging over the Coldcard incident — how did external audits miss the deterministic RNG bug — with four points, according to his post on X. First, the defect was non-obvious and lived in the build system rather than the main application path. Second, he believes Ledger Donjon reviewed Coldcard multiple times over the years and still missed it. Third, most large language models miss the same class of bug when they do not pull full submodule context. Fourth, critical vulnerabilities have sat undetected for a decade-plus in extremely popular codebases including SSL, SSH, and Linux. The post was a direct reply to calle’s observation that the bug sits in arguably the most important line of firmware and that real external researchers had audited the product. For operators evaluating hardware wallets after this week, the durable lesson is not that audits are worthless; it is that an audit scoped to application code, or an AI review scoped to a partial checkout, can still green-light a broken random number generator if the failure lives one layer below the files under review.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

1. entropy

Frank Corva has published a full breakdown of the Coldcard firmware failure that exposed private keys across more than 4,500 bitcoin addresses and cost users roughly $89 million, according to his post on Substack. The root cause was a build configuration error rather than a broken algorithm: Coldcard’s board config set MICROPY_HW_ENABLE_RNG to zero, but the libngu library checked whether that macro was defined rather than whether it was nonzero, so seed generation fell through to a deterministic Yasmarang PRNG seeded from MCU UID, SysTick and RTC values. Corva calls it “one line of bad code” that survived five years without an audit catching it, and urges anyone holding a Mk3 — or any Coldcard that generated its own seed — to move funds immediately and never re-enter the compromised phrase on new hardware. For a freedom-tech audience, the distinction Corva draws is the one that matters: the bitcoin network held, a single vendor’s build toolchain did not, and self-custody is only ever as strong as the weakest link in a device’s supply of randomness.

2. forensics

Core Lightning developer ddustin has traced the Coldcard entropy failure to two commits with almost no explanation attached, according to his guest post in bitcoin++’s Insider Edition. One commit changed 1,534 lines of firmware under a five-character message reading only “runs,” a comment-to-code ratio he calls atrociously bad for the most security-critical part of a signing device. His reconstruction: the developer hit a duplicate symbol compiler error while trying to override MicroPython’s RNG functions, then silenced it by setting MICROPY_HW_ENABLE_RNG to zero, which removed the hardware RNG path entirely and left make_new_wallet calling random.bytes() straight into a software generator. “Do not ship code you do not understand,” he writes, extending the criticism to MicroPython for creating the illusion that embedded work requires no understanding of C. For a freedom-tech audience, this is the piece that converts a vendor incident into a reviewable engineering standard: commit hygiene, compiler warnings and review depth are security properties of a hardware wallet, not developer etiquette.

3. license

A thread circulating among hardware wallet developers argues that Coinkite’s licensing decisions helped create the conditions for the Coldcard entropy flaw, according to skot’s post on X. Coldcard was built partly on GPL code from Trezor. When Foundation Devices forked Coldcard to create Passport, Coinkite moved to a Commons Clause license, which meant the borrowed GPL code had to be stripped out and rewritten — and the RNG defect entered during that rewrite, then sat undetected for five years. Skot’s framing is about incentives rather than intent: “the best reviewers are people, companies and agents integrating into their own projects,” and a source-viewable license removes the economic reason for anyone to audit deeply. For a freedom-tech audience, the causal chain needs proper forensics before anyone calls it settled, but the underlying question is durable: in security hardware, permissive licensing may function less as generosity toward competitors and more as a subsidy for review labor no vendor can afford to buy.

4. quantum

IBM chief executive Arvind Krishna says quantum computing is close to becoming a commercial business rather than a research program, with a measurable contribution to revenue and profit expected by 2028 or 2029, according to Helene Braun in CoinDesk reporting his CNBC interview. “By the end of the 2030s, we are now pretty convinced this is a trillion dollars of value,” Krishna said. IBM has committed $1 billion to a standalone quantum chip foundry, matched by a further $1 billion from the Department of Commerce through the CHIPS incentive program. For a bitcoin audience, two things follow. Quantum machines require entirely different facilities and supply chains from AI data centers, which limits how far miners like MARA, Riot and CleanSpark can extend the diversification playbook into this workload. And while a machine capable of breaking wallet cryptography remains distant, commercialization timelines shorten the runway for migrating to quantum-resistant signatures, turning it from a theoretical debate into a scheduling problem for protocol developers.

5. sanctions

The U.S. Treasury has sanctioned two Iranian maritime firms running a bitcoin-settled insurance scheme for vessels transiting the Strait of Hormuz, according to Shaurya Malwa in CoinDesk. OFAC designated the Persian Gulf Marine Insurance Company and HormuzSafe Marine Services Authority, describing the arrangement as extortion rather than coverage because the policies insured against vessel seizures that “are overwhelmingly created by Iran itself.” Treasury said Hormuz Safe was developed by Iran’s Ministry of Economy and accepts bitcoin and other digital assets as part of the regime’s attempts to bypass Western sanctions, with proceeds flowing to the Islamic Revolutionary Guard Corps. Foreign firms paying in bitcoin carry the same secondary sanctions exposure as those paying through banks. For a freedom-tech audience, that equivalence is the point worth sitting with: censorship resistance at the protocol layer does not extend to the counterparty layer, and enforcement has adapted to target the entities on either end of a settlement rather than the rails between them.

6. blindspot

The Coldcard entropy flaw was surfaced by one AI model and missed by another, and the team behind the miss has explained why, according to their post on X. Kimi K3, an open-weight model, found the bug during firmware review. A team running Anthropic’s Opus did not: “we hadn’t cloned enough of Coldcard’s submodules. This bug lives between files, and some of those files weren’t on disk.” What the model could see told a self-consistent story, complete with docstrings at the boundary promising “best-quality high entropy TRNG bytes.” The failure was in repository setup, not reasoning. For a freedom-tech audience, this is the most actionable detail of the week for anyone pointing models at security-critical code: completeness of context determines whether an audit means anything, a partial checkout yields confident output about code that does not exist as assembled, and the weakest link in automated auditing right now is the harness rather than the model.

Thanks for reading Tangents Daily, the front row for frontier tech. Please share & subscribe:

Subscribe now

Starting with tomorrow's issue, OP_DAILY becomes Tangents Daily. Same daily email, same discipline, wider aperture: the frontier where AI, energy, and Bitcoin touch, and what changes next.

What changes for you: the sender name will say Tangents Daily, and our web home is now tangentsdaily.substack.com. That's it. You don't need to do anything.

Why the new name: the daily outgrew its original lane. The best stories were never inside one lane anyway. They start at the exact point where one system grazes another. AI models colliding with power grids. Miners becoming grid assets. Agents learning to move money. That contact point is what we hunt for, every day.

The daily email tracks the signals. Tangents, the weekly show we are building, connects them. Daily signals. Weekly synthesis.

Nothing great happens in a straight line. See you tomorrow morning.

1. bitkey

Block’s Clay Garrett shared initial findings on a reported Bitkey vulnerability and recommended that users continue using Bitkey normally, according to his post on X. The vulnerability would require exceptional circumstances to exploit and can only occur at a specific narrow time during inheritance setup; even if an attacker exploited it — including exploiting TLS internet security — they would not have enough cryptographic material to access funds. Block’s assessment is no risk of remote drains or immediate funds loss. A patch has been submitted to both app stores and a full technical report is forthcoming. The team credited @1440000bytes for responsible disclosure. For a self-custody audience, the Bitkey disclosure is a useful contrast to the Coldcard incident unfolding in parallel: a vulnerability found through responsible disclosure, assessed publicly as presenting no remote drain risk, with defense-in-depth cited as the reason an attacker reaching the vulnerable window still could not access funds. Not every hardware wallet disclosure this weekend is a funds emergency — the contrast in risk profile matters.

2. scan

Rob Hamilton, contributor to the Bitcoin ecosystem, is urging engineers who work on bitcoin-related software to use OpenRouter or opencode to run Kimi K3 — an open-weight model released Monday — against any bitcoin-related internal codebases and public repositories for vulnerability scanning, according to his post on X. He has been scanning open-source repos himself and finding issues he is passing along to maintainers, noting that K3 one-shots full vulnerability reports, and that the timing of Kimi K3’s open-weight release against the Coldcard issues unfolding is not a coincidence. For a freedom-tech audience, the call is a direct application of the week’s open-weights thesis to a live security emergency: the same argument that open models make better defenders — demonstrated by Hugging Face using GLM 5.2 to contain the OpenAI incident — now has engineers scanning bitcoin infrastructure with open-weight AI in the immediate aftermath of the largest hardware-wallet compromise in the ecosystem’s history.

3. jade

Blockstream Jade issued a scam warning to the bitcoin self-custody community as emotions run high following the Coldcard incident, according to the official Blockstream Jade post on X. The rules listed: never type your recovery phrase into any website, form, checker, or tool; no one legitimate will DM you first asking for seeds or offering to help you migrate; only use official communication channels and software you already trust. Slow down, verify every step, and a few extra minutes of caution is always worth it. For a freedom-tech audience, Blockstream Jade’s warning is the operational complement to Saifedean’s migration checklist and O’Beirne’s dice verification: the technical work of a proper migration matters less if a social engineer intercepts the process and collects the seed phrase directly. Hardware-wallet incidents reliably produce a second wave of theft through phishing and impersonation, and the community is in that window right now. Any unsolicited contact about Coldcard recovery — by DM, email, or any channel — should be treated as an attack.

4. losses

Galaxy Research mapped the flow of funds for the Coldcard vulnerability, finding that 1,196 addresses were drained for 1,082.65 bitcoin worth approximately $70.2 million in a 41-minute window on July 30 — roughly 30 hours before Coinkite’s public advisory, according to the Galaxy Research post on X. Every sweep paid an identical hardcoded 30.0 sat/vB fee, a 30 to 75 times overpay versus the market median that week, with no change output — consistent with an automated tool spending keys it already held. Victims were 1,183 native segwit BIP-84 addresses, 7 BIP-49, and 6 BIP-44, consistent with multi-path key scanning. Proceeds consolidated into four addresses and have not moved since. For a self-custody audience, the forensics confirm the attack was pre-planned and automated, and the stolen funds are fully traceable — sitting unmoved in four known addresses — creating an unusual situation where the full scope of the theft is publicly visible but recovery is structurally impossible without the attacker’s cooperation.

Consider subscribing and sharing OP_Daily with your community.

Subscribe now

1. coldcard

Block’s Bitcoin engineering and security teams published a coordinated root-cause analysis of active Coldcard thefts after users reported non-Bitkey wallets being remotely drained, according to Max Guise’s thread on X and the Block Engineering write-up. A macro defined as zero instead of enabled caused wallet seed generation on affected firmware to use MicroPython’s Yasmarang software PRNG instead of the STM32 hardware RNG; Mk2 and Mk3 devices on 4.x firmware are the most exposed, while Mk4 and Mk5 devices reseeded from secure elements but retained only 32 bits of that material. Exporting a weak seed to another wallet does not fix it. For a self-custody audience, this is the week’s defining incident: open firmware, AI-assisted reverse engineering, and remote drains of life-savings hardware wallets. The operational instruction is unambiguous: move funds only to a new seed generated on fixed firmware or an unaffected device, and do not share seeds with anyone offering recovery help, as social-engineering attempts targeting affected users are already underway.

2. hotfix

Coinkite shipped emergency firmware after the entropy failure became public: Mk3 version 4.2.0, Mk4 and Mk5 version 5.6.0, and Q version 1.5.0Q, with a full technical backgrounder on the 2021 libNgU migration that routed seed generation through MicroPython’s software PRNG instead of the hardware TRNG, according to the official Coldcard wallet post on X. Coinkite estimates roughly 40 bits of effective search space on affected Mk3 seeds without dice, and about 72 bits on later models where SE1 and SE2 entropy was mixed in but still fell short of a 128-bit target. Seeds created with 50 or more independent private dice rolls are treated as outside this RNG failure alone; updating firmware does not repair an already-generated weak seed. For operators and family offices, the sequence is fixed: upgrade firmware first, generate a completely new seed on the fixed device, verify the fingerprint and a receive address, test with a small send, then migrate the rest — and ignore unsolicited recovery messages from anyone claiming to help.

3. migrate

Saifedean Ammous posted a calm, step-by-step migration path for Coldcard users who relied on device-generated randomness alone, according to his post on X. His checklist: generate a completely new seed on an unaffected device or airgapped computer; record and verify the backup; verify wallet fingerprint and a receive address on the hardware; send a small test transaction; only then move remaining funds. He stresses that the bug is in Coldcard firmware entropy contribution, not in Bitcoin consensus, and that 50 to 100 fair private dice rolls at original seed creation are considered protective for this specific failure. A strong BIP-39 passphrase is a separate barrier that still depends on passphrase strength. Anyone unsure about firmware version or dice history should assume risk and migrate. For Bitcoin Park readers, this is the practical companion to the technical disclosures: deliberate action beats panic, and the social-engineering wave that always follows a hardware-wallet incident is already underway — do not share seeds or recovery phrases with anyone.

4. dice

Bitcoin developer James O’Beirne cut through conflicting advice with a verification claim that matters for anyone on the fence: he checked code paths across firmware versions and confirmed that dice rolls are mixed into the seed via hash, and that 99 or more rolls are good, according to his post on X. Separately he told device-generated users to move funds expeditiously today if possible while investigations into current firmware state continue. For a self-custody audience, the durable lesson is that entropy you can see and control is not cargo-cult security theater: when a device’s own RNG path fails, external dice or equivalent physical entropy are what separate a recoverable situation from a total loss. If you never rolled dice, treat the seed as compromised and migrate; if you did, verify against Coinkite’s 50-to-100-roll guidance before deciding whether you still need to rotate. The clearest single answer to the question most affected users are actually asking: dice users who rolled 99 or more are good, device-only users should move funds now.

Consider subscribing and sharing OP_Daily with your community.

Subscribe now