agentpaywire commited on
Commit
f6c57c3
·
verified ·
1 Parent(s): 2901759

Sync library snapshot 2026-11-07 (178 entries; Optech #430, Breez SDK Spark 0.28, BTCPay 2.4.7, Circle x402 Discovery)

Browse files
Files changed (5) hide show
  1. README.md +10 -10
  2. data/library.json +104 -4
  3. data/sources.csv +4 -0
  4. data/sources.jsonl +4 -0
  5. data/tags.json +54 -14
README.md CHANGED
@@ -26,7 +26,7 @@ configs:
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
- A curated library of **174 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
30
 
31
  This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
32
 
@@ -36,15 +36,15 @@ Linked pages, papers, repositories and specifications are **not** included and b
36
 
37
  - Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
38
  - `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
39
- - Snapshot taken 2026-11-06 (last updated 2026-11-06). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (9 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows), 2026-11-06 (2 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-06T00:00:00Z.
40
  - The site is rebuilt when entries are published (on publish). This Hugging Face copy is a snapshot; the live site is authoritative and may be newer. For incremental sync use https://agentpaywire.com/changelog.json (filter by `verified_at`).
41
 
42
  ### Categories (snapshot)
43
 
44
  | category | entries |
45
  | --- | --- |
46
- | bitcoin-lightning (featured) | 40 |
47
- | payments | 71 |
48
  | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
@@ -54,7 +54,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
- One JSON object per line, 174 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
58
 
59
  | field | type | description |
60
  | --- | --- | --- |
@@ -62,7 +62,7 @@ One JSON object per line, 174 rows, single `train` split. Dates are `YYYY-MM-DD`
62
  | `title` | string | Source title, copied from the page. |
63
  | `publisher` | string | Publisher name. |
64
  | `authors` | list of strings | People named on the source; empty list when none are named. |
65
- | `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (78 of 174 rows). |
66
  | `url` | string | Canonical URL of the source. |
67
  | `type` | string | One of `announcement`, `directory`, `docs`, `regulatory`, `repo`, `report`, `research-paper`, `spec`. |
68
  | `category` | string | One of the categories above. |
@@ -70,7 +70,7 @@ One JSON object per line, 174 rows, single `train` split. Dates are `YYYY-MM-DD`
70
  | `summary` | string | Short summary written for this library. |
71
  | `tags` | list of strings | Topic slugs (e.g. `l402`, `x402`, `lightning`, `mcp`, `stablecoins`). |
72
  | `verified_at` | string | Date the URL, title and publication date were checked. |
73
- | `featured` | bool | `true` for featured Bitcoin and Lightning sources (38 rows); `false` or key absent (null when loaded) otherwise. |
74
  | `last_checked` | string | Date the link check last ran. |
75
  | `http_status` | int or null | HTTP status from that check; null when the request failed. |
76
  | `archive_url` | string or null | Wayback Machine snapshot URL; null when none was available. |
@@ -79,9 +79,9 @@ One JSON object per line, 174 rows, single `train` split. Dates are `YYYY-MM-DD`
79
 
80
  | file | contents |
81
  | --- | --- |
82
- | `data/sources.jsonl` | Main table (default config). 174 rows. |
83
- | `data/sources.csv` | Same 174 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
84
- | `data/library.json` | Full library document with category list (8 categories) and 174 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
 
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
+ A curated library of **178 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
30
 
31
  This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
32
 
 
36
 
37
  - Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
38
  - `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
39
+ - Snapshot taken 2026-11-07 (last updated 2026-11-07). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (9 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows), 2026-11-06 (2 rows), 2026-11-07 (4 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-07T00:00:00Z.
40
  - The site is rebuilt when entries are published (on publish). This Hugging Face copy is a snapshot; the live site is authoritative and may be newer. For incremental sync use https://agentpaywire.com/changelog.json (filter by `verified_at`).
41
 
42
  ### Categories (snapshot)
43
 
44
  | category | entries |
45
  | --- | --- |
46
+ | bitcoin-lightning (featured) | 43 |
47
+ | payments | 72 |
48
  | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
 
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
+ One JSON object per line, 178 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
58
 
59
  | field | type | description |
60
  | --- | --- | --- |
 
62
  | `title` | string | Source title, copied from the page. |
63
  | `publisher` | string | Publisher name. |
64
  | `authors` | list of strings | People named on the source; empty list when none are named. |
65
+ | `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (79 of 178 rows). |
66
  | `url` | string | Canonical URL of the source. |
67
  | `type` | string | One of `announcement`, `directory`, `docs`, `regulatory`, `repo`, `report`, `research-paper`, `spec`. |
68
  | `category` | string | One of the categories above. |
 
70
  | `summary` | string | Short summary written for this library. |
71
  | `tags` | list of strings | Topic slugs (e.g. `l402`, `x402`, `lightning`, `mcp`, `stablecoins`). |
72
  | `verified_at` | string | Date the URL, title and publication date were checked. |
73
+ | `featured` | bool | `true` for featured Bitcoin and Lightning sources (41 rows); `false` or key absent (null when loaded) otherwise. |
74
  | `last_checked` | string | Date the link check last ran. |
75
  | `http_status` | int or null | HTTP status from that check; null when the request failed. |
76
  | `archive_url` | string or null | Wayback Machine snapshot URL; null when none was available. |
 
79
 
80
  | file | contents |
81
  | --- | --- |
82
+ | `data/sources.jsonl` | Main table (default config). 178 rows. |
83
+ | `data/sources.csv` | Same 178 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
84
+ | `data/library.json` | Full library document with category list (8 categories) and 178 entries. From https://agentpaywire.com/api/library.json. |
85
  | `data/library.schema.json` | JSON Schema for the library documents. |
86
  | `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
87
  | `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
data/library.json CHANGED
@@ -1,19 +1,19 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-06T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
7
  },
8
  "$schema": "https://agentpaywire.com/schemas/library.schema.json",
9
  "license": "links + original short summaries; content belongs to publishers",
10
- "count": 174,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
14
  "label": "Bitcoin and Lightning",
15
  "featured": true,
16
- "count": 40,
17
  "json_url": "https://agentpaywire.com/api/library/bitcoin-lightning.json",
18
  "markdown_url": "https://agentpaywire.com/library/bitcoin-lightning.md",
19
  "html_url": "https://agentpaywire.com/library/bitcoin-lightning/"
@@ -22,7 +22,7 @@
22
  "id": "payments",
23
  "label": "Payments",
24
  "featured": false,
25
- "count": 71,
26
  "json_url": "https://agentpaywire.com/api/library/payments.json",
27
  "markdown_url": "https://agentpaywire.com/library/payments.md",
28
  "html_url": "https://agentpaywire.com/library/payments/"
@@ -83,6 +83,58 @@
83
  }
84
  ],
85
  "entries": [
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
86
  {
87
  "id": "getalby-hub-v1-24-6-release",
88
  "title": "Release v1.24.6 Julian Assange · getAlby/hub",
@@ -221,6 +273,30 @@
221
  "http_status": 200,
222
  "archive_url": null
223
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
224
  {
225
  "id": "l402sdk-v0-2-0-release",
226
  "title": "L402sdk 0.2.0",
@@ -1925,6 +2001,30 @@
1925
  "http_status": 200,
1926
  "archive_url": "http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"
1927
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1928
  {
1929
  "id": "link-balance-agent-wallet-purchases",
1930
  "title": "Set up a balance for agent wallet purchases",
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-07T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
7
  },
8
  "$schema": "https://agentpaywire.com/schemas/library.schema.json",
9
  "license": "links + original short summaries; content belongs to publishers",
10
+ "count": 178,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
14
  "label": "Bitcoin and Lightning",
15
  "featured": true,
16
+ "count": 43,
17
  "json_url": "https://agentpaywire.com/api/library/bitcoin-lightning.json",
18
  "markdown_url": "https://agentpaywire.com/library/bitcoin-lightning.md",
19
  "html_url": "https://agentpaywire.com/library/bitcoin-lightning/"
 
22
  "id": "payments",
23
  "label": "Payments",
24
  "featured": false,
25
+ "count": 72,
26
  "json_url": "https://agentpaywire.com/api/library/payments.json",
27
  "markdown_url": "https://agentpaywire.com/library/payments.md",
28
  "html_url": "https://agentpaywire.com/library/payments/"
 
83
  }
84
  ],
85
  "entries": [
86
+ {
87
+ "id": "bitcoin-optech-newsletter-430",
88
+ "title": "Bitcoin Optech Newsletter #430",
89
+ "publisher": "Bitcoin Optech",
90
+ "authors": [],
91
+ "date_published": "2026-11-06",
92
+ "url": "https://bitcoinops.org/en/newsletters/2026/11/06/",
93
+ "type": "report",
94
+ "category": "bitcoin-lightning",
95
+ "status": "news",
96
+ "summary": "Newsletter dated 2026-11-06. The releases section calls LND v0.21.6-beta and v0.20.7-beta security releases that include the Linux CVE-2026-98432 mitigation described under LND #11456, and says that mitigation does not fix the kernel. It calls Core Lightning 26.06.10 a security release for dual funding, splicing, onchain HTLC resolution, access controls, and other components, with tests temporarily withheld. It calls BTCPay Server 2.4.7 a security release for 85 findings from Anthropic's OSS Scanner, including payout limits, other stores' data, authentication, and resource exhaustion. Separate from those release announcements, the notable-changes section describes LND #11357 as rejecting duplicate BOLT11 payment secrets and incorrect lengths for the payment hash, description hash, payment secret, and receiver public key, instead of ignoring extras or treating a bad length as absent. It describes Core Lightning #9419 as adding an optional failure_reason on listforwards and forward_event for local forwarding failures, and #9592 as making xpay exclude a forwarding node for the rest of a payment after unknown_next_peer twice. The newsletter also covers an ongoing TCP hole-punching discussion and a draft co-signer spending policy that is not assigned a BIP number.",
97
+ "tags": [
98
+ "bitcoin",
99
+ "lightning",
100
+ "bolt11",
101
+ "lnd",
102
+ "core-lightning",
103
+ "ldk",
104
+ "btcpay",
105
+ "optech"
106
+ ],
107
+ "verified_at": "2026-11-07",
108
+ "featured": true,
109
+ "last_checked": "2026-11-07",
110
+ "http_status": 200,
111
+ "archive_url": null
112
+ },
113
+ {
114
+ "id": "breez-sdk-spark-0-28-0",
115
+ "title": "Breez SDK 0.28 (Spark)",
116
+ "publisher": "Breez (GitHub)",
117
+ "authors": [],
118
+ "date_published": "2026-11-05",
119
+ "url": "https://github.com/breez/spark-sdk/releases/tag/0.28.0",
120
+ "type": "repo",
121
+ "category": "bitcoin-lightning",
122
+ "status": "spec_released",
123
+ "summary": "Release 0.28.0 published 2026-11-05, not a prerelease. The notes add a bridging client to pay a Spark, Lightning, or USDC/USDT address from another chain or over Lightning. USDC and USDT in that sentence are addresses on another chain, not a claim that the SDK treats them as native Lightning assets. The notes add sending to BIP-352 silent payment addresses and a change that rejects expired Lightning invoices. They also say the parser follows BIP-321 and restricts BIP-353 lookups. Compare: https://github.com/breez/spark-sdk/compare/0.27.0...0.28.0.",
124
+ "tags": [
125
+ "lightning",
126
+ "spark",
127
+ "breez",
128
+ "sdk",
129
+ "bip352",
130
+ "release"
131
+ ],
132
+ "verified_at": "2026-11-07",
133
+ "featured": true,
134
+ "last_checked": "2026-11-07",
135
+ "http_status": 200,
136
+ "archive_url": null
137
+ },
138
  {
139
  "id": "getalby-hub-v1-24-6-release",
140
  "title": "Release v1.24.6 Julian Assange · getAlby/hub",
 
273
  "http_status": 200,
274
  "archive_url": null
275
  },
276
+ {
277
+ "id": "btcpay-server-v2-4-7",
278
+ "title": "BTCPay Server v2.4.7",
279
+ "publisher": "BTCPay Server (GitHub)",
280
+ "authors": [],
281
+ "date_published": "2026-10-29",
282
+ "url": "https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.7",
283
+ "type": "repo",
284
+ "category": "bitcoin-lightning",
285
+ "status": "spec_released",
286
+ "summary": "Release v2.4.7 published 2026-10-29, not a prerelease. The notes call it a bug-fix release for security, reliability, and payment accounting, and recommend updating, especially for servers shared by multiple merchants. The release says it fixes 85 security findings from Anthropic's OSS Scanner, using that report's severity ratings: 1 critical, 13 high, 52 medium, and 19 low. Those figures are the release's own table, not a CVE list. Named fixes include payout state changes that bypassed pull-payment limits, checkout forms restricted to the owning store, and BitPay API changes that apply the store's confirmation and expiry limits to anonymously created invoices and limit posData to 64 KiB before parsing. The release does not say every vulnerability in BTCPay is fixed.",
287
+ "tags": [
288
+ "bitcoin",
289
+ "lightning",
290
+ "btcpay",
291
+ "merchant",
292
+ "security"
293
+ ],
294
+ "verified_at": "2026-11-07",
295
+ "featured": true,
296
+ "last_checked": "2026-11-07",
297
+ "http_status": 200,
298
+ "archive_url": null
299
+ },
300
  {
301
  "id": "l402sdk-v0-2-0-release",
302
  "title": "L402sdk 0.2.0",
 
2001
  "http_status": 200,
2002
  "archive_url": "http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"
2003
  },
2004
+ {
2005
+ "id": "circle-agent-marketplace-discovery-api",
2006
+ "title": "Discover x402 services",
2007
+ "publisher": "Circle",
2008
+ "authors": [],
2009
+ "date_published": null,
2010
+ "url": "https://developers.circle.com/agent-stack/agent-marketplace/discovery-api",
2011
+ "type": "docs",
2012
+ "category": "payments",
2013
+ "status": "product_docs",
2014
+ "summary": "Circle's discovery page, checked 2026-11-07, says one public endpoint lists x402 services that accept USDC, with no API key and no account. The documented request is GET https://api.circle.com/v2/x402/discovery/resources. A read of that URL with limit=1 on the same day returned HTTP 200 and JSON with x402Version 2, items[].accepts[] carrying scheme, network, asset, amount, and payTo, metadata.input and metadata.output, and pagination.limit, offset, and total. The page documents filters for category, network, maxUsdPrice, supportsVanillax402, supportsCircleGateway, and siwx, and a type of http or mcp. It says limit defaults to 50 and the maximum is 200. The page links https://agents.circle.com/.well-known/openapi.json, which returned HTTP 200 the same day. This is Circle's catalog. It is not an Agent Paywire listing, and this card does not record a catalog total because that number changes.",
2015
+ "tags": [
2016
+ "x402",
2017
+ "directory",
2018
+ "discovery",
2019
+ "openapi",
2020
+ "usdc"
2021
+ ],
2022
+ "verified_at": "2026-11-07",
2023
+ "featured": false,
2024
+ "last_checked": "2026-11-07",
2025
+ "http_status": 200,
2026
+ "archive_url": null
2027
+ },
2028
  {
2029
  "id": "link-balance-agent-wallet-purchases",
2030
  "title": "Set up a balance for agent wallet purchases",
data/sources.csv CHANGED
@@ -1,10 +1,13 @@
1
  id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
 
 
2
  getalby-hub-v1-24-6-release,Release v1.24.6 Julian Assange · getAlby/hub,GitHub (Alby),,2026-11-05,https://github.com/getAlby/hub/releases/tag/v1.24.6,repo,bitcoin-lightning,product_docs,"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.",lightning; nwc; agent-wallets; security; tools,2026-11-06,true,2026-11-06,200,
3
  aperture-v0-6-0-release,Aperture v0.6.0,Lightning Labs,,2026-11-05,https://github.com/lightninglabs/aperture/releases/tag/v0.6.0,repo,bitcoin-lightning,product_docs,"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",l402; lightning; m2m-payments; release,2026-11-05,true,2026-11-05,200,
4
  core-lightning-v26-06-10,Core Lightning v26.06.10,Elements Project,,2026-11-04,https://github.com/ElementsProject/lightning/releases/tag/v26.06.10,repo,bitcoin-lightning,product_docs,"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",lightning; release; security,2026-11-05,true,2026-11-05,200,
5
  wavelength-v0-2-1-release,Wavelength v0.2.1,Lightning Labs (GitHub),,2026-10-31,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1,repo,bitcoin-lightning,spec_released,"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.",lightning; ark; wallet; release,2026-11-03,true,2026-11-03,200,
6
  lnd-v0-21-6-beta,lnd v0.21.6-beta and v0.20.7-beta,Lightning Labs (GitHub),,2026-10-30,https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta,repo,bitcoin-lightning,product_docs,"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.",lnd; lightning; release; security,2026-11-03,true,2026-11-03,200,
7
  bitcoin-optech-newsletter-429,Bitcoin Optech Newsletter #429,Bitcoin Optech,,2026-10-30,https://bitcoinops.org/en/newsletters/2026/10/30/,report,bitcoin-lightning,news,"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.",bitcoin; lightning; security; optech,2026-10-31,true,2026-10-31,200,
 
8
  l402sdk-v0-2-0-release,L402sdk 0.2.0,Lightning Labs,,2026-10-29,https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md,repo,bitcoin-lightning,product_docs,L402sdk 0.2.0 is dated 2026-10-29 in CHANGELOG.md. Budgets include routing fees and concurrent payment reservations. Automatic payments require a backend that enforces fee limits before submission. A zero fee limit allows only zero-fee routes. Invalid or amountless invoices are rejected before the wallet is called. npm @lightninglabs/l402 0.2.0 was published 2026-10-29T13:46:37.700Z and its repository is this project. The GitHub releases API returned 404 for tag v0.2.0 on 2026-11-04. This replaces the lightninglabs-l402sdk row. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).,l402; lightning; sdk; release,2026-11-04,true,2026-11-04,200,
9
  eclair-v0-14-6-release,Eclair v0.14.6,ACINQ (GitHub),,2026-10-27,https://github.com/ACINQ/eclair/releases/tag/v0.14.6,repo,bitcoin-lightning,product_docs,"Patch release published 2026-10-27. GitHub marks it not a prerelease. The release says it contains security hardening fixes that malicious nodes could exploit, and thanks @erickcestari for responsible disclosures. The release notes add require-confirmed-inputs-for-splicing, enabled by default, so splices spend only confirmed inputs. They say setting it to false is unsafe because a peer may double-spend an unconfirmed parent after signing. The release says it is fully compatible with previous versions and that channels do not need to be closed. Notes: https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.14.6.md.",eclair; lightning; release; security; trampoline; splicing,2026-10-31,true,2026-10-31,200,
10
  getalby-js-sdk-v9-0-0-release,Release v9.0.0 · getAlby/js-sdk,GitHub (Alby),,2026-10-27,https://github.com/getAlby/js-sdk/releases/tag/v9.0.0,repo,bitcoin-lightning,product_docs,"Breaking release published 2026-10-27. The notes say Nip47TimeoutValues.publishTimeout is removed and the publish timeout is fixed per client, while replyTimeout stays per method. A relay that does not reply OK within 5 seconds now rejects with Nip47PublishTimeoutError. Deprecated nwc multi_* methods are removed, matching their removal from NIP-47, and Nip47Method replaces Nip47SingleMethod. An NWC reply that fails to decrypt is rejected. The full changelog link is v8.1.1...v9.0.0. This replaces the library row for v8.1.0.",nwc; nostr; lightning; agent-wallets; tools,2026-11-03,true,2026-11-03,200,
@@ -77,6 +80,7 @@ visa-trusted-agent-protocol-press-release,Visa Introduces Trusted Agent Protocol
77
  mastercard-agentic-commerce-tools-sep-2025,"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce",Mastercard,,2025-09-10,"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",announcement,payments,news,"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",card-networks; tokenization; identity,2026-10-20,,2026-10-20,403,"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"
78
  cloudflare-pay-per-crawl,Introducing pay per crawl: Enabling content owners to charge AI crawlers for access,Cloudflare Blog,,2025-07-01,https://blog.cloudflare.com/introducing-pay-per-crawl/,announcement,payments,news,"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",m2m-payments; micropayments; web-agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/
79
  x402-whitepaper,x402: An open standard for internet-native payments,Coinbase Developer Platform,Erik Reppel; Ronnie Caspers; Kevin Leffew; Danny Organ; Dan Kim; Nemil Dalal,2025-05-06,https://www.x402.org/x402-whitepaper.pdf,spec,payments,research,"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",x402; stablecoins; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf
 
80
  link-balance-agent-wallet-purchases,Set up a balance for agent wallet purchases,Link (Stripe),,,https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases,docs,payments,product_docs,"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.",agent-wallets; stablecoins,2026-11-03,,2026-11-03,200,
81
  coinbase-business-accept-x402-payments,Accept Agentic Payments with x402,Coinbase Developer Platform,,,https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments,docs,payments,product_docs,"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.",x402; stablecoins,2026-10-31,,2026-10-31,200,
82
  x402-org,x402,x402,,,https://www.x402.org/,spec,payments,product_docs,"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",x402; m2m-payments; stablecoins,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261012224709/https://x402.org/
 
1
  id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
2
+ bitcoin-optech-newsletter-430,Bitcoin Optech Newsletter #430,Bitcoin Optech,,2026-11-06,https://bitcoinops.org/en/newsletters/2026/11/06/,report,bitcoin-lightning,news,"Newsletter dated 2026-11-06. The releases section calls LND v0.21.6-beta and v0.20.7-beta security releases that include the Linux CVE-2026-98432 mitigation described under LND #11456, and says that mitigation does not fix the kernel. It calls Core Lightning 26.06.10 a security release for dual funding, splicing, onchain HTLC resolution, access controls, and other components, with tests temporarily withheld. It calls BTCPay Server 2.4.7 a security release for 85 findings from Anthropic's OSS Scanner, including payout limits, other stores' data, authentication, and resource exhaustion. Separate from those release announcements, the notable-changes section describes LND #11357 as rejecting duplicate BOLT11 payment secrets and incorrect lengths for the payment hash, description hash, payment secret, and receiver public key, instead of ignoring extras or treating a bad length as absent. It describes Core Lightning #9419 as adding an optional failure_reason on listforwards and forward_event for local forwarding failures, and #9592 as making xpay exclude a forwarding node for the rest of a payment after unknown_next_peer twice. The newsletter also covers an ongoing TCP hole-punching discussion and a draft co-signer spending policy that is not assigned a BIP number.",bitcoin; lightning; bolt11; lnd; core-lightning; ldk; btcpay; optech,2026-11-07,true,2026-11-07,200,
3
+ breez-sdk-spark-0-28-0,Breez SDK 0.28 (Spark),Breez (GitHub),,2026-11-05,https://github.com/breez/spark-sdk/releases/tag/0.28.0,repo,bitcoin-lightning,spec_released,"Release 0.28.0 published 2026-11-05, not a prerelease. The notes add a bridging client to pay a Spark, Lightning, or USDC/USDT address from another chain or over Lightning. USDC and USDT in that sentence are addresses on another chain, not a claim that the SDK treats them as native Lightning assets. The notes add sending to BIP-352 silent payment addresses and a change that rejects expired Lightning invoices. They also say the parser follows BIP-321 and restricts BIP-353 lookups. Compare: https://github.com/breez/spark-sdk/compare/0.27.0...0.28.0.",lightning; spark; breez; sdk; bip352; release,2026-11-07,true,2026-11-07,200,
4
  getalby-hub-v1-24-6-release,Release v1.24.6 Julian Assange · getAlby/hub,GitHub (Alby),,2026-11-05,https://github.com/getAlby/hub/releases/tag/v1.24.6,repo,bitcoin-lightning,product_docs,"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.",lightning; nwc; agent-wallets; security; tools,2026-11-06,true,2026-11-06,200,
5
  aperture-v0-6-0-release,Aperture v0.6.0,Lightning Labs,,2026-11-05,https://github.com/lightninglabs/aperture/releases/tag/v0.6.0,repo,bitcoin-lightning,product_docs,"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",l402; lightning; m2m-payments; release,2026-11-05,true,2026-11-05,200,
6
  core-lightning-v26-06-10,Core Lightning v26.06.10,Elements Project,,2026-11-04,https://github.com/ElementsProject/lightning/releases/tag/v26.06.10,repo,bitcoin-lightning,product_docs,"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",lightning; release; security,2026-11-05,true,2026-11-05,200,
7
  wavelength-v0-2-1-release,Wavelength v0.2.1,Lightning Labs (GitHub),,2026-10-31,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1,repo,bitcoin-lightning,spec_released,"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.",lightning; ark; wallet; release,2026-11-03,true,2026-11-03,200,
8
  lnd-v0-21-6-beta,lnd v0.21.6-beta and v0.20.7-beta,Lightning Labs (GitHub),,2026-10-30,https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta,repo,bitcoin-lightning,product_docs,"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.",lnd; lightning; release; security,2026-11-03,true,2026-11-03,200,
9
  bitcoin-optech-newsletter-429,Bitcoin Optech Newsletter #429,Bitcoin Optech,,2026-10-30,https://bitcoinops.org/en/newsletters/2026/10/30/,report,bitcoin-lightning,news,"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.",bitcoin; lightning; security; optech,2026-10-31,true,2026-10-31,200,
10
+ btcpay-server-v2-4-7,BTCPay Server v2.4.7,BTCPay Server (GitHub),,2026-10-29,https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.7,repo,bitcoin-lightning,spec_released,"Release v2.4.7 published 2026-10-29, not a prerelease. The notes call it a bug-fix release for security, reliability, and payment accounting, and recommend updating, especially for servers shared by multiple merchants. The release says it fixes 85 security findings from Anthropic's OSS Scanner, using that report's severity ratings: 1 critical, 13 high, 52 medium, and 19 low. Those figures are the release's own table, not a CVE list. Named fixes include payout state changes that bypassed pull-payment limits, checkout forms restricted to the owning store, and BitPay API changes that apply the store's confirmation and expiry limits to anonymously created invoices and limit posData to 64 KiB before parsing. The release does not say every vulnerability in BTCPay is fixed.",bitcoin; lightning; btcpay; merchant; security,2026-11-07,true,2026-11-07,200,
11
  l402sdk-v0-2-0-release,L402sdk 0.2.0,Lightning Labs,,2026-10-29,https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md,repo,bitcoin-lightning,product_docs,L402sdk 0.2.0 is dated 2026-10-29 in CHANGELOG.md. Budgets include routing fees and concurrent payment reservations. Automatic payments require a backend that enforces fee limits before submission. A zero fee limit allows only zero-fee routes. Invalid or amountless invoices are rejected before the wallet is called. npm @lightninglabs/l402 0.2.0 was published 2026-10-29T13:46:37.700Z and its repository is this project. The GitHub releases API returned 404 for tag v0.2.0 on 2026-11-04. This replaces the lightninglabs-l402sdk row. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).,l402; lightning; sdk; release,2026-11-04,true,2026-11-04,200,
12
  eclair-v0-14-6-release,Eclair v0.14.6,ACINQ (GitHub),,2026-10-27,https://github.com/ACINQ/eclair/releases/tag/v0.14.6,repo,bitcoin-lightning,product_docs,"Patch release published 2026-10-27. GitHub marks it not a prerelease. The release says it contains security hardening fixes that malicious nodes could exploit, and thanks @erickcestari for responsible disclosures. The release notes add require-confirmed-inputs-for-splicing, enabled by default, so splices spend only confirmed inputs. They say setting it to false is unsafe because a peer may double-spend an unconfirmed parent after signing. The release says it is fully compatible with previous versions and that channels do not need to be closed. Notes: https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.14.6.md.",eclair; lightning; release; security; trampoline; splicing,2026-10-31,true,2026-10-31,200,
13
  getalby-js-sdk-v9-0-0-release,Release v9.0.0 · getAlby/js-sdk,GitHub (Alby),,2026-10-27,https://github.com/getAlby/js-sdk/releases/tag/v9.0.0,repo,bitcoin-lightning,product_docs,"Breaking release published 2026-10-27. The notes say Nip47TimeoutValues.publishTimeout is removed and the publish timeout is fixed per client, while replyTimeout stays per method. A relay that does not reply OK within 5 seconds now rejects with Nip47PublishTimeoutError. Deprecated nwc multi_* methods are removed, matching their removal from NIP-47, and Nip47Method replaces Nip47SingleMethod. An NWC reply that fails to decrypt is rejected. The full changelog link is v8.1.1...v9.0.0. This replaces the library row for v8.1.0.",nwc; nostr; lightning; agent-wallets; tools,2026-11-03,true,2026-11-03,200,
 
80
  mastercard-agentic-commerce-tools-sep-2025,"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce",Mastercard,,2025-09-10,"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",announcement,payments,news,"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",card-networks; tokenization; identity,2026-10-20,,2026-10-20,403,"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"
81
  cloudflare-pay-per-crawl,Introducing pay per crawl: Enabling content owners to charge AI crawlers for access,Cloudflare Blog,,2025-07-01,https://blog.cloudflare.com/introducing-pay-per-crawl/,announcement,payments,news,"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",m2m-payments; micropayments; web-agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/
82
  x402-whitepaper,x402: An open standard for internet-native payments,Coinbase Developer Platform,Erik Reppel; Ronnie Caspers; Kevin Leffew; Danny Organ; Dan Kim; Nemil Dalal,2025-05-06,https://www.x402.org/x402-whitepaper.pdf,spec,payments,research,"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",x402; stablecoins; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf
83
+ circle-agent-marketplace-discovery-api,Discover x402 services,Circle,,,https://developers.circle.com/agent-stack/agent-marketplace/discovery-api,docs,payments,product_docs,"Circle's discovery page, checked 2026-11-07, says one public endpoint lists x402 services that accept USDC, with no API key and no account. The documented request is GET https://api.circle.com/v2/x402/discovery/resources. A read of that URL with limit=1 on the same day returned HTTP 200 and JSON with x402Version 2, items[].accepts[] carrying scheme, network, asset, amount, and payTo, metadata.input and metadata.output, and pagination.limit, offset, and total. The page documents filters for category, network, maxUsdPrice, supportsVanillax402, supportsCircleGateway, and siwx, and a type of http or mcp. It says limit defaults to 50 and the maximum is 200. The page links https://agents.circle.com/.well-known/openapi.json, which returned HTTP 200 the same day. This is Circle's catalog. It is not an Agent Paywire listing, and this card does not record a catalog total because that number changes.",x402; directory; discovery; openapi; usdc,2026-11-07,,2026-11-07,200,
84
  link-balance-agent-wallet-purchases,Set up a balance for agent wallet purchases,Link (Stripe),,,https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases,docs,payments,product_docs,"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.",agent-wallets; stablecoins,2026-11-03,,2026-11-03,200,
85
  coinbase-business-accept-x402-payments,Accept Agentic Payments with x402,Coinbase Developer Platform,,,https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments,docs,payments,product_docs,"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.",x402; stablecoins,2026-10-31,,2026-10-31,200,
86
  x402-org,x402,x402,,,https://www.x402.org/,spec,payments,product_docs,"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",x402; m2m-payments; stablecoins,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261012224709/https://x402.org/
data/sources.jsonl CHANGED
@@ -1,9 +1,12 @@
 
 
1
  {"id":"getalby-hub-v1-24-6-release","title":"Release v1.24.6 Julian Assange · getAlby/hub","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-11-05","url":"https://github.com/getAlby/hub/releases/tag/v1.24.6","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.","tags":["lightning","nwc","agent-wallets","security","tools"],"verified_at":"2026-11-06","featured":true,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
2
  {"id":"aperture-v0-6-0-release","title":"Aperture v0.6.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-11-05","url":"https://github.com/lightninglabs/aperture/releases/tag/v0.6.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.","tags":["l402","lightning","m2m-payments","release"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
3
  {"id":"core-lightning-v26-06-10","title":"Core Lightning v26.06.10","publisher":"Elements Project","authors":[],"date_published":"2026-11-04","url":"https://github.com/ElementsProject/lightning/releases/tag/v26.06.10","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.","tags":["lightning","release","security"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
4
  {"id":"wavelength-v0-2-1-release","title":"Wavelength v0.2.1","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-31","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
5
  {"id":"lnd-v0-21-6-beta","title":"lnd v0.21.6-beta and v0.20.7-beta","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-30","url":"https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.","tags":["lnd","lightning","release","security"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
6
  {"id":"bitcoin-optech-newsletter-429","title":"Bitcoin Optech Newsletter #429","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-30","url":"https://bitcoinops.org/en/newsletters/2026/10/30/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.","tags":["bitcoin","lightning","security","optech"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
 
7
  {"id":"l402sdk-v0-2-0-release","title":"L402sdk 0.2.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-29","url":"https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"L402sdk 0.2.0 is dated 2026-10-29 in CHANGELOG.md. Budgets include routing fees and concurrent payment reservations. Automatic payments require a backend that enforces fee limits before submission. A zero fee limit allows only zero-fee routes. Invalid or amountless invoices are rejected before the wallet is called. npm @lightninglabs/l402 0.2.0 was published 2026-10-29T13:46:37.700Z and its repository is this project. The GitHub releases API returned 404 for tag v0.2.0 on 2026-11-04. This replaces the lightninglabs-l402sdk row. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).","tags":["l402","lightning","sdk","release"],"verified_at":"2026-11-04","featured":true,"last_checked":"2026-11-04","http_status":200,"archive_url":null}
8
  {"id":"eclair-v0-14-6-release","title":"Eclair v0.14.6","publisher":"ACINQ (GitHub)","authors":[],"date_published":"2026-10-27","url":"https://github.com/ACINQ/eclair/releases/tag/v0.14.6","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release published 2026-10-27. GitHub marks it not a prerelease. The release says it contains security hardening fixes that malicious nodes could exploit, and thanks @erickcestari for responsible disclosures. The release notes add require-confirmed-inputs-for-splicing, enabled by default, so splices spend only confirmed inputs. They say setting it to false is unsafe because a peer may double-spend an unconfirmed parent after signing. The release says it is fully compatible with previous versions and that channels do not need to be closed. Notes: https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.14.6.md.","tags":["eclair","lightning","release","security","trampoline","splicing"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
9
  {"id":"getalby-js-sdk-v9-0-0-release","title":"Release v9.0.0 · getAlby/js-sdk","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-10-27","url":"https://github.com/getAlby/js-sdk/releases/tag/v9.0.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Breaking release published 2026-10-27. The notes say Nip47TimeoutValues.publishTimeout is removed and the publish timeout is fixed per client, while replyTimeout stays per method. A relay that does not reply OK within 5 seconds now rejects with Nip47PublishTimeoutError. Deprecated nwc multi_* methods are removed, matching their removal from NIP-47, and Nip47Method replaces Nip47SingleMethod. An NWC reply that fails to decrypt is rejected. The full changelog link is v8.1.1...v9.0.0. This replaces the library row for v8.1.0.","tags":["nwc","nostr","lightning","agent-wallets","tools"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
@@ -76,6 +79,7 @@
76
  {"id":"mastercard-agentic-commerce-tools-sep-2025","title":"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce","publisher":"Mastercard","authors":[],"date_published":"2025-09-10","url":"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html","type":"announcement","category":"payments","status":"news","summary":"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.","tags":["card-networks","tokenization","identity"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":403,"archive_url":"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"}
77
  {"id":"cloudflare-pay-per-crawl","title":"Introducing pay per crawl: Enabling content owners to charge AI crawlers for access","publisher":"Cloudflare Blog","authors":[],"date_published":"2025-07-01","url":"https://blog.cloudflare.com/introducing-pay-per-crawl/","type":"announcement","category":"payments","status":"news","summary":"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.","tags":["m2m-payments","micropayments","web-agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/"}
78
  {"id":"x402-whitepaper","title":"x402: An open standard for internet-native payments","publisher":"Coinbase Developer Platform","authors":["Erik Reppel","Ronnie Caspers","Kevin Leffew","Danny Organ","Dan Kim","Nemil Dalal"],"date_published":"2025-05-06","url":"https://www.x402.org/x402-whitepaper.pdf","type":"spec","category":"payments","status":"research","summary":"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.","tags":["x402","stablecoins","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"}
 
79
  {"id":"link-balance-agent-wallet-purchases","title":"Set up a balance for agent wallet purchases","publisher":"Link (Stripe)","authors":[],"date_published":null,"url":"https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases","type":"docs","category":"payments","status":"product_docs","summary":"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.","tags":["agent-wallets","stablecoins"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
80
  {"id":"coinbase-business-accept-x402-payments","title":"Accept Agentic Payments with x402","publisher":"Coinbase Developer Platform","authors":[],"date_published":null,"url":"https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments","type":"docs","category":"payments","status":"product_docs","summary":"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.","tags":["x402","stablecoins"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
81
  {"id":"x402-org","title":"x402","publisher":"x402","authors":[],"date_published":null,"url":"https://www.x402.org/","type":"spec","category":"payments","status":"product_docs","summary":"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.","tags":["x402","m2m-payments","stablecoins"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261012224709/https://x402.org/"}
 
1
+ {"id":"bitcoin-optech-newsletter-430","title":"Bitcoin Optech Newsletter #430","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-11-06","url":"https://bitcoinops.org/en/newsletters/2026/11/06/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter dated 2026-11-06. The releases section calls LND v0.21.6-beta and v0.20.7-beta security releases that include the Linux CVE-2026-98432 mitigation described under LND #11456, and says that mitigation does not fix the kernel. It calls Core Lightning 26.06.10 a security release for dual funding, splicing, onchain HTLC resolution, access controls, and other components, with tests temporarily withheld. It calls BTCPay Server 2.4.7 a security release for 85 findings from Anthropic's OSS Scanner, including payout limits, other stores' data, authentication, and resource exhaustion. Separate from those release announcements, the notable-changes section describes LND #11357 as rejecting duplicate BOLT11 payment secrets and incorrect lengths for the payment hash, description hash, payment secret, and receiver public key, instead of ignoring extras or treating a bad length as absent. It describes Core Lightning #9419 as adding an optional failure_reason on listforwards and forward_event for local forwarding failures, and #9592 as making xpay exclude a forwarding node for the rest of a payment after unknown_next_peer twice. The newsletter also covers an ongoing TCP hole-punching discussion and a draft co-signer spending policy that is not assigned a BIP number.","tags":["bitcoin","lightning","bolt11","lnd","core-lightning","ldk","btcpay","optech"],"verified_at":"2026-11-07","featured":true,"last_checked":"2026-11-07","http_status":200,"archive_url":null}
2
+ {"id":"breez-sdk-spark-0-28-0","title":"Breez SDK 0.28 (Spark)","publisher":"Breez (GitHub)","authors":[],"date_published":"2026-11-05","url":"https://github.com/breez/spark-sdk/releases/tag/0.28.0","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release 0.28.0 published 2026-11-05, not a prerelease. The notes add a bridging client to pay a Spark, Lightning, or USDC/USDT address from another chain or over Lightning. USDC and USDT in that sentence are addresses on another chain, not a claim that the SDK treats them as native Lightning assets. The notes add sending to BIP-352 silent payment addresses and a change that rejects expired Lightning invoices. They also say the parser follows BIP-321 and restricts BIP-353 lookups. Compare: https://github.com/breez/spark-sdk/compare/0.27.0...0.28.0.","tags":["lightning","spark","breez","sdk","bip352","release"],"verified_at":"2026-11-07","featured":true,"last_checked":"2026-11-07","http_status":200,"archive_url":null}
3
  {"id":"getalby-hub-v1-24-6-release","title":"Release v1.24.6 Julian Assange · getAlby/hub","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-11-05","url":"https://github.com/getAlby/hub/releases/tag/v1.24.6","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.","tags":["lightning","nwc","agent-wallets","security","tools"],"verified_at":"2026-11-06","featured":true,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
4
  {"id":"aperture-v0-6-0-release","title":"Aperture v0.6.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-11-05","url":"https://github.com/lightninglabs/aperture/releases/tag/v0.6.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.","tags":["l402","lightning","m2m-payments","release"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
5
  {"id":"core-lightning-v26-06-10","title":"Core Lightning v26.06.10","publisher":"Elements Project","authors":[],"date_published":"2026-11-04","url":"https://github.com/ElementsProject/lightning/releases/tag/v26.06.10","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.","tags":["lightning","release","security"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
6
  {"id":"wavelength-v0-2-1-release","title":"Wavelength v0.2.1","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-31","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
7
  {"id":"lnd-v0-21-6-beta","title":"lnd v0.21.6-beta and v0.20.7-beta","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-30","url":"https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security releases published 2026-10-30. v0.21.6-beta at 23:21 UTC is the newest non-prerelease on the 0.21 line. v0.20.7-beta at 22:37 UTC is the matching 0.20 tag. Both release bodies name CVE-2026-98432 and say there are no database migrations. The v0.21.6 notes say the demonstrated exploit needs an MPTCP listener, which Go 1.24+ enables by default, that Windows and macOS are not affected, and that lnd no longer opens MPTCP listeners. They tell Linux operators to upgrade, set net.mptcp.enabled=0, and install a patched kernel, and to start an unupgraded binary with GODEBUG=multipathtcp=0. The notes do not name kernel version numbers. This replaces the library row for v0.21.5-beta. Notes: https://github.com/lightningnetwork/lnd/blob/v0.21.6-beta/docs/release-notes/release-notes-0.21.6.md. The 0.20 tag: https://github.com/lightningnetwork/lnd/releases/tag/v0.20.7-beta.","tags":["lnd","lightning","release","security"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
8
  {"id":"bitcoin-optech-newsletter-429","title":"Bitcoin Optech Newsletter #429","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-30","url":"https://bitcoinops.org/en/newsletters/2026/10/30/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter dated 2026-10-30. It discloses a denial-of-service in Core Lightning 25.02 through 26.04: a channel announcement that names the same node as both endpoints passed validation, was stored, and then crashed gossipd on a no-duplicates assertion. The stored message crashed the node again on every restart until the operator removed it by hand, which upgrading alone did not do. The fix is CLN 26.04.1, which rejects an announcement whose node_id_1 is not strictly less than node_id_2. BOLTs #1333 added the same receiver check to BOLT7, which had only required senders to order the IDs.","tags":["bitcoin","lightning","security","optech"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
9
+ {"id":"btcpay-server-v2-4-7","title":"BTCPay Server v2.4.7","publisher":"BTCPay Server (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/btcpayserver/btcpayserver/releases/tag/v2.4.7","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release v2.4.7 published 2026-10-29, not a prerelease. The notes call it a bug-fix release for security, reliability, and payment accounting, and recommend updating, especially for servers shared by multiple merchants. The release says it fixes 85 security findings from Anthropic's OSS Scanner, using that report's severity ratings: 1 critical, 13 high, 52 medium, and 19 low. Those figures are the release's own table, not a CVE list. Named fixes include payout state changes that bypassed pull-payment limits, checkout forms restricted to the owning store, and BitPay API changes that apply the store's confirmation and expiry limits to anonymously created invoices and limit posData to 64 KiB before parsing. The release does not say every vulnerability in BTCPay is fixed.","tags":["bitcoin","lightning","btcpay","merchant","security"],"verified_at":"2026-11-07","featured":true,"last_checked":"2026-11-07","http_status":200,"archive_url":null}
10
  {"id":"l402sdk-v0-2-0-release","title":"L402sdk 0.2.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-29","url":"https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"L402sdk 0.2.0 is dated 2026-10-29 in CHANGELOG.md. Budgets include routing fees and concurrent payment reservations. Automatic payments require a backend that enforces fee limits before submission. A zero fee limit allows only zero-fee routes. Invalid or amountless invoices are rejected before the wallet is called. npm @lightninglabs/l402 0.2.0 was published 2026-10-29T13:46:37.700Z and its repository is this project. The GitHub releases API returned 404 for tag v0.2.0 on 2026-11-04. This replaces the lightninglabs-l402sdk row. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).","tags":["l402","lightning","sdk","release"],"verified_at":"2026-11-04","featured":true,"last_checked":"2026-11-04","http_status":200,"archive_url":null}
11
  {"id":"eclair-v0-14-6-release","title":"Eclair v0.14.6","publisher":"ACINQ (GitHub)","authors":[],"date_published":"2026-10-27","url":"https://github.com/ACINQ/eclair/releases/tag/v0.14.6","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release published 2026-10-27. GitHub marks it not a prerelease. The release says it contains security hardening fixes that malicious nodes could exploit, and thanks @erickcestari for responsible disclosures. The release notes add require-confirmed-inputs-for-splicing, enabled by default, so splices spend only confirmed inputs. They say setting it to false is unsafe because a peer may double-spend an unconfirmed parent after signing. The release says it is fully compatible with previous versions and that channels do not need to be closed. Notes: https://github.com/ACINQ/eclair/blob/master/docs/release-notes/eclair-v0.14.6.md.","tags":["eclair","lightning","release","security","trampoline","splicing"],"verified_at":"2026-10-31","featured":true,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
12
  {"id":"getalby-js-sdk-v9-0-0-release","title":"Release v9.0.0 · getAlby/js-sdk","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-10-27","url":"https://github.com/getAlby/js-sdk/releases/tag/v9.0.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Breaking release published 2026-10-27. The notes say Nip47TimeoutValues.publishTimeout is removed and the publish timeout is fixed per client, while replyTimeout stays per method. A relay that does not reply OK within 5 seconds now rejects with Nip47PublishTimeoutError. Deprecated nwc multi_* methods are removed, matching their removal from NIP-47, and Nip47Method replaces Nip47SingleMethod. An NWC reply that fails to decrypt is rejected. The full changelog link is v8.1.1...v9.0.0. This replaces the library row for v8.1.0.","tags":["nwc","nostr","lightning","agent-wallets","tools"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
 
79
  {"id":"mastercard-agentic-commerce-tools-sep-2025","title":"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce","publisher":"Mastercard","authors":[],"date_published":"2025-09-10","url":"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html","type":"announcement","category":"payments","status":"news","summary":"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.","tags":["card-networks","tokenization","identity"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":403,"archive_url":"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"}
80
  {"id":"cloudflare-pay-per-crawl","title":"Introducing pay per crawl: Enabling content owners to charge AI crawlers for access","publisher":"Cloudflare Blog","authors":[],"date_published":"2025-07-01","url":"https://blog.cloudflare.com/introducing-pay-per-crawl/","type":"announcement","category":"payments","status":"news","summary":"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.","tags":["m2m-payments","micropayments","web-agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/"}
81
  {"id":"x402-whitepaper","title":"x402: An open standard for internet-native payments","publisher":"Coinbase Developer Platform","authors":["Erik Reppel","Ronnie Caspers","Kevin Leffew","Danny Organ","Dan Kim","Nemil Dalal"],"date_published":"2025-05-06","url":"https://www.x402.org/x402-whitepaper.pdf","type":"spec","category":"payments","status":"research","summary":"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.","tags":["x402","stablecoins","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"}
82
+ {"id":"circle-agent-marketplace-discovery-api","title":"Discover x402 services","publisher":"Circle","authors":[],"date_published":null,"url":"https://developers.circle.com/agent-stack/agent-marketplace/discovery-api","type":"docs","category":"payments","status":"product_docs","summary":"Circle's discovery page, checked 2026-11-07, says one public endpoint lists x402 services that accept USDC, with no API key and no account. The documented request is GET https://api.circle.com/v2/x402/discovery/resources. A read of that URL with limit=1 on the same day returned HTTP 200 and JSON with x402Version 2, items[].accepts[] carrying scheme, network, asset, amount, and payTo, metadata.input and metadata.output, and pagination.limit, offset, and total. The page documents filters for category, network, maxUsdPrice, supportsVanillax402, supportsCircleGateway, and siwx, and a type of http or mcp. It says limit defaults to 50 and the maximum is 200. The page links https://agents.circle.com/.well-known/openapi.json, which returned HTTP 200 the same day. This is Circle's catalog. It is not an Agent Paywire listing, and this card does not record a catalog total because that number changes.","tags":["x402","directory","discovery","openapi","usdc"],"verified_at":"2026-11-07","featured":false,"last_checked":"2026-11-07","http_status":200,"archive_url":null}
83
  {"id":"link-balance-agent-wallet-purchases","title":"Set up a balance for agent wallet purchases","publisher":"Link (Stripe)","authors":[],"date_published":null,"url":"https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases","type":"docs","category":"payments","status":"product_docs","summary":"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.","tags":["agent-wallets","stablecoins"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
84
  {"id":"coinbase-business-accept-x402-payments","title":"Accept Agentic Payments with x402","publisher":"Coinbase Developer Platform","authors":[],"date_published":null,"url":"https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments","type":"docs","category":"payments","status":"product_docs","summary":"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.","tags":["x402","stablecoins"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
85
  {"id":"x402-org","title":"x402","publisher":"x402","authors":[],"date_published":null,"url":"https://www.x402.org/","type":"spec","category":"payments","status":"product_docs","summary":"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.","tags":["x402","m2m-payments","stablecoins"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261012224709/https://x402.org/"}
data/tags.json CHANGED
@@ -1,7 +1,7 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-06T00:00:00Z",
4
- "count": 70,
5
  "tags": [
6
  {
7
  "tag": "a2a",
@@ -63,11 +63,21 @@
63
  "count": 8,
64
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
65
  },
 
 
 
 
 
66
  {
67
  "tag": "bitcoin",
68
- "count": 14,
69
  "json_url": "https://agentpaywire.com/api/library/tag/bitcoin.json"
70
  },
 
 
 
 
 
71
  {
72
  "tag": "bolt12",
73
  "count": 4,
@@ -79,8 +89,13 @@
79
  "json_url": "https://agentpaywire.com/api/library/tag/bot-access.json"
80
  },
81
  {
82
- "tag": "btcpay",
83
  "count": 1,
 
 
 
 
 
84
  "json_url": "https://agentpaywire.com/api/library/tag/btcpay.json"
85
  },
86
  {
@@ -88,6 +103,11 @@
88
  "count": 11,
89
  "json_url": "https://agentpaywire.com/api/library/tag/card-networks.json"
90
  },
 
 
 
 
 
91
  {
92
  "tag": "dataset",
93
  "count": 2,
@@ -95,9 +115,14 @@
95
  },
96
  {
97
  "tag": "directory",
98
- "count": 17,
99
  "json_url": "https://agentpaywire.com/api/library/tag/directory.json"
100
  },
 
 
 
 
 
101
  {
102
  "tag": "eclair",
103
  "count": 2,
@@ -140,7 +165,7 @@
140
  },
141
  {
142
  "tag": "ldk",
143
- "count": 1,
144
  "json_url": "https://agentpaywire.com/api/library/tag/ldk.json"
145
  },
146
  {
@@ -150,7 +175,7 @@
150
  },
151
  {
152
  "tag": "lightning",
153
- "count": 44,
154
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
155
  },
156
  {
@@ -160,7 +185,7 @@
160
  },
161
  {
162
  "tag": "lnd",
163
- "count": 2,
164
  "json_url": "https://agentpaywire.com/api/library/tag/lnd.json"
165
  },
166
  {
@@ -193,6 +218,11 @@
193
  "count": 30,
194
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
195
  },
 
 
 
 
 
196
  {
197
  "tag": "merchant-readiness",
198
  "count": 1,
@@ -225,12 +255,12 @@
225
  },
226
  {
227
  "tag": "openapi",
228
- "count": 5,
229
  "json_url": "https://agentpaywire.com/api/library/tag/openapi.json"
230
  },
231
  {
232
  "tag": "optech",
233
- "count": 2,
234
  "json_url": "https://agentpaywire.com/api/library/tag/optech.json"
235
  },
236
  {
@@ -250,7 +280,7 @@
250
  },
251
  {
252
  "tag": "release",
253
- "count": 6,
254
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
255
  },
256
  {
@@ -270,12 +300,12 @@
270
  },
271
  {
272
  "tag": "sdk",
273
- "count": 4,
274
  "json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
275
  },
276
  {
277
  "tag": "security",
278
- "count": 33,
279
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
280
  },
281
  {
@@ -288,6 +318,11 @@
288
  "count": 1,
289
  "json_url": "https://agentpaywire.com/api/library/tag/solana.json"
290
  },
 
 
 
 
 
291
  {
292
  "tag": "spend-controls",
293
  "count": 2,
@@ -328,6 +363,11 @@
328
  "count": 1,
329
  "json_url": "https://agentpaywire.com/api/library/tag/trampoline.json"
330
  },
 
 
 
 
 
331
  {
332
  "tag": "vulnerabilities",
333
  "count": 1,
@@ -350,7 +390,7 @@
350
  },
351
  {
352
  "tag": "x402",
353
- "count": 34,
354
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
355
  }
356
  ]
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-07T00:00:00Z",
4
+ "count": 78,
5
  "tags": [
6
  {
7
  "tag": "a2a",
 
63
  "count": 8,
64
  "json_url": "https://agentpaywire.com/api/library/tag/benchmark.json"
65
  },
66
+ {
67
+ "tag": "bip352",
68
+ "count": 1,
69
+ "json_url": "https://agentpaywire.com/api/library/tag/bip352.json"
70
+ },
71
  {
72
  "tag": "bitcoin",
73
+ "count": 16,
74
  "json_url": "https://agentpaywire.com/api/library/tag/bitcoin.json"
75
  },
76
+ {
77
+ "tag": "bolt11",
78
+ "count": 1,
79
+ "json_url": "https://agentpaywire.com/api/library/tag/bolt11.json"
80
+ },
81
  {
82
  "tag": "bolt12",
83
  "count": 4,
 
89
  "json_url": "https://agentpaywire.com/api/library/tag/bot-access.json"
90
  },
91
  {
92
+ "tag": "breez",
93
  "count": 1,
94
+ "json_url": "https://agentpaywire.com/api/library/tag/breez.json"
95
+ },
96
+ {
97
+ "tag": "btcpay",
98
+ "count": 3,
99
  "json_url": "https://agentpaywire.com/api/library/tag/btcpay.json"
100
  },
101
  {
 
103
  "count": 11,
104
  "json_url": "https://agentpaywire.com/api/library/tag/card-networks.json"
105
  },
106
+ {
107
+ "tag": "core-lightning",
108
+ "count": 1,
109
+ "json_url": "https://agentpaywire.com/api/library/tag/core-lightning.json"
110
+ },
111
  {
112
  "tag": "dataset",
113
  "count": 2,
 
115
  },
116
  {
117
  "tag": "directory",
118
+ "count": 18,
119
  "json_url": "https://agentpaywire.com/api/library/tag/directory.json"
120
  },
121
+ {
122
+ "tag": "discovery",
123
+ "count": 1,
124
+ "json_url": "https://agentpaywire.com/api/library/tag/discovery.json"
125
+ },
126
  {
127
  "tag": "eclair",
128
  "count": 2,
 
165
  },
166
  {
167
  "tag": "ldk",
168
+ "count": 2,
169
  "json_url": "https://agentpaywire.com/api/library/tag/ldk.json"
170
  },
171
  {
 
175
  },
176
  {
177
  "tag": "lightning",
178
+ "count": 47,
179
  "json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
180
  },
181
  {
 
185
  },
186
  {
187
  "tag": "lnd",
188
+ "count": 3,
189
  "json_url": "https://agentpaywire.com/api/library/tag/lnd.json"
190
  },
191
  {
 
218
  "count": 30,
219
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
220
  },
221
+ {
222
+ "tag": "merchant",
223
+ "count": 1,
224
+ "json_url": "https://agentpaywire.com/api/library/tag/merchant.json"
225
+ },
226
  {
227
  "tag": "merchant-readiness",
228
  "count": 1,
 
255
  },
256
  {
257
  "tag": "openapi",
258
+ "count": 6,
259
  "json_url": "https://agentpaywire.com/api/library/tag/openapi.json"
260
  },
261
  {
262
  "tag": "optech",
263
+ "count": 3,
264
  "json_url": "https://agentpaywire.com/api/library/tag/optech.json"
265
  },
266
  {
 
280
  },
281
  {
282
  "tag": "release",
283
+ "count": 7,
284
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
285
  },
286
  {
 
300
  },
301
  {
302
  "tag": "sdk",
303
+ "count": 5,
304
  "json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
305
  },
306
  {
307
  "tag": "security",
308
+ "count": 34,
309
  "json_url": "https://agentpaywire.com/api/library/tag/security.json"
310
  },
311
  {
 
318
  "count": 1,
319
  "json_url": "https://agentpaywire.com/api/library/tag/solana.json"
320
  },
321
+ {
322
+ "tag": "spark",
323
+ "count": 1,
324
+ "json_url": "https://agentpaywire.com/api/library/tag/spark.json"
325
+ },
326
  {
327
  "tag": "spend-controls",
328
  "count": 2,
 
363
  "count": 1,
364
  "json_url": "https://agentpaywire.com/api/library/tag/trampoline.json"
365
  },
366
+ {
367
+ "tag": "usdc",
368
+ "count": 1,
369
+ "json_url": "https://agentpaywire.com/api/library/tag/usdc.json"
370
+ },
371
  {
372
  "tag": "vulnerabilities",
373
  "count": 1,
 
390
  },
391
  {
392
  "tag": "x402",
393
+ "count": 35,
394
  "json_url": "https://agentpaywire.com/api/library/tag/x402.json"
395
  }
396
  ]