Your comments section is drowning in AI-written garbage, and the CAPTCHAs you keep bolting on are starting to block real people too. Proof-of-work gates work great on paper. Then a proxyware SDK running on somebody's hijacked TV stick pays near-zero for CPU cycles, and the whole cost asymmetry flips the wrong way. You paid for the engineering, the attacker paid the power bill of a grandma in Ohio, and your comments section is still full of bots.

Here's the thing I did not expect to type this week. On April 21st, the commander of U.S. Indo-Pacific Command sat down in front of the Senate Armed Services Committee and told them flat out that the military runs a node on the Bitcoin network to study proof-of-work economics. His words, not mine: "Bitcoin shows incredible potential as a computer science tool that, through the proof-of-work protocols, actually imposes more costs than just the algorithmic securing of networks." Then he called it "a valuable computer science tool as a power projection." The https://www.btcpolicy.org/articles/press-release-indo-pacific-commander-calls-bitcoin-a-tool-for-us-power-projection-in-senate-testimony has the transcript.

Read that first quote again. "Imposes more costs than just the algorithmic securing." That is the whole argument for pricing web interaction, said by a four-star from a witness chair. Blocking bots loses. Somebody always writes a better bot, or buys cheaper compute, or leases a proxyware pool. Pricing the request wins, because price travels with the request no matter who is holding the keyboard. Good agents pay a couple sats and get through. Scrapers pay at volume and eat the cost asymmetry. Grandma's TV stick is not going to open a Lightning channel to hammer your site, so the hijacked-device attack stops being free. Lightning is the payment rail for the ones who have sats. PoW is the fallback for the ones who do not, or who are not set up for it yet. You get both tiers without caring which kind of caller showed up.

I have been shipping the boring version of this argument at the HTTP layer for a few months now. @powforge/captcha is live on npm, MIT licensed, three lines of Express middleware, and the fallback works without a Lightning node so you can drop it on a brand new project and let the PoW tier carry traffic while you sort out your Lightning setup. The invoice tier kicks in when the caller has sats, and the prices are set by the site, not by me. The next piece going out is a chaintip-freshness cert so a caller can prove their proof-of-work was computed against a recent block, not replayed from last Tuesday afternoon. Same primitive, different shape. Real receipts, no thesis-lecture required.

So here is the honest question. Which is the worse bet right now, turning away a paying agent because your stack was built to block bots, or letting your content train somebody else's model for free while you argue about CAPTCHA UX?

Refs:

• Senate hearing page: https://www.armed-services.senate.gov/hearings/to-receive-testimony-on-the-posture-of-united-states-indo-pacific-command-and-united-states-forces-korea-in-review-of-the-defense-authorization-request-for-fiscal-year-2027-and-the-future-years-defense-program
• Bitcoin.com News coverage: https://news.bitcoin.com/us-military-runs-bitcoin-node-conducts-operational-tests-indo-pacific-commander-tells-senate/
• Decrypt civilian framing: https://decrypt.co/365221/us-government-runs-bitcoin-node-not-mining-btc
• @powforge/captcha on npm: https://www.npmjs.com/package/@powforge/captcha