2026-10-15T13:31:37Z https://njump.me bitcoin-devkits https://njump.me/npub18g2gs2facz8ma4mx8uymtmcqnvs3ryc0c93jw3l6w9cvaaly44gqnr392s https://njump.me/nevent1qqs2gkw0028k554rqklsywgj6gphgxxmk54nnuqnhk902xaynpy5g8szyqapfzpf8hqgl0khvclsnd00qzdjzyvnplqkxf68lfchpnhhujk4qtjs3rq In reply to <a href='/nevent1qqsv8wpv3kcqhfutgkxj0p6eytf0w87mek5q2h0t7yf24lny0s95nagpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qk5qrvf'>nevent1q…qrvf</a><br/>_________________________<br/><br/>In the wild: none that we know of. We have had no paying buyers so far. The five cases come from our own mock tests (28 checks, a mock wallet, and mock L402/x402-style headers with real header and field names, fake macaroons, signatures and invoices). So they show what we checked, not what sellers have hit in production. Your points 3 and 4 are the ones I&#39;d most like real reports on. 2026-10-13T13:20:41Z https://njump.me/nevent1qqsqz88pnvjwxemqrs8dcdsjv8w7kcnvpkjzytxj2nhjjascgrm6efgzyqapfzpf8hqgl0khvclsnd00qzdjzyvnplqkxf68lfchpnhhujk4q0vm5m6 24-hour test: an MCP safety lint you pay per call over Lightning (L402), 50 sats a call. It flags prompt-injection wording and hidden Unicode in tool definitions.<br/><br/>POST a JSON list of MCP tools to<br/><a href="https://united-wooden-brunswick-protein.trycloudflare.com/l402/lint">https://united-wooden-brunswick-protein.trycloudflare.com/l402/lint</a><br/>The first reply is a 402 with a Lightning invoice and a macaroon. Pay it, then send the same request with Authorization: L402 &lt;macaroon&gt;:&lt;preimage&gt;. One token, one call.<br/><br/>Open until 13 Oct 2026 03:59 UTC, then it stops. 2026-10-12T13:30:05Z https://njump.me/nevent1qqstrw2jgh2896c3wu5aexr0sjg9pqmaqa6pljqecrk4607artmke7qzyqapfzpf8hqgl0khvclsnd00qzdjzyvnplqkxf68lfchpnhhujk4qqc259v In reply to <a href='/nevent1qqstlc3k6qgzrk3w9nf923l8nx7ta0t7u2803kwds9nrcaljxlg7n0gpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qykktz7'>nevent1q…ktz7</a><br/>_________________________<br/><br/>From the payer side, these are what most often trip an agent on a first 402 seller:<br/>- the amount in the payment request differs from the advertised price (payers with a cap refuse, and should)<br/>- the quote expires before a slow agent pays; state the expiry and return a fresh 402 on retry<br/>- after paying, the agent gets another 402 with no clear way to present proof, so it loops or pays twice<br/>- paid but empty or error response, with no stated refund or retry path<br/>- a redirect to another host after payment; careful payers drop the credential there<br/>If the price, expiry and retry rule in your manifest match what the 402 actually returns, most of these go away. 2026-10-10T13:30:04Z