agentpaywire commited on
Commit
8f124ec
·
verified ·
1 Parent(s): 68717c2

Sync library snapshot 2026-11-04 (170 entries; L402sdk 0.2.0, MCP Ruby SDK Tier 1, protocol-facts mcp_sdk_tiers)

Browse files
README.md CHANGED
@@ -26,7 +26,7 @@ configs:
26
 
27
  # Agent Paywire Knowledge Library
28
 
29
- A curated library of **169 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,7 +36,7 @@ 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-03 (last updated 2026-11-03). `verified_at` dates: 2026-10-20 (112 rows), 2026-10-21 (10 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 (2 rows), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-03T00: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)
@@ -45,7 +45,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
45
  | --- | --- |
46
  | bitcoin-lightning (featured) | 39 |
47
  | payments | 70 |
48
- | agent-protocols | 32 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
  | datasets-benchmarks | 8 |
@@ -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, 169 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, 169 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 (79 of 169 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, 169 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 (36 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, 169 rows, single `train` split. Dates are `YYYY-MM-DD`
79
 
80
  | file | contents |
81
  | --- | --- |
82
- | `data/sources.jsonl` | Main table (default config). 169 rows. |
83
- | `data/sources.csv` | Same 169 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 169 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 **170 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-04 (last updated 2026-11-04). `verified_at` dates: 2026-10-20 (112 rows), 2026-10-21 (10 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); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-04T00: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)
 
45
  | --- | --- |
46
  | bitcoin-lightning (featured) | 39 |
47
  | payments | 70 |
48
+ | agent-protocols | 33 |
49
  | robotics-autonomy | 4 |
50
  | iot | 4 |
51
  | datasets-benchmarks | 8 |
 
54
 
55
  ## Fields (`data/sources.jsonl`)
56
 
57
+ One JSON object per line, 170 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 (78 of 170 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 (37 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). 170 rows. |
83
+ | `data/sources.csv` | Same 170 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 170 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,13 +1,13 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-03T00: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": 169,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
@@ -31,7 +31,7 @@
31
  "id": "agent-protocols",
32
  "label": "Agent protocols",
33
  "featured": false,
34
- "count": 32,
35
  "json_url": "https://agentpaywire.com/api/library/agent-protocols.json",
36
  "markdown_url": "https://agentpaywire.com/library/agent-protocols.md",
37
  "html_url": "https://agentpaywire.com/library/agent-protocols/"
@@ -152,6 +152,29 @@
152
  "http_status": 200,
153
  "archive_url": null
154
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
155
  {
156
  "id": "eclair-v0-14-6-release",
157
  "title": "Eclair v0.14.6",
@@ -996,28 +1019,6 @@
996
  "http_status": 200,
997
  "archive_url": null
998
  },
999
- {
1000
- "id": "lightninglabs-l402sdk",
1001
- "title": "lightninglabs/L402sdk",
1002
- "publisher": "GitHub (Lightning Labs)",
1003
- "authors": [],
1004
- "date_published": null,
1005
- "url": "https://github.com/lightninglabs/L402sdk",
1006
- "type": "repo",
1007
- "category": "bitcoin-lightning",
1008
- "status": "product_docs",
1009
- "summary": "Lightning Labs repository for an L402 client SDK for AI agent frameworks. The README says the core is Rust, with TypeScript bindings for the Vercel AI SDK and Python bindings, including LangChain tools, and the TypeScript example constructs a WasmBudgetConfig. The README license is MIT or Apache-2.0. Checked on 2026-10-27: npm has @lightninglabs/l402 0.1.0 and @lightninglabs/l402-ai 0.1.0, and both name this repository. PyPI has l402sdk 0.1.0 and l402sdk-langchain 0.1.0, and both name this repository. The README install line still says pip install l402 and links https://pypi.org/project/l402/, whose homepage is https://github.com/Fewsats/l402-python. PyPI has no project named l402-langchain. crates.io has no crate named l402-core. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).",
1010
- "tags": [
1011
- "l402",
1012
- "lightning",
1013
- "sdk"
1014
- ],
1015
- "verified_at": "2026-10-27",
1016
- "featured": false,
1017
- "last_checked": "2026-10-27",
1018
- "http_status": 200,
1019
- "archive_url": null
1020
- },
1021
  {
1022
  "id": "stripe-link-cli",
1023
  "title": "stripe/link-cli",
@@ -2577,6 +2578,29 @@
2577
  "http_status": 200,
2578
  "archive_url": null
2579
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2580
  {
2581
  "id": "mcp-sep-3392-extension-lifecycle",
2582
  "title": "SEP-3392: Extension Lifecycle",
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-04T00: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": 170,
11
  "categories": [
12
  {
13
  "id": "bitcoin-lightning",
 
31
  "id": "agent-protocols",
32
  "label": "Agent protocols",
33
  "featured": false,
34
+ "count": 33,
35
  "json_url": "https://agentpaywire.com/api/library/agent-protocols.json",
36
  "markdown_url": "https://agentpaywire.com/library/agent-protocols.md",
37
  "html_url": "https://agentpaywire.com/library/agent-protocols/"
 
152
  "http_status": 200,
153
  "archive_url": null
154
  },
155
+ {
156
+ "id": "l402sdk-v0-2-0-release",
157
+ "title": "L402sdk 0.2.0",
158
+ "publisher": "Lightning Labs",
159
+ "authors": [],
160
+ "date_published": "2026-10-29",
161
+ "url": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md",
162
+ "type": "repo",
163
+ "category": "bitcoin-lightning",
164
+ "status": "product_docs",
165
+ "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).",
166
+ "tags": [
167
+ "l402",
168
+ "lightning",
169
+ "sdk",
170
+ "release"
171
+ ],
172
+ "verified_at": "2026-11-04",
173
+ "featured": true,
174
+ "last_checked": "2026-11-04",
175
+ "http_status": 200,
176
+ "archive_url": null
177
+ },
178
  {
179
  "id": "eclair-v0-14-6-release",
180
  "title": "Eclair v0.14.6",
 
1019
  "http_status": 200,
1020
  "archive_url": null
1021
  },
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1022
  {
1023
  "id": "stripe-link-cli",
1024
  "title": "stripe/link-cli",
 
2578
  "http_status": 200,
2579
  "archive_url": null
2580
  },
2581
+ {
2582
+ "id": "mcp-ruby-sdk-tier-1",
2583
+ "title": "The Official Ruby SDK for MCP Reaches Tier 1",
2584
+ "publisher": "Model Context Protocol Blog",
2585
+ "authors": [
2586
+ "Koichi Ito"
2587
+ ],
2588
+ "date_published": "2026-10-30",
2589
+ "url": "https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/",
2590
+ "type": "announcement",
2591
+ "category": "agent-protocols",
2592
+ "status": "news",
2593
+ "summary": "MCP Blog post by Koichi Ito, dated 2026-10-30. The official Ruby SDK is now a Tier 1 SDK, and the post says it joins the TypeScript, Python, C#, Go, and Rust SDKs. Starting with version 1.2.0 of the mcp gem, the post says the SDK fully supports the 2026-07-28 MCP specification. It says the SDK passes 100% of the scored server and client conformance scenarios for both the 2025-11-25 and 2026-07-28 requirement sets, measured with the standard MCP conformance suite. The post does not use the word sixth. The post links the tiering system at https://modelcontextprotocol.io/community/sdk-tiers, the gem at https://rubygems.org/gems/mcp, and the v1.2.0 tag at https://github.com/modelcontextprotocol/ruby-sdk/releases/tag/v1.2.0.",
2594
+ "tags": [
2595
+ "mcp",
2596
+ "sdk"
2597
+ ],
2598
+ "verified_at": "2026-11-04",
2599
+ "featured": false,
2600
+ "last_checked": "2026-11-04",
2601
+ "http_status": 200,
2602
+ "archive_url": null
2603
+ },
2604
  {
2605
  "id": "mcp-sep-3392-extension-lifecycle",
2606
  "title": "SEP-3392: Extension Lifecycle",
data/protocol-facts.json CHANGED
@@ -1,6 +1,6 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-03T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
@@ -66,12 +66,12 @@
66
  "url": "https://github.com/lightninglabs/lnget"
67
  },
68
  {
69
- "name": "lightninglabs/L402sdk. Published packages checked on 2026-10-27: PyPI l402sdk and l402sdk-langchain; npm @lightninglabs/l402 and @lightninglabs/l402-ai. The README install line still says pip install l402. That PyPI project is not this repository.",
70
- "url": "https://github.com/lightninglabs/L402sdk"
71
  }
72
  ],
73
- "source": "https://github.com/lightninglabs/L402sdk",
74
- "verified_at": "2026-10-27"
75
  },
76
  "pay_flow": {
77
  "value": [
@@ -705,6 +705,21 @@
705
  },
706
  "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392",
707
  "verified_at": "2026-10-31"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
708
  }
709
  },
710
  {
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-04T00:00:00Z",
4
  "disclaimer": {
5
  "text": "Not investment advice.",
6
  "url": "https://agentpaywire.com/disclaimer.json"
 
66
  "url": "https://github.com/lightninglabs/lnget"
67
  },
68
  {
69
+ "name": "lightninglabs/L402sdk 0.2.0. From this version, automatic payments require a backend that enforces a fee limit before submission. A zero fee limit allows only zero-fee routes.",
70
+ "url": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md"
71
  }
72
  ],
73
+ "source": "https://github.com/lightninglabs/L402sdk/blob/main/CHANGELOG.md",
74
+ "verified_at": "2026-11-04"
75
  },
76
  "pay_flow": {
77
  "value": [
 
705
  },
706
  "source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392",
707
  "verified_at": "2026-10-31"
708
+ },
709
+ "mcp_sdk_tiers": {
710
+ "value": {
711
+ "tier_1": [
712
+ "TypeScript",
713
+ "Python",
714
+ "C#",
715
+ "Go",
716
+ "Rust",
717
+ "Ruby"
718
+ ],
719
+ "note": "The 2026-10-30 post says the official Ruby SDK is now Tier 1 and joins the TypeScript, Python, C#, Go, and Rust SDKs. The post does not use the word sixth, and this page was not a separate tier registry."
720
+ },
721
+ "source": "https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/",
722
+ "verified_at": "2026-11-04"
723
  }
724
  },
725
  {
data/sources.csv CHANGED
@@ -2,6 +2,7 @@ id,title,publisher,authors,date_published,url,type,category,status,summary,tags,
2
  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,
3
  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,
4
  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,
 
5
  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,
6
  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,
7
  lightning-labs-wavelength-docs,Wavelength docs: llms.txt and Build with agents,Lightning Labs,,2026-10-23,https://wavelength.lightning.engineering/llms.txt,docs,bitcoin-lightning,product_docs,"Machine-readable docs index for the Wavelength SDK, a self-custodial Bitcoin, Lightning, and Ark wallet. Every docs page has a markdown twin at the same URL with .md appended, and https://wavelength.lightning.engineering/llms-full.txt holds the whole corpus. The Build with agents page is https://wavelength.lightning.engineering/agents.md. `wavecli mcp serve` runs a stdio MCP server that exposes each daemon RPC as a typed tool; create and unlock are omitted. `wavecli schema` dumps method schemas as JSON. Related: https://wavelength.lightning.engineering/cli/mcp.md, https://wavelength.lightning.engineering/cli/schema.md.",lightning; ark; wallet; mcp; llms-txt; agent-tooling,2026-10-25,true,2026-10-25,200,
@@ -37,7 +38,6 @@ l402-org,"L402: native payments for MCP, AI agents, APIs and data",l402.org,,,ht
37
  nostr-nip-90-data-vending-machine,NIP-90: Data Vending Machine,GitHub (nostr-protocol/nips),,,https://github.com/nostr-protocol/nips/blob/master/90.md,spec,bitcoin-lightning,spec_released,"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",nostr; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md
38
  l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
39
  voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
40
- lightninglabs-l402sdk,lightninglabs/L402sdk,GitHub (Lightning Labs),,,https://github.com/lightninglabs/L402sdk,repo,bitcoin-lightning,product_docs,"Lightning Labs repository for an L402 client SDK for AI agent frameworks. The README says the core is Rust, with TypeScript bindings for the Vercel AI SDK and Python bindings, including LangChain tools, and the TypeScript example constructs a WasmBudgetConfig. The README license is MIT or Apache-2.0. Checked on 2026-10-27: npm has @lightninglabs/l402 0.1.0 and @lightninglabs/l402-ai 0.1.0, and both name this repository. PyPI has l402sdk 0.1.0 and l402sdk-langchain 0.1.0, and both name this repository. The README install line still says pip install l402 and links https://pypi.org/project/l402/, whose homepage is https://github.com/Fewsats/l402-python. PyPI has no project named l402-langchain. crates.io has no crate named l402-core. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).",l402; lightning; sdk,2026-10-27,,2026-10-27,200,
41
  stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
42
  stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
43
  singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
@@ -108,6 +108,7 @@ celo-x402-facilitator,x402 Facilitator — Celo,Celo Core Co.,,,https://x402.cel
108
  stripe-docs-mcp,Model Context Protocol (MCP),Stripe Docs,,,https://docs.stripe.com/mcp,docs,payments,product_docs,"Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.",mcp; agent-wallets; tools,2026-10-23,,2026-10-23,200,
109
  visa-trusted-agent-protocol-reference,Trusted Agent Protocol sample implementation,Visa,,,https://github.com/visa/trusted-agent-protocol,repo,payments,product_docs,"Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.",card-networks; identity; security,2026-10-23,,2026-10-23,200,
110
  stripe-docs-mpp-sessions,Accept streaming payments,Stripe Docs,,,https://docs.stripe.com/payments/machine/mpp/sessions,docs,payments,product_docs,"Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.",m2m-payments; stablecoins,2026-10-23,,2026-10-23,200,
 
111
  mcp-sep-3392-extension-lifecycle,SEP-3392: Extension Lifecycle,GitHub (Model Context Protocol),Peter Alexander,2026-10-29,https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392,docs,agent-protocols,standard,"Process SEP. The merged document header status is Final. The pull request merged on 2026-10-29. An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification. The stage is the directory specification/experimental, specification/beta, or specification/stable. The document says the repository name does not show the stage, and that an earlier draft used experimental-ext-, beta-ext-, and ext- prefixes. Its transition table, under the heading Stage at Final, classifies ext-apps and ext-auth as Stable, ext-skills, ext-tasks, and ext-server-card as Beta, and experimental-ext-interceptors, experimental-ext-variants, experimental-ext-triggers-events, and experimental-ext-tool-annotations as Experimental. It says Extension Maintainers move the specification into that directory and a Core Maintainer approves the move.",mcp; standards,2026-10-31,,2026-10-31,200,
112
  mcp-sep-3398-release-cycle-updates,SEP-3398: Release Cycle Updates,GitHub (Model Context Protocol),Kurtis Van Gent,2026-10-27,https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398,docs,agent-protocols,product_docs,"Process SEP for the Model Context Protocol. The header status is Accepted. It was created 2026-09-17, accepted 2026-10-14, and the pull request merged on 2026-10-27. The author is Kurtis Van Gent. Specification releases occur every six months, generally on the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar. The SEP moves the release previously targeted for December 2026 to March 30, 2027, the last Tuesday of March, subject to confirmation in the transition calendar. Soft freeze is 2.5 months before release, the SDK beta is 1.5 months before release, and hard freeze is 1 month before release. The published release calendar defines the exact milestone dates. The SEP says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. The pull request's accepted label says an accepted SEP still requires final wording and a reference implementation.",mcp; standards,2026-10-28,,2026-10-28,200,
113
  erc-tba-agent-income-statements,ERC-TBA: Agent Income Statements,Fellowship of Ethereum Magicians,priors-agents,2026-10-22,https://ethereum-magicians.org/t/erc-tba-agent-income-statements/30047,spec,agent-protocols,individual_draft,"Draft profile of the ERC-8004 Reputation Registry, posted by priors-agents on 2026-10-22. It specifies chained, Merkle-rooted statements of what an agent's agentWallet received in one asset, under tag2 x402.statement, with windows cut at ERC-721 Transfer and MetadataSet(""agentWallet"") logs so the figures can be rebuilt from token logs. The repository has a verifier, a reference writer, and a checker. The author says the reference implementation is not audited and must not be deployed without an external audit. The thread was still active on 2026-10-25. Repository: https://github.com/priors-agents/erc-agent-income-statements.",identity; x402,2026-10-26,,2026-10-26,200,
 
2
  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,
3
  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,
4
  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,
5
+ 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,
6
  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,
7
  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,
8
  lightning-labs-wavelength-docs,Wavelength docs: llms.txt and Build with agents,Lightning Labs,,2026-10-23,https://wavelength.lightning.engineering/llms.txt,docs,bitcoin-lightning,product_docs,"Machine-readable docs index for the Wavelength SDK, a self-custodial Bitcoin, Lightning, and Ark wallet. Every docs page has a markdown twin at the same URL with .md appended, and https://wavelength.lightning.engineering/llms-full.txt holds the whole corpus. The Build with agents page is https://wavelength.lightning.engineering/agents.md. `wavecli mcp serve` runs a stdio MCP server that exposes each daemon RPC as a typed tool; create and unlock are omitted. `wavecli schema` dumps method schemas as JSON. Related: https://wavelength.lightning.engineering/cli/mcp.md, https://wavelength.lightning.engineering/cli/schema.md.",lightning; ark; wallet; mcp; llms-txt; agent-tooling,2026-10-25,true,2026-10-25,200,
 
38
  nostr-nip-90-data-vending-machine,NIP-90: Data Vending Machine,GitHub (nostr-protocol/nips),,,https://github.com/nostr-protocol/nips/blob/master/90.md,spec,bitcoin-lightning,spec_released,"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",nostr; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md
39
  l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
40
  voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
 
41
  stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
42
  stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
43
  singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
 
108
  stripe-docs-mcp,Model Context Protocol (MCP),Stripe Docs,,,https://docs.stripe.com/mcp,docs,payments,product_docs,"Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.",mcp; agent-wallets; tools,2026-10-23,,2026-10-23,200,
109
  visa-trusted-agent-protocol-reference,Trusted Agent Protocol sample implementation,Visa,,,https://github.com/visa/trusted-agent-protocol,repo,payments,product_docs,"Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.",card-networks; identity; security,2026-10-23,,2026-10-23,200,
110
  stripe-docs-mpp-sessions,Accept streaming payments,Stripe Docs,,,https://docs.stripe.com/payments/machine/mpp/sessions,docs,payments,product_docs,"Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.",m2m-payments; stablecoins,2026-10-23,,2026-10-23,200,
111
+ mcp-ruby-sdk-tier-1,The Official Ruby SDK for MCP Reaches Tier 1,Model Context Protocol Blog,Koichi Ito,2026-10-30,https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/,announcement,agent-protocols,news,"MCP Blog post by Koichi Ito, dated 2026-10-30. The official Ruby SDK is now a Tier 1 SDK, and the post says it joins the TypeScript, Python, C#, Go, and Rust SDKs. Starting with version 1.2.0 of the mcp gem, the post says the SDK fully supports the 2026-07-28 MCP specification. It says the SDK passes 100% of the scored server and client conformance scenarios for both the 2025-11-25 and 2026-07-28 requirement sets, measured with the standard MCP conformance suite. The post does not use the word sixth. The post links the tiering system at https://modelcontextprotocol.io/community/sdk-tiers, the gem at https://rubygems.org/gems/mcp, and the v1.2.0 tag at https://github.com/modelcontextprotocol/ruby-sdk/releases/tag/v1.2.0.",mcp; sdk,2026-11-04,,2026-11-04,200,
112
  mcp-sep-3392-extension-lifecycle,SEP-3392: Extension Lifecycle,GitHub (Model Context Protocol),Peter Alexander,2026-10-29,https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392,docs,agent-protocols,standard,"Process SEP. The merged document header status is Final. The pull request merged on 2026-10-29. An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification. The stage is the directory specification/experimental, specification/beta, or specification/stable. The document says the repository name does not show the stage, and that an earlier draft used experimental-ext-, beta-ext-, and ext- prefixes. Its transition table, under the heading Stage at Final, classifies ext-apps and ext-auth as Stable, ext-skills, ext-tasks, and ext-server-card as Beta, and experimental-ext-interceptors, experimental-ext-variants, experimental-ext-triggers-events, and experimental-ext-tool-annotations as Experimental. It says Extension Maintainers move the specification into that directory and a Core Maintainer approves the move.",mcp; standards,2026-10-31,,2026-10-31,200,
113
  mcp-sep-3398-release-cycle-updates,SEP-3398: Release Cycle Updates,GitHub (Model Context Protocol),Kurtis Van Gent,2026-10-27,https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398,docs,agent-protocols,product_docs,"Process SEP for the Model Context Protocol. The header status is Accepted. It was created 2026-09-17, accepted 2026-10-14, and the pull request merged on 2026-10-27. The author is Kurtis Van Gent. Specification releases occur every six months, generally on the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar. The SEP moves the release previously targeted for December 2026 to March 30, 2027, the last Tuesday of March, subject to confirmation in the transition calendar. Soft freeze is 2.5 months before release, the SDK beta is 1.5 months before release, and hard freeze is 1 month before release. The published release calendar defines the exact milestone dates. The SEP says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. The pull request's accepted label says an accepted SEP still requires final wording and a reference implementation.",mcp; standards,2026-10-28,,2026-10-28,200,
114
  erc-tba-agent-income-statements,ERC-TBA: Agent Income Statements,Fellowship of Ethereum Magicians,priors-agents,2026-10-22,https://ethereum-magicians.org/t/erc-tba-agent-income-statements/30047,spec,agent-protocols,individual_draft,"Draft profile of the ERC-8004 Reputation Registry, posted by priors-agents on 2026-10-22. It specifies chained, Merkle-rooted statements of what an agent's agentWallet received in one asset, under tag2 x402.statement, with windows cut at ERC-721 Transfer and MetadataSet(""agentWallet"") logs so the figures can be rebuilt from token logs. The repository has a verifier, a reference writer, and a checker. The author says the reference implementation is not audited and must not be deployed without an external audit. The thread was still active on 2026-10-25. Repository: https://github.com/priors-agents/erc-agent-income-statements.",identity; x402,2026-10-26,,2026-10-26,200,
data/sources.jsonl CHANGED
@@ -1,6 +1,7 @@
1
  {"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}
2
  {"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}
3
  {"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}
 
4
  {"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}
5
  {"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}
6
  {"id":"lightning-labs-wavelength-docs","title":"Wavelength docs: llms.txt and Build with agents","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-23","url":"https://wavelength.lightning.engineering/llms.txt","type":"docs","category":"bitcoin-lightning","status":"product_docs","summary":"Machine-readable docs index for the Wavelength SDK, a self-custodial Bitcoin, Lightning, and Ark wallet. Every docs page has a markdown twin at the same URL with .md appended, and https://wavelength.lightning.engineering/llms-full.txt holds the whole corpus. The Build with agents page is https://wavelength.lightning.engineering/agents.md. `wavecli mcp serve` runs a stdio MCP server that exposes each daemon RPC as a typed tool; create and unlock are omitted. `wavecli schema` dumps method schemas as JSON. Related: https://wavelength.lightning.engineering/cli/mcp.md, https://wavelength.lightning.engineering/cli/schema.md.","tags":["lightning","ark","wallet","mcp","llms-txt","agent-tooling"],"verified_at":"2026-10-25","featured":true,"last_checked":"2026-10-25","http_status":200,"archive_url":null}
@@ -36,7 +37,6 @@
36
  {"id":"nostr-nip-90-data-vending-machine","title":"NIP-90: Data Vending Machine","publisher":"GitHub (nostr-protocol/nips)","authors":[],"date_published":null,"url":"https://github.com/nostr-protocol/nips/blob/master/90.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.","tags":["nostr","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md"}
37
  {"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
38
  {"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
39
- {"id":"lightninglabs-l402sdk","title":"lightninglabs/L402sdk","publisher":"GitHub (Lightning Labs)","authors":[],"date_published":null,"url":"https://github.com/lightninglabs/L402sdk","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Lightning Labs repository for an L402 client SDK for AI agent frameworks. The README says the core is Rust, with TypeScript bindings for the Vercel AI SDK and Python bindings, including LangChain tools, and the TypeScript example constructs a WasmBudgetConfig. The README license is MIT or Apache-2.0. Checked on 2026-10-27: npm has @lightninglabs/l402 0.1.0 and @lightninglabs/l402-ai 0.1.0, and both name this repository. PyPI has l402sdk 0.1.0 and l402sdk-langchain 0.1.0, and both name this repository. The README install line still says pip install l402 and links https://pypi.org/project/l402/, whose homepage is https://github.com/Fewsats/l402-python. PyPI has no project named l402-langchain. crates.io has no crate named l402-core. Related library entry: lightninglabs-l402-github (https://github.com/lightninglabs/L402).","tags":["l402","lightning","sdk"],"verified_at":"2026-10-27","featured":false,"last_checked":"2026-10-27","http_status":200,"archive_url":null}
40
  {"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
41
  {"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
42
  {"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
@@ -107,6 +107,7 @@
107
  {"id":"stripe-docs-mcp","title":"Model Context Protocol (MCP)","publisher":"Stripe Docs","authors":[],"date_published":null,"url":"https://docs.stripe.com/mcp","type":"docs","category":"payments","status":"product_docs","summary":"Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.","tags":["mcp","agent-wallets","tools"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
108
  {"id":"visa-trusted-agent-protocol-reference","title":"Trusted Agent Protocol sample implementation","publisher":"Visa","authors":[],"date_published":null,"url":"https://github.com/visa/trusted-agent-protocol","type":"repo","category":"payments","status":"product_docs","summary":"Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.","tags":["card-networks","identity","security"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
109
  {"id":"stripe-docs-mpp-sessions","title":"Accept streaming payments","publisher":"Stripe Docs","authors":[],"date_published":null,"url":"https://docs.stripe.com/payments/machine/mpp/sessions","type":"docs","category":"payments","status":"product_docs","summary":"Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.","tags":["m2m-payments","stablecoins"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
 
110
  {"id":"mcp-sep-3392-extension-lifecycle","title":"SEP-3392: Extension Lifecycle","publisher":"GitHub (Model Context Protocol)","authors":["Peter Alexander"],"date_published":"2026-10-29","url":"https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392","type":"docs","category":"agent-protocols","status":"standard","summary":"Process SEP. The merged document header status is Final. The pull request merged on 2026-10-29. An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification. The stage is the directory specification/experimental, specification/beta, or specification/stable. The document says the repository name does not show the stage, and that an earlier draft used experimental-ext-, beta-ext-, and ext- prefixes. Its transition table, under the heading Stage at Final, classifies ext-apps and ext-auth as Stable, ext-skills, ext-tasks, and ext-server-card as Beta, and experimental-ext-interceptors, experimental-ext-variants, experimental-ext-triggers-events, and experimental-ext-tool-annotations as Experimental. It says Extension Maintainers move the specification into that directory and a Core Maintainer approves the move.","tags":["mcp","standards"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
111
  {"id":"mcp-sep-3398-release-cycle-updates","title":"SEP-3398: Release Cycle Updates","publisher":"GitHub (Model Context Protocol)","authors":["Kurtis Van Gent"],"date_published":"2026-10-27","url":"https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398","type":"docs","category":"agent-protocols","status":"product_docs","summary":"Process SEP for the Model Context Protocol. The header status is Accepted. It was created 2026-09-17, accepted 2026-10-14, and the pull request merged on 2026-10-27. The author is Kurtis Van Gent. Specification releases occur every six months, generally on the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar. The SEP moves the release previously targeted for December 2026 to March 30, 2027, the last Tuesday of March, subject to confirmation in the transition calendar. Soft freeze is 2.5 months before release, the SDK beta is 1.5 months before release, and hard freeze is 1 month before release. The published release calendar defines the exact milestone dates. The SEP says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. The pull request's accepted label says an accepted SEP still requires final wording and a reference implementation.","tags":["mcp","standards"],"verified_at":"2026-10-28","featured":false,"last_checked":"2026-10-28","http_status":200,"archive_url":null}
112
  {"id":"erc-tba-agent-income-statements","title":"ERC-TBA: Agent Income Statements","publisher":"Fellowship of Ethereum Magicians","authors":["priors-agents"],"date_published":"2026-10-22","url":"https://ethereum-magicians.org/t/erc-tba-agent-income-statements/30047","type":"spec","category":"agent-protocols","status":"individual_draft","summary":"Draft profile of the ERC-8004 Reputation Registry, posted by priors-agents on 2026-10-22. It specifies chained, Merkle-rooted statements of what an agent's agentWallet received in one asset, under tag2 x402.statement, with windows cut at ERC-721 Transfer and MetadataSet(\"agentWallet\") logs so the figures can be rebuilt from token logs. The repository has a verifier, a reference writer, and a checker. The author says the reference implementation is not audited and must not be deployed without an external audit. The thread was still active on 2026-10-25. Repository: https://github.com/priors-agents/erc-agent-income-statements.","tags":["identity","x402"],"verified_at":"2026-10-26","featured":false,"last_checked":"2026-10-26","http_status":200,"archive_url":null}
 
1
  {"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}
2
  {"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}
3
  {"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}
4
+ {"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}
5
  {"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}
6
  {"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}
7
  {"id":"lightning-labs-wavelength-docs","title":"Wavelength docs: llms.txt and Build with agents","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-23","url":"https://wavelength.lightning.engineering/llms.txt","type":"docs","category":"bitcoin-lightning","status":"product_docs","summary":"Machine-readable docs index for the Wavelength SDK, a self-custodial Bitcoin, Lightning, and Ark wallet. Every docs page has a markdown twin at the same URL with .md appended, and https://wavelength.lightning.engineering/llms-full.txt holds the whole corpus. The Build with agents page is https://wavelength.lightning.engineering/agents.md. `wavecli mcp serve` runs a stdio MCP server that exposes each daemon RPC as a typed tool; create and unlock are omitted. `wavecli schema` dumps method schemas as JSON. Related: https://wavelength.lightning.engineering/cli/mcp.md, https://wavelength.lightning.engineering/cli/schema.md.","tags":["lightning","ark","wallet","mcp","llms-txt","agent-tooling"],"verified_at":"2026-10-25","featured":true,"last_checked":"2026-10-25","http_status":200,"archive_url":null}
 
37
  {"id":"nostr-nip-90-data-vending-machine","title":"NIP-90: Data Vending Machine","publisher":"GitHub (nostr-protocol/nips)","authors":[],"date_published":null,"url":"https://github.com/nostr-protocol/nips/blob/master/90.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.","tags":["nostr","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md"}
38
  {"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
39
  {"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
 
40
  {"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
41
  {"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
42
  {"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
 
107
  {"id":"stripe-docs-mcp","title":"Model Context Protocol (MCP)","publisher":"Stripe Docs","authors":[],"date_published":null,"url":"https://docs.stripe.com/mcp","type":"docs","category":"payments","status":"product_docs","summary":"Stripe documentation for its Model Context Protocol server, labeled public preview. The server URL is https://mcp.stripe.com. Clients authenticate with OAuth or with an agent API key passed as a bearer token in the Authorization header. A GET of https://mcp.stripe.com with no API key returned HTTP 401 on 2026-10-23. Treasury tools on the server are labeled public preview. Related library entry: stripe-treasury-for-agents.","tags":["mcp","agent-wallets","tools"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
108
  {"id":"visa-trusted-agent-protocol-reference","title":"Trusted Agent Protocol sample implementation","publisher":"Visa","authors":[],"date_published":null,"url":"https://github.com/visa/trusted-agent-protocol","type":"repo","category":"payments","status":"product_docs","summary":"Visa's GitHub repository for a Trusted Agent Protocol sample implementation. The repository includes the modules agent-registry, tap-agent, and merchant-backend. The README says an agent signature includes a timestamp, a session identifier, a key identifier, and an algorithm identifier, and that the signature is bound to the merchant domain and the operation. License: not open source. LICENSE.md requires the Visa Developer Center Terms of Use (https://developer.visa.com/terms), including the Visa Trusted Agent Protocol Product Terms. Related library entries: visa-developer-trusted-agent-protocol and visa-bill-billtrust-trusted-agent-b2b-pilot.","tags":["card-networks","identity","security"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
109
  {"id":"stripe-docs-mpp-sessions","title":"Accept streaming payments","publisher":"Stripe Docs","authors":[],"date_published":null,"url":"https://docs.stripe.com/payments/machine/mpp/sessions","type":"docs","category":"payments","status":"product_docs","summary":"Stripe documentation for MPP sessions. An agent deposits USDC into a session on Tempo. The server charges for each unit of work in increments as small as 0.000001 USDC and settles funds to the Stripe balance in increments of 0.01 USD or more. Any sub-cent remainder, such as when a client closes a session, is forfeited. Related library entries: stripe-docs-mpp, stripe-introducing-machine-payments-protocol, and stripe-docs-mcp.","tags":["m2m-payments","stablecoins"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
110
+ {"id":"mcp-ruby-sdk-tier-1","title":"The Official Ruby SDK for MCP Reaches Tier 1","publisher":"Model Context Protocol Blog","authors":["Koichi Ito"],"date_published":"2026-10-30","url":"https://blog.modelcontextprotocol.io/posts/ruby-sdk-tier-1/","type":"announcement","category":"agent-protocols","status":"news","summary":"MCP Blog post by Koichi Ito, dated 2026-10-30. The official Ruby SDK is now a Tier 1 SDK, and the post says it joins the TypeScript, Python, C#, Go, and Rust SDKs. Starting with version 1.2.0 of the mcp gem, the post says the SDK fully supports the 2026-07-28 MCP specification. It says the SDK passes 100% of the scored server and client conformance scenarios for both the 2025-11-25 and 2026-07-28 requirement sets, measured with the standard MCP conformance suite. The post does not use the word sixth. The post links the tiering system at https://modelcontextprotocol.io/community/sdk-tiers, the gem at https://rubygems.org/gems/mcp, and the v1.2.0 tag at https://github.com/modelcontextprotocol/ruby-sdk/releases/tag/v1.2.0.","tags":["mcp","sdk"],"verified_at":"2026-11-04","featured":false,"last_checked":"2026-11-04","http_status":200,"archive_url":null}
111
  {"id":"mcp-sep-3392-extension-lifecycle","title":"SEP-3392: Extension Lifecycle","publisher":"GitHub (Model Context Protocol)","authors":["Peter Alexander"],"date_published":"2026-10-29","url":"https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392","type":"docs","category":"agent-protocols","status":"standard","summary":"Process SEP. The merged document header status is Final. The pull request merged on 2026-10-29. An extension starts as Experimental, may advance to Beta, and then either becomes Stable as an extension or is promoted into the core specification. The stage is the directory specification/experimental, specification/beta, or specification/stable. The document says the repository name does not show the stage, and that an earlier draft used experimental-ext-, beta-ext-, and ext- prefixes. Its transition table, under the heading Stage at Final, classifies ext-apps and ext-auth as Stable, ext-skills, ext-tasks, and ext-server-card as Beta, and experimental-ext-interceptors, experimental-ext-variants, experimental-ext-triggers-events, and experimental-ext-tool-annotations as Experimental. It says Extension Maintainers move the specification into that directory and a Core Maintainer approves the move.","tags":["mcp","standards"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
112
  {"id":"mcp-sep-3398-release-cycle-updates","title":"SEP-3398: Release Cycle Updates","publisher":"GitHub (Model Context Protocol)","authors":["Kurtis Van Gent"],"date_published":"2026-10-27","url":"https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3398","type":"docs","category":"agent-protocols","status":"product_docs","summary":"Process SEP for the Model Context Protocol. The header status is Accepted. It was created 2026-09-17, accepted 2026-10-14, and the pull request merged on 2026-10-27. The author is Kurtis Van Gent. Specification releases occur every six months, generally on the last Tuesday of March and September. Release managers confirm the exact date in each cycle's published calendar. The SEP moves the release previously targeted for December 2026 to March 30, 2027, the last Tuesday of March, subject to confirmation in the transition calendar. Soft freeze is 2.5 months before release, the SDK beta is 1.5 months before release, and hard freeze is 1 month before release. The published release calendar defines the exact milestone dates. The SEP says it introduces no protocol messages, schema changes, version-negotiation changes, or new requirements for deployed clients and servers. The pull request's accepted label says an accepted SEP still requires final wording and a reference implementation.","tags":["mcp","standards"],"verified_at":"2026-10-28","featured":false,"last_checked":"2026-10-28","http_status":200,"archive_url":null}
113
  {"id":"erc-tba-agent-income-statements","title":"ERC-TBA: Agent Income Statements","publisher":"Fellowship of Ethereum Magicians","authors":["priors-agents"],"date_published":"2026-10-22","url":"https://ethereum-magicians.org/t/erc-tba-agent-income-statements/30047","type":"spec","category":"agent-protocols","status":"individual_draft","summary":"Draft profile of the ERC-8004 Reputation Registry, posted by priors-agents on 2026-10-22. It specifies chained, Merkle-rooted statements of what an agent's agentWallet received in one asset, under tag2 x402.statement, with windows cut at ERC-721 Transfer and MetadataSet(\"agentWallet\") logs so the figures can be rebuilt from token logs. The repository has a verifier, a reference writer, and a checker. The author says the reference implementation is not audited and must not be deployed without an external audit. The thread was still active on 2026-10-25. Repository: https://github.com/priors-agents/erc-agent-income-statements.","tags":["identity","x402"],"verified_at":"2026-10-26","featured":false,"last_checked":"2026-10-26","http_status":200,"archive_url":null}
data/tags.json CHANGED
@@ -1,6 +1,6 @@
1
  {
2
  "schema_version": "1",
3
- "generated_at": "2026-11-03T00:00:00Z",
4
  "count": 70,
5
  "tags": [
6
  {
@@ -190,7 +190,7 @@
190
  },
191
  {
192
  "tag": "mcp",
193
- "count": 29,
194
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
195
  },
196
  {
@@ -250,7 +250,7 @@
250
  },
251
  {
252
  "tag": "release",
253
- "count": 3,
254
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
255
  },
256
  {
@@ -270,7 +270,7 @@
270
  },
271
  {
272
  "tag": "sdk",
273
- "count": 2,
274
  "json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
275
  },
276
  {
 
1
  {
2
  "schema_version": "1",
3
+ "generated_at": "2026-11-04T00:00:00Z",
4
  "count": 70,
5
  "tags": [
6
  {
 
190
  },
191
  {
192
  "tag": "mcp",
193
+ "count": 30,
194
  "json_url": "https://agentpaywire.com/api/library/tag/mcp.json"
195
  },
196
  {
 
250
  },
251
  {
252
  "tag": "release",
253
+ "count": 4,
254
  "json_url": "https://agentpaywire.com/api/library/tag/release.json"
255
  },
256
  {
 
270
  },
271
  {
272
  "tag": "sdk",
273
+ "count": 3,
274
  "json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
275
  },
276
  {