Good Morning Bitcoin, 10 August

Today's Snapshot

  • BSV developer submits an x402 integration for agent payments
  • the pull request is open and awaiting maintainer review
  • settlement on BSV is proposed not adopted

Machine-to-machine payments are quietly becoming infrastructure, with AI agents and software services needing to settle with each other over standard web protocols at scale. A BSV developer has shown up to that conversation with working code.

Top Stories

BSV pull request targets x402, the open protocol for agent payments

The news Darren Kellenschwiler, a developer at the BSV Association who goes by the handle sirdeggen, has opened pull request 2890 on the x402 GitHub repository, titled "feat(bsv): add exact scheme support for BSV." x402 is an open protocol, originally from Coinbase and now stewarded by the x402 Foundation, that lets machines and software agents pay each other over standard HTTP, settling primarily in USDC on the Base network. The PR is open and unmerged, awaiting review and formal authorization from the x402 maintainers, with no official approvals yet.

More on this The PR introduces a new package called @x402/bsv, shipping client, server and facilitator code that maps BSV's BRC-121 Simple 402 Payments flow onto x402's exact payment scheme. It uses BRC-29 remittances over BRC-42 key derivation for privacy, and has the recipient's own BRC-100 wallet act as the facilitator - meaning no third-party custody of funds. The package registers BSV mainnet, testnet and two Teranode test networks and ships with more than 103 unit tests plus live integration testing. Community response has been notable, with more than 34 positive reactions and more than 40 comment threads including technical feedback from other implementers.

What's next? The central questions are whether the x402 maintainers merge the PR, whether they formally recognize BSV as a supported chain and how much weight they give to a community submission. Even if it merges, x402 is deliberately chain-agnostic and today runs mostly on USDC over Base, so presence in the codebase is a different thing from agent payment traffic actually settling on BSV.

The Takeaway

If BSV becomes a recognized settlement option on the x402 rail, its sub-cent fees and the high-throughput ambitions of Teranode - targeting over one million transactions per second - position it sensibly for large volumes of small agent payments. That is a genuine fit worth noting. But submitting a pull request is the first step, not the finish line and the outcome rests with maintainers and, ultimately, with whether developers building agent systems choose to route traffic there.

What Else We're Watching

What to Watch

  • Whether PR 2890 is reviewed, requested for changes or merged by the x402 maintainers, and what direction or conditions they attach to it
  • Teranode's progress from test networks toward production readiness, which is the underlying technical promise that makes BSV's case for agent-scale payment volume credible in the first place

The Block Drop goes out each morning - forward it to anyone building on the original protocol.