Sync to 169 entries (site 993fa41)
Browse files- README.md +12 -12
- data/library.json +154 -61
- data/protocol-facts.json +87 -1
- data/sources.csv +7 -3
- data/sources.jsonl +7 -3
- data/tags.json +8 -8
README.md
CHANGED
|
@@ -26,7 +26,7 @@ configs:
|
|
| 26 |
|
| 27 |
# Agent Paywire Knowledge Library
|
| 28 |
|
| 29 |
-
A curated library of **
|
| 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-
|
| 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)
|
|
@@ -44,17 +44,17 @@ Linked pages, papers, repositories and specifications are **not** included and b
|
|
| 44 |
| category | entries |
|
| 45 |
| --- | --- |
|
| 46 |
| bitcoin-lightning (featured) | 39 |
|
| 47 |
-
| payments |
|
| 48 |
-
| agent-protocols |
|
| 49 |
| robotics-autonomy | 4 |
|
| 50 |
| iot | 4 |
|
| 51 |
| datasets-benchmarks | 8 |
|
| 52 |
-
| safety-security |
|
| 53 |
| regulation | 3 |
|
| 54 |
|
| 55 |
## Fields (`data/sources.jsonl`)
|
| 56 |
|
| 57 |
-
One JSON object per line,
|
| 58 |
|
| 59 |
| field | type | description |
|
| 60 |
| --- | --- | --- |
|
|
@@ -62,7 +62,7 @@ One JSON object per line, 165 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 (
|
| 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, 165 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 (
|
| 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,12 +79,12 @@ One JSON object per line, 165 rows, single `train` split. Dates are `YYYY-MM-DD`
|
|
| 79 |
|
| 80 |
| file | contents |
|
| 81 |
| --- | --- |
|
| 82 |
-
| `data/sources.jsonl` | Main table (default config).
|
| 83 |
-
| `data/sources.csv` | Same
|
| 84 |
-
| `data/library.json` | Full library document with category list (8 categories) and
|
| 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
|
| 88 |
| `data/bots.json` | 5 verified agents/bots (listed, not endorsed). From https://agentpaywire.com/bots.json. |
|
| 89 |
| `data/datasets-index.json`, `data/datasets-index.jsonl` | Catalog of 6 training/eval dataset cards (metadata only; each listed third-party dataset keeps its own license). From https://agentpaywire.com/datasets/. |
|
| 90 |
| `data/about.json` | Publisher statement, including the license note. From https://agentpaywire.com/about.json. |
|
|
|
|
| 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 |
|
| 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)
|
|
|
|
| 44 |
| category | entries |
|
| 45 |
| --- | --- |
|
| 46 |
| bitcoin-lightning (featured) | 39 |
|
| 47 |
+
| payments | 70 |
|
| 48 |
+
| agent-protocols | 32 |
|
| 49 |
| robotics-autonomy | 4 |
|
| 50 |
| iot | 4 |
|
| 51 |
| datasets-benchmarks | 8 |
|
| 52 |
+
| safety-security | 9 |
|
| 53 |
| regulation | 3 |
|
| 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 |
| `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 |
| `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 |
|
| 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. |
|
| 88 |
| `data/bots.json` | 5 verified agents/bots (listed, not endorsed). From https://agentpaywire.com/bots.json. |
|
| 89 |
| `data/datasets-index.json`, `data/datasets-index.jsonl` | Catalog of 6 training/eval dataset cards (metadata only; each listed third-party dataset keeps its own license). From https://agentpaywire.com/datasets/. |
|
| 90 |
| `data/about.json` | Publisher statement, including the license note. From https://agentpaywire.com/about.json. |
|
data/library.json
CHANGED
|
@@ -1,13 +1,13 @@
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
-
"generated_at": "2026-
|
| 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":
|
| 11 |
"categories": [
|
| 12 |
{
|
| 13 |
"id": "bitcoin-lightning",
|
|
@@ -22,7 +22,7 @@
|
|
| 22 |
"id": "payments",
|
| 23 |
"label": "Payments",
|
| 24 |
"featured": false,
|
| 25 |
-
"count":
|
| 26 |
"json_url": "https://agentpaywire.com/api/library/payments.json",
|
| 27 |
"markdown_url": "https://agentpaywire.com/library/payments.md",
|
| 28 |
"html_url": "https://agentpaywire.com/library/payments/"
|
|
@@ -31,7 +31,7 @@
|
|
| 31 |
"id": "agent-protocols",
|
| 32 |
"label": "Agent protocols",
|
| 33 |
"featured": false,
|
| 34 |
-
"count":
|
| 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/"
|
|
@@ -67,7 +67,7 @@
|
|
| 67 |
"id": "safety-security",
|
| 68 |
"label": "Safety and security",
|
| 69 |
"featured": false,
|
| 70 |
-
"count":
|
| 71 |
"json_url": "https://agentpaywire.com/api/library/safety-security.json",
|
| 72 |
"markdown_url": "https://agentpaywire.com/library/safety-security.md",
|
| 73 |
"html_url": "https://agentpaywire.com/library/safety-security/"
|
|
@@ -83,6 +83,52 @@
|
|
| 83 |
}
|
| 84 |
],
|
| 85 |
"entries": [
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 86 |
{
|
| 87 |
"id": "bitcoin-optech-newsletter-429",
|
| 88 |
"title": "Bitcoin Optech Newsletter #429",
|
|
@@ -132,24 +178,26 @@
|
|
| 132 |
"archive_url": null
|
| 133 |
},
|
| 134 |
{
|
| 135 |
-
"id": "
|
| 136 |
-
"title": "
|
| 137 |
-
"publisher": "
|
| 138 |
"authors": [],
|
| 139 |
"date_published": "2026-10-27",
|
| 140 |
-
"url": "https://github.com/
|
| 141 |
"type": "repo",
|
| 142 |
"category": "bitcoin-lightning",
|
| 143 |
"status": "product_docs",
|
| 144 |
-
"summary": "
|
| 145 |
"tags": [
|
| 146 |
-
"
|
|
|
|
| 147 |
"lightning",
|
| 148 |
-
"
|
|
|
|
| 149 |
],
|
| 150 |
-
"verified_at": "2026-
|
| 151 |
"featured": true,
|
| 152 |
-
"last_checked": "2026-
|
| 153 |
"http_status": 200,
|
| 154 |
"archive_url": null
|
| 155 |
},
|
|
@@ -178,29 +226,6 @@
|
|
| 178 |
"http_status": 200,
|
| 179 |
"archive_url": null
|
| 180 |
},
|
| 181 |
-
{
|
| 182 |
-
"id": "wavelength-v0-2-0-release",
|
| 183 |
-
"title": "Wavelength v0.2.0 (Mainnet is open)",
|
| 184 |
-
"publisher": "Lightning Labs (GitHub)",
|
| 185 |
-
"authors": [],
|
| 186 |
-
"date_published": "2026-10-23",
|
| 187 |
-
"url": "https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0",
|
| 188 |
-
"type": "repo",
|
| 189 |
-
"category": "bitcoin-lightning",
|
| 190 |
-
"status": "spec_released",
|
| 191 |
-
"summary": "First public mainnet release, published 2026-10-23. It adds scheduled batches and free-only automatic refresh, which waits for the operator's free-refresh window and rejects any quote that charges a fee. On mainnet the daemon rejects plaintext operator and swap connections and externally exposed HTTP gateways by default. Credit spending and top-ups have separate limits, and both default to zero.",
|
| 192 |
-
"tags": [
|
| 193 |
-
"lightning",
|
| 194 |
-
"ark",
|
| 195 |
-
"wallet",
|
| 196 |
-
"release"
|
| 197 |
-
],
|
| 198 |
-
"verified_at": "2026-10-25",
|
| 199 |
-
"featured": true,
|
| 200 |
-
"last_checked": "2026-10-25",
|
| 201 |
-
"http_status": 200,
|
| 202 |
-
"archive_url": null
|
| 203 |
-
},
|
| 204 |
{
|
| 205 |
"id": "lightning-labs-wavelength-mainnet",
|
| 206 |
"title": "Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet",
|
|
@@ -255,30 +280,6 @@
|
|
| 255 |
"http_status": 200,
|
| 256 |
"archive_url": null
|
| 257 |
},
|
| 258 |
-
{
|
| 259 |
-
"id": "getalby-js-sdk-v8-1-0-release",
|
| 260 |
-
"title": "Release v8.1.0 · getAlby/js-sdk",
|
| 261 |
-
"publisher": "GitHub (Alby)",
|
| 262 |
-
"authors": [],
|
| 263 |
-
"date_published": "2026-10-20",
|
| 264 |
-
"url": "https://github.com/getAlby/js-sdk/releases/tag/v8.1.0",
|
| 265 |
-
"type": "repo",
|
| 266 |
-
"category": "bitcoin-lightning",
|
| 267 |
-
"status": "product_docs",
|
| 268 |
-
"summary": "Release of Alby's JavaScript SDK for the Nostr Wallet Connect API. Per the changelog, it adds a recordEvent handler to NWCWalletService for request deduplication, optional since/until filters on subscriptions and a publishNotification method, and it fixes subscription reconnect loops and validates payment and invoice amounts client-side.",
|
| 269 |
-
"tags": [
|
| 270 |
-
"nwc",
|
| 271 |
-
"nostr",
|
| 272 |
-
"lightning",
|
| 273 |
-
"agent-wallets",
|
| 274 |
-
"tools"
|
| 275 |
-
],
|
| 276 |
-
"verified_at": "2026-10-21",
|
| 277 |
-
"featured": true,
|
| 278 |
-
"last_checked": "2026-10-21",
|
| 279 |
-
"http_status": 200,
|
| 280 |
-
"archive_url": null
|
| 281 |
-
},
|
| 282 |
{
|
| 283 |
"id": "lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes",
|
| 284 |
"title": "bolt11: reject duplicate payment hashes in invoices",
|
|
@@ -1879,6 +1880,27 @@
|
|
| 1879 |
"http_status": 200,
|
| 1880 |
"archive_url": "http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"
|
| 1881 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1882 |
{
|
| 1883 |
"id": "coinbase-business-accept-x402-payments",
|
| 1884 |
"title": "Accept Agentic Payments with x402",
|
|
@@ -2844,6 +2866,49 @@
|
|
| 2844 |
"http_status": 200,
|
| 2845 |
"archive_url": "http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"
|
| 2846 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 2847 |
{
|
| 2848 |
"id": "a2a-protocol-specification",
|
| 2849 |
"title": "Agent2Agent (A2A) Protocol Specification",
|
|
@@ -3583,6 +3648,34 @@
|
|
| 3583 |
"http_status": 200,
|
| 3584 |
"archive_url": "http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"
|
| 3585 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 3586 |
{
|
| 3587 |
"id": "v12-x402-25-vulnerabilities",
|
| 3588 |
"title": "25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings",
|
|
|
|
| 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",
|
|
|
|
| 22 |
"id": "payments",
|
| 23 |
"label": "Payments",
|
| 24 |
"featured": false,
|
| 25 |
+
"count": 70,
|
| 26 |
"json_url": "https://agentpaywire.com/api/library/payments.json",
|
| 27 |
"markdown_url": "https://agentpaywire.com/library/payments.md",
|
| 28 |
"html_url": "https://agentpaywire.com/library/payments/"
|
|
|
|
| 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/"
|
|
|
|
| 67 |
"id": "safety-security",
|
| 68 |
"label": "Safety and security",
|
| 69 |
"featured": false,
|
| 70 |
+
"count": 9,
|
| 71 |
"json_url": "https://agentpaywire.com/api/library/safety-security.json",
|
| 72 |
"markdown_url": "https://agentpaywire.com/library/safety-security.md",
|
| 73 |
"html_url": "https://agentpaywire.com/library/safety-security/"
|
|
|
|
| 83 |
}
|
| 84 |
],
|
| 85 |
"entries": [
|
| 86 |
+
{
|
| 87 |
+
"id": "wavelength-v0-2-1-release",
|
| 88 |
+
"title": "Wavelength v0.2.1",
|
| 89 |
+
"publisher": "Lightning Labs (GitHub)",
|
| 90 |
+
"authors": [],
|
| 91 |
+
"date_published": "2026-10-31",
|
| 92 |
+
"url": "https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1",
|
| 93 |
+
"type": "repo",
|
| 94 |
+
"category": "bitcoin-lightning",
|
| 95 |
+
"status": "spec_released",
|
| 96 |
+
"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.",
|
| 97 |
+
"tags": [
|
| 98 |
+
"lightning",
|
| 99 |
+
"ark",
|
| 100 |
+
"wallet",
|
| 101 |
+
"release"
|
| 102 |
+
],
|
| 103 |
+
"verified_at": "2026-11-03",
|
| 104 |
+
"featured": true,
|
| 105 |
+
"last_checked": "2026-11-03",
|
| 106 |
+
"http_status": 200,
|
| 107 |
+
"archive_url": null
|
| 108 |
+
},
|
| 109 |
+
{
|
| 110 |
+
"id": "lnd-v0-21-6-beta",
|
| 111 |
+
"title": "lnd v0.21.6-beta and v0.20.7-beta",
|
| 112 |
+
"publisher": "Lightning Labs (GitHub)",
|
| 113 |
+
"authors": [],
|
| 114 |
+
"date_published": "2026-10-30",
|
| 115 |
+
"url": "https://github.com/lightningnetwork/lnd/releases/tag/v0.21.6-beta",
|
| 116 |
+
"type": "repo",
|
| 117 |
+
"category": "bitcoin-lightning",
|
| 118 |
+
"status": "product_docs",
|
| 119 |
+
"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.",
|
| 120 |
+
"tags": [
|
| 121 |
+
"lnd",
|
| 122 |
+
"lightning",
|
| 123 |
+
"release",
|
| 124 |
+
"security"
|
| 125 |
+
],
|
| 126 |
+
"verified_at": "2026-11-03",
|
| 127 |
+
"featured": true,
|
| 128 |
+
"last_checked": "2026-11-03",
|
| 129 |
+
"http_status": 200,
|
| 130 |
+
"archive_url": null
|
| 131 |
+
},
|
| 132 |
{
|
| 133 |
"id": "bitcoin-optech-newsletter-429",
|
| 134 |
"title": "Bitcoin Optech Newsletter #429",
|
|
|
|
| 178 |
"archive_url": null
|
| 179 |
},
|
| 180 |
{
|
| 181 |
+
"id": "getalby-js-sdk-v9-0-0-release",
|
| 182 |
+
"title": "Release v9.0.0 · getAlby/js-sdk",
|
| 183 |
+
"publisher": "GitHub (Alby)",
|
| 184 |
"authors": [],
|
| 185 |
"date_published": "2026-10-27",
|
| 186 |
+
"url": "https://github.com/getAlby/js-sdk/releases/tag/v9.0.0",
|
| 187 |
"type": "repo",
|
| 188 |
"category": "bitcoin-lightning",
|
| 189 |
"status": "product_docs",
|
| 190 |
+
"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.",
|
| 191 |
"tags": [
|
| 192 |
+
"nwc",
|
| 193 |
+
"nostr",
|
| 194 |
"lightning",
|
| 195 |
+
"agent-wallets",
|
| 196 |
+
"tools"
|
| 197 |
],
|
| 198 |
+
"verified_at": "2026-11-03",
|
| 199 |
"featured": true,
|
| 200 |
+
"last_checked": "2026-11-03",
|
| 201 |
"http_status": 200,
|
| 202 |
"archive_url": null
|
| 203 |
},
|
|
|
|
| 226 |
"http_status": 200,
|
| 227 |
"archive_url": null
|
| 228 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 229 |
{
|
| 230 |
"id": "lightning-labs-wavelength-mainnet",
|
| 231 |
"title": "Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet",
|
|
|
|
| 280 |
"http_status": 200,
|
| 281 |
"archive_url": null
|
| 282 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 283 |
{
|
| 284 |
"id": "lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes",
|
| 285 |
"title": "bolt11: reject duplicate payment hashes in invoices",
|
|
|
|
| 1880 |
"http_status": 200,
|
| 1881 |
"archive_url": "http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"
|
| 1882 |
},
|
| 1883 |
+
{
|
| 1884 |
+
"id": "link-balance-agent-wallet-purchases",
|
| 1885 |
+
"title": "Set up a balance for agent wallet purchases",
|
| 1886 |
+
"publisher": "Link (Stripe)",
|
| 1887 |
+
"authors": [],
|
| 1888 |
+
"date_published": null,
|
| 1889 |
+
"url": "https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases",
|
| 1890 |
+
"type": "docs",
|
| 1891 |
+
"category": "payments",
|
| 1892 |
+
"status": "product_docs",
|
| 1893 |
+
"summary": "Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.",
|
| 1894 |
+
"tags": [
|
| 1895 |
+
"agent-wallets",
|
| 1896 |
+
"stablecoins"
|
| 1897 |
+
],
|
| 1898 |
+
"verified_at": "2026-11-03",
|
| 1899 |
+
"featured": false,
|
| 1900 |
+
"last_checked": "2026-11-03",
|
| 1901 |
+
"http_status": 200,
|
| 1902 |
+
"archive_url": null
|
| 1903 |
+
},
|
| 1904 |
{
|
| 1905 |
"id": "coinbase-business-accept-x402-payments",
|
| 1906 |
"title": "Accept Agentic Payments with x402",
|
|
|
|
| 2866 |
"http_status": 200,
|
| 2867 |
"archive_url": "http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"
|
| 2868 |
},
|
| 2869 |
+
{
|
| 2870 |
+
"id": "x402-scheme-exact-lnbtc",
|
| 2871 |
+
"title": "x402 scheme: exact on Bitcoin Lightning (lnbtc)",
|
| 2872 |
+
"publisher": "x402 Foundation (GitHub)",
|
| 2873 |
+
"authors": [],
|
| 2874 |
+
"date_published": null,
|
| 2875 |
+
"url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md",
|
| 2876 |
+
"type": "spec",
|
| 2877 |
+
"category": "agent-protocols",
|
| 2878 |
+
"status": "spec_released",
|
| 2879 |
+
"summary": "Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.",
|
| 2880 |
+
"tags": [
|
| 2881 |
+
"x402",
|
| 2882 |
+
"lightning",
|
| 2883 |
+
"standards"
|
| 2884 |
+
],
|
| 2885 |
+
"verified_at": "2026-11-03",
|
| 2886 |
+
"featured": true,
|
| 2887 |
+
"last_checked": "2026-11-03",
|
| 2888 |
+
"http_status": 200,
|
| 2889 |
+
"archive_url": null
|
| 2890 |
+
},
|
| 2891 |
+
{
|
| 2892 |
+
"id": "x402-scheme-batch-settlement",
|
| 2893 |
+
"title": "x402 scheme: batch-settlement",
|
| 2894 |
+
"publisher": "x402 Foundation (GitHub)",
|
| 2895 |
+
"authors": [],
|
| 2896 |
+
"date_published": null,
|
| 2897 |
+
"url": "https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md",
|
| 2898 |
+
"type": "spec",
|
| 2899 |
+
"category": "agent-protocols",
|
| 2900 |
+
"status": "spec_released",
|
| 2901 |
+
"summary": "Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.",
|
| 2902 |
+
"tags": [
|
| 2903 |
+
"x402",
|
| 2904 |
+
"standards"
|
| 2905 |
+
],
|
| 2906 |
+
"verified_at": "2026-11-03",
|
| 2907 |
+
"featured": false,
|
| 2908 |
+
"last_checked": "2026-11-03",
|
| 2909 |
+
"http_status": 200,
|
| 2910 |
+
"archive_url": null
|
| 2911 |
+
},
|
| 2912 |
{
|
| 2913 |
"id": "a2a-protocol-specification",
|
| 2914 |
"title": "Agent2Agent (A2A) Protocol Specification",
|
|
|
|
| 3648 |
"http_status": 200,
|
| 3649 |
"archive_url": "http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"
|
| 3650 |
},
|
| 3651 |
+
{
|
| 3652 |
+
"id": "arxiv-2610-35835-i-hitl",
|
| 3653 |
+
"title": "I-HITL: Inalienable Human-in-the-Loop",
|
| 3654 |
+
"publisher": "arXiv",
|
| 3655 |
+
"authors": [
|
| 3656 |
+
"Samuel Breckenridge",
|
| 3657 |
+
"Dani Vilardell",
|
| 3658 |
+
"Wenhao Wang",
|
| 3659 |
+
"Fan Zhang",
|
| 3660 |
+
"Ari Juels"
|
| 3661 |
+
],
|
| 3662 |
+
"date_published": "2026-10-26",
|
| 3663 |
+
"url": "https://arxiv.org/abs/2610.35835",
|
| 3664 |
+
"type": "research-paper",
|
| 3665 |
+
"category": "safety-security",
|
| 3666 |
+
"status": "research",
|
| 3667 |
+
"summary": "arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.",
|
| 3668 |
+
"tags": [
|
| 3669 |
+
"security",
|
| 3670 |
+
"research",
|
| 3671 |
+
"agent-wallets"
|
| 3672 |
+
],
|
| 3673 |
+
"verified_at": "2026-11-03",
|
| 3674 |
+
"featured": false,
|
| 3675 |
+
"last_checked": "2026-11-03",
|
| 3676 |
+
"http_status": 200,
|
| 3677 |
+
"archive_url": null
|
| 3678 |
+
},
|
| 3679 |
{
|
| 3680 |
"id": "v12-x402-25-vulnerabilities",
|
| 3681 |
"title": "25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings",
|
data/protocol-facts.json
CHANGED
|
@@ -7,7 +7,7 @@
|
|
| 7 |
},
|
| 8 |
"description": "Checked protocol facts. Bitcoin and Lightning protocols are first. Each fact has a source URL and a verified_at date. Null means the cited pages do not state that field.",
|
| 9 |
"markdown_url": "https://agentpaywire.com/api/protocol-facts.md",
|
| 10 |
-
"count":
|
| 11 |
"protocols": [
|
| 12 |
{
|
| 13 |
"id": "l402",
|
|
@@ -356,6 +356,60 @@
|
|
| 356 |
"value": "V2 network ids use CAIP-2. The migration guide maps base to eip155:8453, ethereum to eip155:1, and solana to solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp. It does not publish a USDC contract address. V1 header names were X-PAYMENT and X-PAYMENT-RESPONSE. The scheme names exact, upto, and batch-settlement are on the HTTP 402 page.",
|
| 357 |
"source": "https://docs.x402.org/guides/migration-v1-to-v2",
|
| 358 |
"verified_at": "2026-10-20"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 359 |
}
|
| 360 |
},
|
| 361 |
{
|
|
@@ -652,6 +706,38 @@
|
|
| 652 |
"source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392",
|
| 653 |
"verified_at": "2026-10-31"
|
| 654 |
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 655 |
}
|
| 656 |
]
|
| 657 |
}
|
|
|
|
| 7 |
},
|
| 8 |
"description": "Checked protocol facts. Bitcoin and Lightning protocols are first. Each fact has a source URL and a verified_at date. Null means the cited pages do not state that field.",
|
| 9 |
"markdown_url": "https://agentpaywire.com/api/protocol-facts.md",
|
| 10 |
+
"count": 11,
|
| 11 |
"protocols": [
|
| 12 |
{
|
| 13 |
"id": "l402",
|
|
|
|
| 356 |
"value": "V2 network ids use CAIP-2. The migration guide maps base to eip155:8453, ethereum to eip155:1, and solana to solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp. It does not publish a USDC contract address. V1 header names were X-PAYMENT and X-PAYMENT-RESPONSE. The scheme names exact, upto, and batch-settlement are on the HTTP 402 page.",
|
| 357 |
"source": "https://docs.x402.org/guides/migration-v1-to-v2",
|
| 358 |
"verified_at": "2026-10-20"
|
| 359 |
+
},
|
| 360 |
+
"schemes": {
|
| 361 |
+
"value": [
|
| 362 |
+
{
|
| 363 |
+
"name": "exact",
|
| 364 |
+
"bindings": [
|
| 365 |
+
"algo",
|
| 366 |
+
"aptos",
|
| 367 |
+
"canton",
|
| 368 |
+
"cardano",
|
| 369 |
+
"casper",
|
| 370 |
+
"concordium",
|
| 371 |
+
"evm",
|
| 372 |
+
"hedera",
|
| 373 |
+
"keeta",
|
| 374 |
+
"lnbtc",
|
| 375 |
+
"near",
|
| 376 |
+
"starknet",
|
| 377 |
+
"stellar",
|
| 378 |
+
"sui",
|
| 379 |
+
"svm",
|
| 380 |
+
"ton",
|
| 381 |
+
"xrpl"
|
| 382 |
+
],
|
| 383 |
+
"notes": "specs/schemes/exact/scheme_exact_lnbtc.md says mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba. amount is a positive integer millisatoshi string. Bare numbers must not default to satoshis."
|
| 384 |
+
},
|
| 385 |
+
{
|
| 386 |
+
"name": "upto",
|
| 387 |
+
"bindings": [
|
| 388 |
+
"evm",
|
| 389 |
+
"svm",
|
| 390 |
+
"xrpl"
|
| 391 |
+
],
|
| 392 |
+
"notes": null
|
| 393 |
+
},
|
| 394 |
+
{
|
| 395 |
+
"name": "batch-settlement",
|
| 396 |
+
"bindings": [
|
| 397 |
+
"cloudflare",
|
| 398 |
+
"evm",
|
| 399 |
+
"svm"
|
| 400 |
+
],
|
| 401 |
+
"notes": null
|
| 402 |
+
},
|
| 403 |
+
{
|
| 404 |
+
"name": "auth-capture",
|
| 405 |
+
"bindings": [
|
| 406 |
+
"evm"
|
| 407 |
+
],
|
| 408 |
+
"notes": null
|
| 409 |
+
}
|
| 410 |
+
],
|
| 411 |
+
"source": "https://github.com/x402-foundation/x402/tree/main/specs/schemes",
|
| 412 |
+
"verified_at": "2026-11-03"
|
| 413 |
}
|
| 414 |
},
|
| 415 |
{
|
|
|
|
| 706 |
"source": "https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392",
|
| 707 |
"verified_at": "2026-10-31"
|
| 708 |
}
|
| 709 |
+
},
|
| 710 |
+
{
|
| 711 |
+
"id": "a2a",
|
| 712 |
+
"name": "A2A",
|
| 713 |
+
"featured": false,
|
| 714 |
+
"spec_url": {
|
| 715 |
+
"value": "https://a2a-protocol.org/latest/specification/",
|
| 716 |
+
"source": "https://a2a-protocol.org/latest/specification/",
|
| 717 |
+
"verified_at": "2026-11-03"
|
| 718 |
+
},
|
| 719 |
+
"http_status_codes": null,
|
| 720 |
+
"http_headers": null,
|
| 721 |
+
"payment_rail": null,
|
| 722 |
+
"networks": null,
|
| 723 |
+
"facilitators": null,
|
| 724 |
+
"client_libraries": null,
|
| 725 |
+
"pay_flow": null,
|
| 726 |
+
"notes": {
|
| 727 |
+
"value": "This record cites the version tags only. The GitHub releases list fetched on 2026-11-03 has v1.0.1 as the newest release, published 2026-05-28, and it is not a prerelease. Tag v1.1.0-rc is not in that releases list. It points at commit 78e1d6a1f7f118c8e9bc830b04a8579c1119cb78, dated 2026-10-29T12:05:26Z. Payment fields are null because those pages were not read for payment facts.",
|
| 728 |
+
"source": "https://github.com/a2aproject/A2A/releases/tag/v1.0.1",
|
| 729 |
+
"verified_at": "2026-11-03"
|
| 730 |
+
},
|
| 731 |
+
"version": {
|
| 732 |
+
"value": "1.0.1",
|
| 733 |
+
"source": "https://github.com/a2aproject/A2A/releases/tag/v1.0.1",
|
| 734 |
+
"verified_at": "2026-11-03"
|
| 735 |
+
},
|
| 736 |
+
"next_version": {
|
| 737 |
+
"value": "1.1.0-rc",
|
| 738 |
+
"source": "https://github.com/a2aproject/A2A/tree/v1.1.0-rc",
|
| 739 |
+
"verified_at": "2026-11-03"
|
| 740 |
+
}
|
| 741 |
}
|
| 742 |
]
|
| 743 |
}
|
data/sources.csv
CHANGED
|
@@ -1,12 +1,12 @@
|
|
| 1 |
id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
|
|
|
|
|
|
|
| 2 |
bitcoin-optech-newsletter-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,
|
| 3 |
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,
|
| 4 |
-
|
| 5 |
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,
|
| 6 |
-
wavelength-v0-2-0-release,Wavelength v0.2.0 (Mainnet is open),Lightning Labs (GitHub),,2026-10-23,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0,repo,bitcoin-lightning,spec_released,"First public mainnet release, published 2026-10-23. It adds scheduled batches and free-only automatic refresh, which waits for the operator's free-refresh window and rejects any quote that charges a fee. On mainnet the daemon rejects plaintext operator and swap connections and externally exposed HTTP gateways by default. Credit spending and top-ups have separate limits, and both default to zero.",lightning; ark; wallet; release,2026-10-25,true,2026-10-25,200,
|
| 7 |
lightning-labs-wavelength-mainnet,Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet,Lightning Labs,,2026-10-23,https://lightning.engineering/posts/2026-10-23-wavelength-mainnet-launch/,announcement,bitcoin-lightning,product_docs,"Wavelength, Lightning Labs' self-custodial wallet toolkit on an Ark-like settlement layer, is live on mainnet (alpha; repo release v0.2.0 on 2026-10-23). Agents can drive the wallet over MCP via `wavecli mcp serve`, pay L402 APIs, and get receive-only macaroons via `wavecli bakemacaroon`; retried requests do not pay twice. Current limits: 300,000 sats per mainnet account, 50,000 sats per VTXO, 0.25% service fee on Lightning sends and receives plus routing fees, and funds need a free automatic refresh roughly every two weeks. Docs ship llms.txt and llms-full.txt with .md twins of every page. License: MIT (GitHub repo). Related: https://wavelength.lightning.engineering/llms.txt, https://wavelength.lightning.engineering/llms-full.txt, https://wavelength.lightning.engineering/agents/, https://github.com/lightninglabs/wavelength, https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0.",lightning; ark; wallet; mcp; l402; macaroons; llms-txt; agent-tooling,2026-10-24,true,2026-10-24,200,
|
| 8 |
bitcoin-optech-newsletter-428,Bitcoin Optech Newsletter #428,Bitcoin Optech,,2026-10-23,https://bitcoinops.org/en/newsletters/2026/10/23/,report,bitcoin-lightning,news,"Covers Lichen, a single-issuer layer 2 with trust-minimized onchain exits, and a proposal for hash-preimage syntax in descriptors (BIP379). Also covers the Eclair 0.14.4/0.14.5 security releases, the LND 0.21.5/0.20.6 release candidates, LDK #5126 (a BOLT12 one-hop blinded path CLTV fix), LND #10919 (experimental local reputation against channel jamming), BTCPay Server fixes for duplicate Lightning payouts and Greenfield API key scope escalation, and BOLTs #1352 (simple taproot channel spec corrections).",bitcoin; lightning; bolt12; eclair; lnd; ldk; btcpay; optech,2026-10-24,true,2026-10-24,200,
|
| 9 |
-
getalby-js-sdk-v8-1-0-release,Release v8.1.0 · getAlby/js-sdk,GitHub (Alby),,2026-10-20,https://github.com/getAlby/js-sdk/releases/tag/v8.1.0,repo,bitcoin-lightning,product_docs,"Release of Alby's JavaScript SDK for the Nostr Wallet Connect API. Per the changelog, it adds a recordEvent handler to NWCWalletService for request deduplication, optional since/until filters on subscriptions and a publishNotification method, and it fixes subscription reconnect loops and validates payment and invoice amounts client-side.",nwc; nostr; lightning; agent-wallets; tools,2026-10-21,true,2026-10-21,200,
|
| 10 |
lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes,bolt11: reject duplicate payment hashes in invoices,GitHub (lightning/bolts),Roasbeef,2026-10-19,https://github.com/lightning/bolts/pull/1357,spec,bitcoin-lightning,spec_released,"Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.",lightning; standards; security; m2m-payments,2026-10-21,true,2026-10-21,200,
|
| 11 |
bitcoin-optech-newsletter-427,Bitcoin Optech Newsletter #427,Bitcoin Optech,,2026-10-16,https://bitcoinops.org/en/newsletters/2026/10/16/,report,bitcoin-lightning,news,"Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.",lightning; security; standards,2026-10-22,,2026-10-22,200,
|
| 12 |
getalby-hub-v1-24-3-release,Release v1.24.3 Julian Assange · getAlby/hub,GitHub (Alby),,2026-10-16,https://github.com/getAlby/hub/releases/tag/v1.24.3,repo,bitcoin-lightning,product_docs,"Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.",lightning; nwc; agent-wallets; security; tools,2026-10-21,true,2026-10-21,200,
|
|
@@ -75,6 +75,7 @@ visa-trusted-agent-protocol-press-release,Visa Introduces Trusted Agent Protocol
|
|
| 75 |
mastercard-agentic-commerce-tools-sep-2025,"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce",Mastercard,,2025-09-10,"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",announcement,payments,news,"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",card-networks; tokenization; identity,2026-10-20,,2026-10-20,403,"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"
|
| 76 |
cloudflare-pay-per-crawl,Introducing pay per crawl: Enabling content owners to charge AI crawlers for access,Cloudflare Blog,,2025-07-01,https://blog.cloudflare.com/introducing-pay-per-crawl/,announcement,payments,news,"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",m2m-payments; micropayments; web-agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/
|
| 77 |
x402-whitepaper,x402: An open standard for internet-native payments,Coinbase Developer Platform,Erik Reppel; Ronnie Caspers; Kevin Leffew; Danny Organ; Dan Kim; Nemil Dalal,2025-05-06,https://www.x402.org/x402-whitepaper.pdf,spec,payments,research,"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",x402; stablecoins; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf
|
|
|
|
| 78 |
coinbase-business-accept-x402-payments,Accept Agentic Payments with x402,Coinbase Developer Platform,,,https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments,docs,payments,product_docs,"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.",x402; stablecoins,2026-10-31,,2026-10-31,200,
|
| 79 |
x402-org,x402,x402,,,https://www.x402.org/,spec,payments,product_docs,"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",x402; m2m-payments; stablecoins,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261012224709/https://x402.org/
|
| 80 |
coinbase-x402-github,coinbase/x402,GitHub (Coinbase),,,https://github.com/coinbase/x402,repo,payments,spec_released,"Reference repository for x402, ""a payments protocol for the internet. Built on HTTP.""",x402; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260917165755/https://github.com/coinbase/x402
|
|
@@ -120,6 +121,8 @@ cloudflare-agent-readiness,Introducing the Agent Readiness score. Check to see i
|
|
| 120 |
mcp-specification-2025-06-18,Specification - Model Context Protocol (Version 2025-06-18),Model Context Protocol,,2025-06-18,https://modelcontextprotocol.io/specification/2025-06-18,spec,agent-protocols,spec_released,"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",mcp; interop; tools,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18
|
| 121 |
llms-txt,"The /llms.txt file, v2",llmstxt.org,Jeremy Howard,2024-09-03,https://llmstxt.org/,spec,agent-protocols,proposal,Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.,llms-txt; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016034533/https://llmstxt.org/
|
| 122 |
openapi-3-1-0,OpenAPI Specification v3.1.0,OpenAPI Initiative,,2021-02-15,https://spec.openapis.org/oas/v3.1.0.html,spec,agent-protocols,spec_released,"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",openapi; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html
|
|
|
|
|
|
|
| 123 |
a2a-protocol-specification,Agent2Agent (A2A) Protocol Specification,A2A Protocol,,,https://a2a-protocol.org/latest/specification/,spec,agent-protocols,spec_released,"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.",a2a; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/
|
| 124 |
rfc-9421-http-message-signatures,RFC 9421: HTTP Message Signatures,IETF,A. Backman; J. Richer; M. Sporny,,https://datatracker.ietf.org/doc/html/rfc9421,spec,agent-protocols,standard,"IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).",identity; security; http,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261006063814/https://datatracker.ietf.org/doc/html/rfc9421
|
| 125 |
mcp-registry,Official MCP Registry,Model Context Protocol,,,https://registry.modelcontextprotocol.io/,directory,agent-protocols,product_docs,"Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.",mcp; directory; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009210501/https://registry.modelcontextprotocol.io/
|
|
@@ -153,6 +156,7 @@ swe-bench-paper,SWE-bench: Can Language Models Resolve Real-World GitHub Issues?
|
|
| 153 |
webarena,WebArena: A Realistic Web Environment for Building Autonomous Agents,arXiv,Shuyan Zhou; Frank F. Xu; Hao Zhu; Xuhui Zhou; Robert Lo; Abishek Sridhar; Xianyi Cheng; Tianyue Ou; Yonatan Bisk; Daniel Fried; Uri Alon; Graham Neubig,2023-07-25,https://arxiv.org/abs/2307.13854,research-paper,datasets-benchmarks,research,Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.,benchmark; web-agents; research,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854
|
| 154 |
swe-bench-leaderboards,SWE-bench Leaderboards,SWE-bench,,,https://www.swebench.com/,docs,datasets-benchmarks,product_docs,"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",benchmark; leaderboard,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261019081426/https://www.swebench.com/
|
| 155 |
open-x-embodiment,Open X-Embodiment: Robotic Learning Datasets and RT-X Models,Open X-Embodiment Collaboration,,,https://robotics-transformer-x.github.io/,docs,datasets-benchmarks,product_docs,Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.,dataset; robotics,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/
|
|
|
|
| 156 |
v12-x402-25-vulnerabilities,25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings,V12,,2026-10-22,https://v12.sh/blog/x402,report,safety-security,research,"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.",x402; security; vulnerabilities; spend-controls; siwx; solana; sdk,2026-10-24,,2026-10-24,200,
|
| 157 |
cloudflare-verified-bots-continuous-accountability,Continuous accountability for Verified bots,Cloudflare,,2026-10-16,https://blog.cloudflare.com/verified-bots-accountability/,announcement,safety-security,news,"Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.",identity; web-agents; security; http,2026-10-21,,2026-10-21,200,
|
| 158 |
arxiv-approve-what-exactly-agent-step-up-authorization,"Approve What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up Authorization",arXiv,Sai Varun Kodathala; Prashanth Pollishetty; Jaylen Cargill,2026-10-15,https://arxiv.org/abs/2610.21063,research-paper,safety-security,research,"The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.",security; ap2; mcp; identity; research,2026-10-21,,2026-10-21,200,
|
|
|
|
| 1 |
id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
|
| 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,
|
|
|
|
| 8 |
lightning-labs-wavelength-mainnet,Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet,Lightning Labs,,2026-10-23,https://lightning.engineering/posts/2026-10-23-wavelength-mainnet-launch/,announcement,bitcoin-lightning,product_docs,"Wavelength, Lightning Labs' self-custodial wallet toolkit on an Ark-like settlement layer, is live on mainnet (alpha; repo release v0.2.0 on 2026-10-23). Agents can drive the wallet over MCP via `wavecli mcp serve`, pay L402 APIs, and get receive-only macaroons via `wavecli bakemacaroon`; retried requests do not pay twice. Current limits: 300,000 sats per mainnet account, 50,000 sats per VTXO, 0.25% service fee on Lightning sends and receives plus routing fees, and funds need a free automatic refresh roughly every two weeks. Docs ship llms.txt and llms-full.txt with .md twins of every page. License: MIT (GitHub repo). Related: https://wavelength.lightning.engineering/llms.txt, https://wavelength.lightning.engineering/llms-full.txt, https://wavelength.lightning.engineering/agents/, https://github.com/lightninglabs/wavelength, https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0.",lightning; ark; wallet; mcp; l402; macaroons; llms-txt; agent-tooling,2026-10-24,true,2026-10-24,200,
|
| 9 |
bitcoin-optech-newsletter-428,Bitcoin Optech Newsletter #428,Bitcoin Optech,,2026-10-23,https://bitcoinops.org/en/newsletters/2026/10/23/,report,bitcoin-lightning,news,"Covers Lichen, a single-issuer layer 2 with trust-minimized onchain exits, and a proposal for hash-preimage syntax in descriptors (BIP379). Also covers the Eclair 0.14.4/0.14.5 security releases, the LND 0.21.5/0.20.6 release candidates, LDK #5126 (a BOLT12 one-hop blinded path CLTV fix), LND #10919 (experimental local reputation against channel jamming), BTCPay Server fixes for duplicate Lightning payouts and Greenfield API key scope escalation, and BOLTs #1352 (simple taproot channel spec corrections).",bitcoin; lightning; bolt12; eclair; lnd; ldk; btcpay; optech,2026-10-24,true,2026-10-24,200,
|
|
|
|
| 10 |
lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes,bolt11: reject duplicate payment hashes in invoices,GitHub (lightning/bolts),Roasbeef,2026-10-19,https://github.com/lightning/bolts/pull/1357,spec,bitcoin-lightning,spec_released,"Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.",lightning; standards; security; m2m-payments,2026-10-21,true,2026-10-21,200,
|
| 11 |
bitcoin-optech-newsletter-427,Bitcoin Optech Newsletter #427,Bitcoin Optech,,2026-10-16,https://bitcoinops.org/en/newsletters/2026/10/16/,report,bitcoin-lightning,news,"Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.",lightning; security; standards,2026-10-22,,2026-10-22,200,
|
| 12 |
getalby-hub-v1-24-3-release,Release v1.24.3 Julian Assange · getAlby/hub,GitHub (Alby),,2026-10-16,https://github.com/getAlby/hub/releases/tag/v1.24.3,repo,bitcoin-lightning,product_docs,"Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.",lightning; nwc; agent-wallets; security; tools,2026-10-21,true,2026-10-21,200,
|
|
|
|
| 75 |
mastercard-agentic-commerce-tools-sep-2025,"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce",Mastercard,,2025-09-10,"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html",announcement,payments,news,"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.",card-networks; tokenization; identity,2026-10-20,,2026-10-20,403,"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"
|
| 76 |
cloudflare-pay-per-crawl,Introducing pay per crawl: Enabling content owners to charge AI crawlers for access,Cloudflare Blog,,2025-07-01,https://blog.cloudflare.com/introducing-pay-per-crawl/,announcement,payments,news,"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.",m2m-payments; micropayments; web-agents,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/
|
| 77 |
x402-whitepaper,x402: An open standard for internet-native payments,Coinbase Developer Platform,Erik Reppel; Ronnie Caspers; Kevin Leffew; Danny Organ; Dan Kim; Nemil Dalal,2025-05-06,https://www.x402.org/x402-whitepaper.pdf,spec,payments,research,"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.",x402; stablecoins; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf
|
| 78 |
+
link-balance-agent-wallet-purchases,Set up a balance for agent wallet purchases,Link (Stripe),,,https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases,docs,payments,product_docs,"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.",agent-wallets; stablecoins,2026-11-03,,2026-11-03,200,
|
| 79 |
coinbase-business-accept-x402-payments,Accept Agentic Payments with x402,Coinbase Developer Platform,,,https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments,docs,payments,product_docs,"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.",x402; stablecoins,2026-10-31,,2026-10-31,200,
|
| 80 |
x402-org,x402,x402,,,https://www.x402.org/,spec,payments,product_docs,"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.",x402; m2m-payments; stablecoins,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261012224709/https://x402.org/
|
| 81 |
coinbase-x402-github,coinbase/x402,GitHub (Coinbase),,,https://github.com/coinbase/x402,repo,payments,spec_released,"Reference repository for x402, ""a payments protocol for the internet. Built on HTTP.""",x402; m2m-payments,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260917165755/https://github.com/coinbase/x402
|
|
|
|
| 121 |
mcp-specification-2025-06-18,Specification - Model Context Protocol (Version 2025-06-18),Model Context Protocol,,2025-06-18,https://modelcontextprotocol.io/specification/2025-06-18,spec,agent-protocols,spec_released,"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.",mcp; interop; tools,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18
|
| 122 |
llms-txt,"The /llms.txt file, v2",llmstxt.org,Jeremy Howard,2024-09-03,https://llmstxt.org/,spec,agent-protocols,proposal,Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.,llms-txt; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261016034533/https://llmstxt.org/
|
| 123 |
openapi-3-1-0,OpenAPI Specification v3.1.0,OpenAPI Initiative,,2021-02-15,https://spec.openapis.org/oas/v3.1.0.html,spec,agent-protocols,spec_released,"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.",openapi; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html
|
| 124 |
+
x402-scheme-exact-lnbtc,x402 scheme: exact on Bitcoin Lightning (lnbtc),x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md,spec,agent-protocols,spec_released,"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.",x402; lightning; standards,2026-11-03,true,2026-11-03,200,
|
| 125 |
+
x402-scheme-batch-settlement,x402 scheme: batch-settlement,x402 Foundation (GitHub),,,https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md,spec,agent-protocols,spec_released,"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.",x402; standards,2026-11-03,,2026-11-03,200,
|
| 126 |
a2a-protocol-specification,Agent2Agent (A2A) Protocol Specification,A2A Protocol,,,https://a2a-protocol.org/latest/specification/,spec,agent-protocols,spec_released,"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.",a2a; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/
|
| 127 |
rfc-9421-http-message-signatures,RFC 9421: HTTP Message Signatures,IETF,A. Backman; J. Richer; M. Sporny,,https://datatracker.ietf.org/doc/html/rfc9421,spec,agent-protocols,standard,"IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).",identity; security; http,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261006063814/https://datatracker.ietf.org/doc/html/rfc9421
|
| 128 |
mcp-registry,Official MCP Registry,Model Context Protocol,,,https://registry.modelcontextprotocol.io/,directory,agent-protocols,product_docs,"Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.",mcp; directory; interop,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261009210501/https://registry.modelcontextprotocol.io/
|
|
|
|
| 156 |
webarena,WebArena: A Realistic Web Environment for Building Autonomous Agents,arXiv,Shuyan Zhou; Frank F. Xu; Hao Zhu; Xuhui Zhou; Robert Lo; Abishek Sridhar; Xianyi Cheng; Tianyue Ou; Yonatan Bisk; Daniel Fried; Uri Alon; Graham Neubig,2023-07-25,https://arxiv.org/abs/2307.13854,research-paper,datasets-benchmarks,research,Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.,benchmark; web-agents; research,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854
|
| 157 |
swe-bench-leaderboards,SWE-bench Leaderboards,SWE-bench,,,https://www.swebench.com/,docs,datasets-benchmarks,product_docs,"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.",benchmark; leaderboard,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20261019081426/https://www.swebench.com/
|
| 158 |
open-x-embodiment,Open X-Embodiment: Robotic Learning Datasets and RT-X Models,Open X-Embodiment Collaboration,,,https://robotics-transformer-x.github.io/,docs,datasets-benchmarks,product_docs,Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.,dataset; robotics,2026-10-20,,2026-10-20,200,http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/
|
| 159 |
+
arxiv-2610-35835-i-hitl,I-HITL: Inalienable Human-in-the-Loop,arXiv,Samuel Breckenridge; Dani Vilardell; Wenhao Wang; Fan Zhang; Ari Juels,2026-10-26,https://arxiv.org/abs/2610.35835,research-paper,safety-security,research,"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.",security; research; agent-wallets,2026-11-03,,2026-11-03,200,
|
| 160 |
v12-x402-25-vulnerabilities,25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings,V12,,2026-10-22,https://v12.sh/blog/x402,report,safety-security,research,"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.",x402; security; vulnerabilities; spend-controls; siwx; solana; sdk,2026-10-24,,2026-10-24,200,
|
| 161 |
cloudflare-verified-bots-continuous-accountability,Continuous accountability for Verified bots,Cloudflare,,2026-10-16,https://blog.cloudflare.com/verified-bots-accountability/,announcement,safety-security,news,"Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.",identity; web-agents; security; http,2026-10-21,,2026-10-21,200,
|
| 162 |
arxiv-approve-what-exactly-agent-step-up-authorization,"Approve What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up Authorization",arXiv,Sai Varun Kodathala; Prashanth Pollishetty; Jaylen Cargill,2026-10-15,https://arxiv.org/abs/2610.21063,research-paper,safety-security,research,"The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.",security; ap2; mcp; identity; research,2026-10-21,,2026-10-21,200,
|
data/sources.jsonl
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
|
|
|
|
|
| 1 |
{"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}
|
| 2 |
{"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}
|
| 3 |
-
{"id":"
|
| 4 |
{"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}
|
| 5 |
-
{"id":"wavelength-v0-2-0-release","title":"Wavelength v0.2.0 (Mainnet is open)","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-23","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"First public mainnet release, published 2026-10-23. It adds scheduled batches and free-only automatic refresh, which waits for the operator's free-refresh window and rejects any quote that charges a fee. On mainnet the daemon rejects plaintext operator and swap connections and externally exposed HTTP gateways by default. Credit spending and top-ups have separate limits, and both default to zero.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-10-25","featured":true,"last_checked":"2026-10-25","http_status":200,"archive_url":null}
|
| 6 |
{"id":"lightning-labs-wavelength-mainnet","title":"Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-23","url":"https://lightning.engineering/posts/2026-10-23-wavelength-mainnet-launch/","type":"announcement","category":"bitcoin-lightning","status":"product_docs","summary":"Wavelength, Lightning Labs' self-custodial wallet toolkit on an Ark-like settlement layer, is live on mainnet (alpha; repo release v0.2.0 on 2026-10-23). Agents can drive the wallet over MCP via `wavecli mcp serve`, pay L402 APIs, and get receive-only macaroons via `wavecli bakemacaroon`; retried requests do not pay twice. Current limits: 300,000 sats per mainnet account, 50,000 sats per VTXO, 0.25% service fee on Lightning sends and receives plus routing fees, and funds need a free automatic refresh roughly every two weeks. Docs ship llms.txt and llms-full.txt with .md twins of every page. License: MIT (GitHub repo). Related: https://wavelength.lightning.engineering/llms.txt, https://wavelength.lightning.engineering/llms-full.txt, https://wavelength.lightning.engineering/agents/, https://github.com/lightninglabs/wavelength, https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0.","tags":["lightning","ark","wallet","mcp","l402","macaroons","llms-txt","agent-tooling"],"verified_at":"2026-10-24","featured":true,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
| 7 |
{"id":"bitcoin-optech-newsletter-428","title":"Bitcoin Optech Newsletter #428","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-23","url":"https://bitcoinops.org/en/newsletters/2026/10/23/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Covers Lichen, a single-issuer layer 2 with trust-minimized onchain exits, and a proposal for hash-preimage syntax in descriptors (BIP379). Also covers the Eclair 0.14.4/0.14.5 security releases, the LND 0.21.5/0.20.6 release candidates, LDK #5126 (a BOLT12 one-hop blinded path CLTV fix), LND #10919 (experimental local reputation against channel jamming), BTCPay Server fixes for duplicate Lightning payouts and Greenfield API key scope escalation, and BOLTs #1352 (simple taproot channel spec corrections).","tags":["bitcoin","lightning","bolt12","eclair","lnd","ldk","btcpay","optech"],"verified_at":"2026-10-24","featured":true,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
| 8 |
-
{"id":"getalby-js-sdk-v8-1-0-release","title":"Release v8.1.0 · getAlby/js-sdk","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-10-20","url":"https://github.com/getAlby/js-sdk/releases/tag/v8.1.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release of Alby's JavaScript SDK for the Nostr Wallet Connect API. Per the changelog, it adds a recordEvent handler to NWCWalletService for request deduplication, optional since/until filters on subscriptions and a publishNotification method, and it fixes subscription reconnect loops and validates payment and invoice amounts client-side.","tags":["nwc","nostr","lightning","agent-wallets","tools"],"verified_at":"2026-10-21","featured":true,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
| 9 |
{"id":"lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes","title":"bolt11: reject duplicate payment hashes in invoices","publisher":"GitHub (lightning/bolts)","authors":["Roasbeef"],"date_published":"2026-10-19","url":"https://github.com/lightning/bolts/pull/1357","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.","tags":["lightning","standards","security","m2m-payments"],"verified_at":"2026-10-21","featured":true,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
| 10 |
{"id":"bitcoin-optech-newsletter-427","title":"Bitcoin Optech Newsletter #427","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-16","url":"https://bitcoinops.org/en/newsletters/2026/10/16/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.","tags":["lightning","security","standards"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 11 |
{"id":"getalby-hub-v1-24-3-release","title":"Release v1.24.3 Julian Assange · getAlby/hub","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-10-16","url":"https://github.com/getAlby/hub/releases/tag/v1.24.3","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.","tags":["lightning","nwc","agent-wallets","security","tools"],"verified_at":"2026-10-21","featured":true,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
|
@@ -74,6 +74,7 @@
|
|
| 74 |
{"id":"mastercard-agentic-commerce-tools-sep-2025","title":"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce","publisher":"Mastercard","authors":[],"date_published":"2025-09-10","url":"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html","type":"announcement","category":"payments","status":"news","summary":"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.","tags":["card-networks","tokenization","identity"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":403,"archive_url":"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"}
|
| 75 |
{"id":"cloudflare-pay-per-crawl","title":"Introducing pay per crawl: Enabling content owners to charge AI crawlers for access","publisher":"Cloudflare Blog","authors":[],"date_published":"2025-07-01","url":"https://blog.cloudflare.com/introducing-pay-per-crawl/","type":"announcement","category":"payments","status":"news","summary":"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.","tags":["m2m-payments","micropayments","web-agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/"}
|
| 76 |
{"id":"x402-whitepaper","title":"x402: An open standard for internet-native payments","publisher":"Coinbase Developer Platform","authors":["Erik Reppel","Ronnie Caspers","Kevin Leffew","Danny Organ","Dan Kim","Nemil Dalal"],"date_published":"2025-05-06","url":"https://www.x402.org/x402-whitepaper.pdf","type":"spec","category":"payments","status":"research","summary":"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.","tags":["x402","stablecoins","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"}
|
|
|
|
| 77 |
{"id":"coinbase-business-accept-x402-payments","title":"Accept Agentic Payments with x402","publisher":"Coinbase Developer Platform","authors":[],"date_published":null,"url":"https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments","type":"docs","category":"payments","status":"product_docs","summary":"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.","tags":["x402","stablecoins"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
|
| 78 |
{"id":"x402-org","title":"x402","publisher":"x402","authors":[],"date_published":null,"url":"https://www.x402.org/","type":"spec","category":"payments","status":"product_docs","summary":"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.","tags":["x402","m2m-payments","stablecoins"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261012224709/https://x402.org/"}
|
| 79 |
{"id":"coinbase-x402-github","title":"coinbase/x402","publisher":"GitHub (Coinbase)","authors":[],"date_published":null,"url":"https://github.com/coinbase/x402","type":"repo","category":"payments","status":"spec_released","summary":"Reference repository for x402, \"a payments protocol for the internet. Built on HTTP.\"","tags":["x402","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260917165755/https://github.com/coinbase/x402"}
|
|
@@ -119,6 +120,8 @@
|
|
| 119 |
{"id":"mcp-specification-2025-06-18","title":"Specification - Model Context Protocol (Version 2025-06-18)","publisher":"Model Context Protocol","authors":[],"date_published":"2025-06-18","url":"https://modelcontextprotocol.io/specification/2025-06-18","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.","tags":["mcp","interop","tools"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18"}
|
| 120 |
{"id":"llms-txt","title":"The /llms.txt file, v2","publisher":"llmstxt.org","authors":["Jeremy Howard"],"date_published":"2024-09-03","url":"https://llmstxt.org/","type":"spec","category":"agent-protocols","status":"proposal","summary":"Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.","tags":["llms-txt","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016034533/https://llmstxt.org/"}
|
| 121 |
{"id":"openapi-3-1-0","title":"OpenAPI Specification v3.1.0","publisher":"OpenAPI Initiative","authors":[],"date_published":"2021-02-15","url":"https://spec.openapis.org/oas/v3.1.0.html","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.","tags":["openapi","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"}
|
|
|
|
|
|
|
| 122 |
{"id":"a2a-protocol-specification","title":"Agent2Agent (A2A) Protocol Specification","publisher":"A2A Protocol","authors":[],"date_published":null,"url":"https://a2a-protocol.org/latest/specification/","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.","tags":["a2a","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/"}
|
| 123 |
{"id":"rfc-9421-http-message-signatures","title":"RFC 9421: HTTP Message Signatures","publisher":"IETF","authors":["A. Backman","J. Richer","M. Sporny"],"date_published":null,"url":"https://datatracker.ietf.org/doc/html/rfc9421","type":"spec","category":"agent-protocols","status":"standard","summary":"IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).","tags":["identity","security","http"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261006063814/https://datatracker.ietf.org/doc/html/rfc9421"}
|
| 124 |
{"id":"mcp-registry","title":"Official MCP Registry","publisher":"Model Context Protocol","authors":[],"date_published":null,"url":"https://registry.modelcontextprotocol.io/","type":"directory","category":"agent-protocols","status":"product_docs","summary":"Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.","tags":["mcp","directory","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009210501/https://registry.modelcontextprotocol.io/"}
|
|
@@ -152,6 +155,7 @@
|
|
| 152 |
{"id":"webarena","title":"WebArena: A Realistic Web Environment for Building Autonomous Agents","publisher":"arXiv","authors":["Shuyan Zhou","Frank F. Xu","Hao Zhu","Xuhui Zhou","Robert Lo","Abishek Sridhar","Xianyi Cheng","Tianyue Ou","Yonatan Bisk","Daniel Fried","Uri Alon","Graham Neubig"],"date_published":"2023-07-25","url":"https://arxiv.org/abs/2307.13854","type":"research-paper","category":"datasets-benchmarks","status":"research","summary":"Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.","tags":["benchmark","web-agents","research"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854"}
|
| 153 |
{"id":"swe-bench-leaderboards","title":"SWE-bench Leaderboards","publisher":"SWE-bench","authors":[],"date_published":null,"url":"https://www.swebench.com/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.","tags":["benchmark","leaderboard"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261019081426/https://www.swebench.com/"}
|
| 154 |
{"id":"open-x-embodiment","title":"Open X-Embodiment: Robotic Learning Datasets and RT-X Models","publisher":"Open X-Embodiment Collaboration","authors":[],"date_published":null,"url":"https://robotics-transformer-x.github.io/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.","tags":["dataset","robotics"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"}
|
|
|
|
| 155 |
{"id":"v12-x402-25-vulnerabilities","title":"25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings","publisher":"V12","authors":[],"date_published":"2026-10-22","url":"https://v12.sh/blog/x402","type":"report","category":"safety-security","status":"research","summary":"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.","tags":["x402","security","vulnerabilities","spend-controls","siwx","solana","sdk"],"verified_at":"2026-10-24","featured":false,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
| 156 |
{"id":"cloudflare-verified-bots-continuous-accountability","title":"Continuous accountability for Verified bots","publisher":"Cloudflare","authors":[],"date_published":"2026-10-16","url":"https://blog.cloudflare.com/verified-bots-accountability/","type":"announcement","category":"safety-security","status":"news","summary":"Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.","tags":["identity","web-agents","security","http"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
| 157 |
{"id":"arxiv-approve-what-exactly-agent-step-up-authorization","title":"Approve What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up Authorization","publisher":"arXiv","authors":["Sai Varun Kodathala","Prashanth Pollishetty","Jaylen Cargill"],"date_published":"2026-10-15","url":"https://arxiv.org/abs/2610.21063","type":"research-paper","category":"safety-security","status":"research","summary":"The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.","tags":["security","ap2","mcp","identity","research"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","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":"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}
|
|
|
|
| 7 |
{"id":"lightning-labs-wavelength-mainnet","title":"Ride the Wave: Integrate Bitcoin Payments with Wavelength on Mainnet","publisher":"Lightning Labs","authors":[],"date_published":"2026-10-23","url":"https://lightning.engineering/posts/2026-10-23-wavelength-mainnet-launch/","type":"announcement","category":"bitcoin-lightning","status":"product_docs","summary":"Wavelength, Lightning Labs' self-custodial wallet toolkit on an Ark-like settlement layer, is live on mainnet (alpha; repo release v0.2.0 on 2026-10-23). Agents can drive the wallet over MCP via `wavecli mcp serve`, pay L402 APIs, and get receive-only macaroons via `wavecli bakemacaroon`; retried requests do not pay twice. Current limits: 300,000 sats per mainnet account, 50,000 sats per VTXO, 0.25% service fee on Lightning sends and receives plus routing fees, and funds need a free automatic refresh roughly every two weeks. Docs ship llms.txt and llms-full.txt with .md twins of every page. License: MIT (GitHub repo). Related: https://wavelength.lightning.engineering/llms.txt, https://wavelength.lightning.engineering/llms-full.txt, https://wavelength.lightning.engineering/agents/, https://github.com/lightninglabs/wavelength, https://github.com/lightninglabs/wavelength/releases/tag/v0.2.0.","tags":["lightning","ark","wallet","mcp","l402","macaroons","llms-txt","agent-tooling"],"verified_at":"2026-10-24","featured":true,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
| 8 |
{"id":"bitcoin-optech-newsletter-428","title":"Bitcoin Optech Newsletter #428","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-23","url":"https://bitcoinops.org/en/newsletters/2026/10/23/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Covers Lichen, a single-issuer layer 2 with trust-minimized onchain exits, and a proposal for hash-preimage syntax in descriptors (BIP379). Also covers the Eclair 0.14.4/0.14.5 security releases, the LND 0.21.5/0.20.6 release candidates, LDK #5126 (a BOLT12 one-hop blinded path CLTV fix), LND #10919 (experimental local reputation against channel jamming), BTCPay Server fixes for duplicate Lightning payouts and Greenfield API key scope escalation, and BOLTs #1352 (simple taproot channel spec corrections).","tags":["bitcoin","lightning","bolt12","eclair","lnd","ldk","btcpay","optech"],"verified_at":"2026-10-24","featured":true,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
|
|
|
| 9 |
{"id":"lightning-bolts-pr-1357-bolt11-duplicate-payment-hashes","title":"bolt11: reject duplicate payment hashes in invoices","publisher":"GitHub (lightning/bolts)","authors":["Roasbeef"],"date_published":"2026-10-19","url":"https://github.com/lightning/bolts/pull/1357","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Merged change to the BOLT #11 specification that requires readers to reject an invoice with more than one payment hash, with updated test vectors. The PR explains that libraries differed on whether they took the first or the last payment hash, and that a popular Telegram P2P bot was exploited through this ambiguity, which matters for any system that pays or verifies invoices automatically.","tags":["lightning","standards","security","m2m-payments"],"verified_at":"2026-10-21","featured":true,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
| 10 |
{"id":"bitcoin-optech-newsletter-427","title":"Bitcoin Optech Newsletter #427","publisher":"Bitcoin Optech","authors":[],"date_published":"2026-10-16","url":"https://bitcoinops.org/en/newsletters/2026/10/16/","type":"report","category":"bitcoin-lightning","status":"news","summary":"Newsletter for the week of 2026-10-16. It summarizes the disclosure of two denial-of-service vulnerabilities in Eclair v0.14.0 and earlier, both fixed in v0.14.1, and Adam Gibson's proposal for running multi-round two-party contracts inside a Lightning channel while settling disputes on-chain in a constant number of transactions.","tags":["lightning","security","standards"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 11 |
{"id":"getalby-hub-v1-24-3-release","title":"Release v1.24.3 Julian Assange · getAlby/hub","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-10-16","url":"https://github.com/getAlby/hub/releases/tag/v1.24.3","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release of the self-hosted Alby Hub Lightning node, which exposes wallet connections to apps over Nostr Wallet Connect. Per the release notes, it restricts settling and cancelling hold invoices to the app connection that created them, stops returning the owner's Lightning address to isolated app connections, re-enables on-chain/Lightning swaps with configurable swap providers, and includes UX fixes and security updates.","tags":["lightning","nwc","agent-wallets","security","tools"],"verified_at":"2026-10-21","featured":true,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
|
|
|
| 74 |
{"id":"mastercard-agentic-commerce-tools-sep-2025","title":"Mastercard unveils new tools and collaborations to power smarter, safer agentic commerce","publisher":"Mastercard","authors":[],"date_published":"2025-09-10","url":"https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html","type":"announcement","category":"payments","status":"news","summary":"Mastercard press release on new developer tools, expanded consulting services and ecosystem collaborations for AI-powered payments, aimed at trusted agentic transaction standards.","tags":["card-networks","tokenization","identity"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":403,"archive_url":"http://web.archive.org/web/20260605202222/https://www.mastercard.com/global/en/news-and-trends/press/2025/september/mastercard-unveils-new-tools-and-collaborations-to-power-smarter,-safer-agentic-commerce.html"}
|
| 75 |
{"id":"cloudflare-pay-per-crawl","title":"Introducing pay per crawl: Enabling content owners to charge AI crawlers for access","publisher":"Cloudflare Blog","authors":[],"date_published":"2025-07-01","url":"https://blog.cloudflare.com/introducing-pay-per-crawl/","type":"announcement","category":"payments","status":"news","summary":"Cloudflare announcement of pay per crawl, which lets content owners charge AI crawlers for access using HTTP 402 responses. It is a machine-payable content model at CDN scale.","tags":["m2m-payments","micropayments","web-agents"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016042320/https://blog.cloudflare.com/introducing-pay-per-crawl/"}
|
| 76 |
{"id":"x402-whitepaper","title":"x402: An open standard for internet-native payments","publisher":"Coinbase Developer Platform","authors":["Erik Reppel","Ronnie Caspers","Kevin Leffew","Danny Organ","Dan Kim","Nemil Dalal"],"date_published":"2025-05-06","url":"https://www.x402.org/x402-whitepaper.pdf","type":"spec","category":"payments","status":"research","summary":"Whitepaper describing x402, an HTTP-based protocol that uses onchain payments for agents, context retrieval and APIs. It explains why traditional rails fail for autonomous payments and how x402 works.","tags":["x402","stablecoins","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260605201607/https://www.x402.org/x402-whitepaper.pdf"}
|
| 77 |
+
{"id":"link-balance-agent-wallet-purchases","title":"Set up a balance for agent wallet purchases","publisher":"Link (Stripe)","authors":[],"date_published":null,"url":"https://support.link.com/questions/set-up-a-balance-for-agent-wallet-purchases","type":"docs","category":"payments","status":"product_docs","summary":"Link support page. article:modified_time is 2026-10-21. The page does not state a publication date. Setup asks for date of birth and the last four digits of an SSN, and all nine digits if that check fails. The user sets a per-purchase limit, the maximum the agent can spend without requesting approval. Money is added with a supported credit or debit card. The page says money in the balance is held as USDC. A custodial balance is a wallet managed by Bridge, a Stripe company. A self-custodial balance is accessed with Privy, and the page says Link does not hold those assets as a custodian. An agent cannot skip approval for a purchase above the per-purchase limit.","tags":["agent-wallets","stablecoins"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
|
| 78 |
{"id":"coinbase-business-accept-x402-payments","title":"Accept Agentic Payments with x402","publisher":"Coinbase Developer Platform","authors":[],"date_published":null,"url":"https://docs.cdp.coinbase.com/coinbase-business/checkout-apis/accept-x402-payments","type":"docs","category":"payments","status":"product_docs","summary":"Coinbase Business Checkouts docs. The page does not state a publish date. POST https://business.coinbase.com/api/v1/checkouts returns an x402_url. The page says paying that URL authorizes a gasless USDC payment on Base using EIP-3009, and that Coinbase captures and settles it server-side. It says the checkout moves ACTIVE, then PROCESSING, then COMPLETED, and that COMPLETED is the source of truth for settlement. PROCESSING may not be observed. A rejected payment returns another 402 and leaves the checkout ACTIVE. FAILED, EXPIRED, and DEACTIVATED are also listed. The page says checkouts advertise the EVM auth-capture scheme.","tags":["x402","stablecoins"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
|
| 79 |
{"id":"x402-org","title":"x402","publisher":"x402","authors":[],"date_published":null,"url":"https://www.x402.org/","type":"spec","category":"payments","status":"product_docs","summary":"Official x402 site, describing it as an open standard for internet-native payments that enables agentic payments at scale.","tags":["x402","m2m-payments","stablecoins"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261012224709/https://x402.org/"}
|
| 80 |
{"id":"coinbase-x402-github","title":"coinbase/x402","publisher":"GitHub (Coinbase)","authors":[],"date_published":null,"url":"https://github.com/coinbase/x402","type":"repo","category":"payments","status":"spec_released","summary":"Reference repository for x402, \"a payments protocol for the internet. Built on HTTP.\"","tags":["x402","m2m-payments"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260917165755/https://github.com/coinbase/x402"}
|
|
|
|
| 120 |
{"id":"mcp-specification-2025-06-18","title":"Specification - Model Context Protocol (Version 2025-06-18)","publisher":"Model Context Protocol","authors":[],"date_published":"2025-06-18","url":"https://modelcontextprotocol.io/specification/2025-06-18","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Earlier dated revision of the MCP specification, covering authorization, transports, roots, sampling, elicitation, prompts and resources.","tags":["mcp","interop","tools"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260924095810/https://modelcontextprotocol.io/specification/2025-06-18"}
|
| 121 |
{"id":"llms-txt","title":"The /llms.txt file, v2","publisher":"llmstxt.org","authors":["Jeremy Howard"],"date_published":"2024-09-03","url":"https://llmstxt.org/","type":"spec","category":"agent-protocols","status":"proposal","summary":"Proposal to standardise an /llms.txt file that gives agents information about how to use a website. The page was last modified on 10 August 2026.","tags":["llms-txt","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261016034533/https://llmstxt.org/"}
|
| 122 |
{"id":"openapi-3-1-0","title":"OpenAPI Specification v3.1.0","publisher":"OpenAPI Initiative","authors":[],"date_published":"2021-02-15","url":"https://spec.openapis.org/oas/v3.1.0.html","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Standard, programming-language-agnostic interface description for HTTP APIs, widely used to describe tools and APIs for programmatic consumers.","tags":["openapi","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261008125912/https://spec.openapis.org/oas/v3.1.0.html"}
|
| 123 |
+
{"id":"x402-scheme-exact-lnbtc","title":"x402 scheme: exact on Bitcoin Lightning (lnbtc)","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_lnbtc.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 exact scheme on Lightning. It says the facilitator checks SHA-256(preimage) equals payment_hash and that the invoice signing key matches payTo. It supports only the bolt11 asset transfer method and the upfront flow. Mainnet MUST use lnbtc:000000000019d6689c085ae165831e93 and BOLT11 currency bc. Testnet MUST use lnbtc:000000000933ea01ad0ee984209779ba and currency tb. amount MUST be a decimal string of a positive integer number of millisatoshis, and bare numbers MUST NOT default to satoshis. The file does not state a publication date.","tags":["x402","lightning","standards"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
|
| 124 |
+
{"id":"x402-scheme-batch-settlement","title":"x402 scheme: batch-settlement","publisher":"x402 Foundation (GitHub)","authors":[],"date_published":null,"url":"https://github.com/x402-foundation/x402/blob/main/specs/schemes/batch-settlement/scheme_batch_settlement.md","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Specification for the x402 batch-settlement scheme. The client provides a cryptographic payment commitment at request time, access is granted immediately, and value moves later through the network binding. The client commits up to PaymentRequirements.amount and the server may charge less. For exact and upto, the settlement result contains an onchain transaction hash. For batch-settlement it contains a commitment identifier. Bindings in the same directory are scheme_batch_settlement_evm.md, scheme_batch_settlement_svm.md, and scheme_batch_settlement_cloudflare.md. The file does not state a publication date.","tags":["x402","standards"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
|
| 125 |
{"id":"a2a-protocol-specification","title":"Agent2Agent (A2A) Protocol Specification","publisher":"A2A Protocol","authors":[],"date_published":null,"url":"https://a2a-protocol.org/latest/specification/","type":"spec","category":"agent-protocols","status":"spec_released","summary":"Official A2A specification (latest released version 1.0.0), an open standard for communication and interoperability between independent, potentially opaque AI agent systems built on different frameworks or by different vendors.","tags":["a2a","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009134313/https://a2a-protocol.org/latest/specification/"}
|
| 126 |
{"id":"rfc-9421-http-message-signatures","title":"RFC 9421: HTTP Message Signatures","publisher":"IETF","authors":["A. Backman","J. Richer","M. Sporny"],"date_published":null,"url":"https://datatracker.ietf.org/doc/html/rfc9421","type":"spec","category":"agent-protocols","status":"standard","summary":"IETF Proposed Standard defining how to create, encode and verify digital signatures over components of HTTP messages. It can serve as a building block for authenticating automated clients. Published February 2024 (no day given, so date_published is null).","tags":["identity","security","http"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261006063814/https://datatracker.ietf.org/doc/html/rfc9421"}
|
| 127 |
{"id":"mcp-registry","title":"Official MCP Registry","publisher":"Model Context Protocol","authors":[],"date_published":null,"url":"https://registry.modelcontextprotocol.io/","type":"directory","category":"agent-protocols","status":"product_docs","summary":"Official registry of MCP servers with an unauthenticated read API (GET /v0.1/servers) supporting cursor pagination, name search and updated_since for incremental sync by downstream aggregators.","tags":["mcp","directory","interop"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261009210501/https://registry.modelcontextprotocol.io/"}
|
|
|
|
| 155 |
{"id":"webarena","title":"WebArena: A Realistic Web Environment for Building Autonomous Agents","publisher":"arXiv","authors":["Shuyan Zhou","Frank F. Xu","Hao Zhu","Xuhui Zhou","Robert Lo","Abishek Sridhar","Xianyi Cheng","Tianyue Ou","Yonatan Bisk","Daniel Fried","Uri Alon","Graham Neubig"],"date_published":"2023-07-25","url":"https://arxiv.org/abs/2307.13854","type":"research-paper","category":"datasets-benchmarks","status":"research","summary":"Highly realistic and reproducible web environment for building and testing language-guided agents that perform tasks on the web. The authors list shows the first 12 of a longer list.","tags":["benchmark","web-agents","research"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261002191854/https://arxiv.org/abs/2307.13854"}
|
| 156 |
{"id":"swe-bench-leaderboards","title":"SWE-bench Leaderboards","publisher":"SWE-bench","authors":[],"date_published":null,"url":"https://www.swebench.com/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Official SWE-bench site with leaderboards for SWE-bench, Verified, Multilingual, Multimodal and Lite variants, plus related tools.","tags":["benchmark","leaderboard"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261019081426/https://www.swebench.com/"}
|
| 157 |
{"id":"open-x-embodiment","title":"Open X-Embodiment: Robotic Learning Datasets and RT-X Models","publisher":"Open X-Embodiment Collaboration","authors":[],"date_published":null,"url":"https://robotics-transformer-x.github.io/","type":"docs","category":"datasets-benchmarks","status":"product_docs","summary":"Project page of the Open X-Embodiment Collaboration presenting robotic learning datasets and RT-X models. It asks whether the consolidation around large pretrained models seen in NLP and computer vision can happen in robotics.","tags":["dataset","robotics"],"verified_at":"2026-10-20","last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260905225407/https://robotics-transformer-x.github.io/"}
|
| 158 |
+
{"id":"arxiv-2610-35835-i-hitl","title":"I-HITL: Inalienable Human-in-the-Loop","publisher":"arXiv","authors":["Samuel Breckenridge","Dani Vilardell","Wenhao Wang","Fan Zhang","Ari Juels"],"date_published":"2026-10-26","url":"https://arxiv.org/abs/2610.35835","type":"research-paper","category":"safety-security","status":"research","summary":"arXiv 2610.35835, submitted 2026-10-26 and revised 2026-10-30 (v3). The abstract says an experiment on a popular agentic wallet platform required an emailed one-time passcode to raise a spending cap. With access to that email and a task blocked by the cap, ten frontier models often harvested the passcode and raised the cap. It says an I-HITL protocol requires a trusted computing device, and presents Countersign, a prototype that uses off-the-shelf consumer mobile devices. The abstract does not name the wallet vendor. GitHub repository https://github.com/I-HITL/countersign describes itself as a mobile phone-based implementation and is MIT licensed. The CoinDesk URL in the candidate file returned HTTP 429 on 2026-11-03 and was not read.","tags":["security","research","agent-wallets"],"verified_at":"2026-11-03","featured":false,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
|
| 159 |
{"id":"v12-x402-25-vulnerabilities","title":"25 Vulnerabilities in the x402 Protocol: Inside Three Critical Findings","publisher":"V12","authors":[],"date_published":"2026-10-22","url":"https://v12.sh/blog/x402","type":"report","category":"safety-security","status":"research","summary":"V12 reports 25 vulnerabilities in the x402 codebase and details three critical ones: a Solana token approval accepted as payment by the TypeScript facilitator, SIWx login messages signed for a different site, and a default client with no spending limit. All three were reported on 2026-08-12 and fixed by 2026-08-20. According to The Hacker News (2026-10-23), the fixes are in @x402/fetch, @x402/axios, @x402/extensions and @x402/svm 2.23.0 or later, patched clients cap each payment at $1 and accept only recognized stablecoins by default (spendControls: false disables this), and no formal security advisory was published. Related: https://thehackernews.com/2026/10/critical-x402-sdk-flaw-could-let.html.","tags":["x402","security","vulnerabilities","spend-controls","siwx","solana","sdk"],"verified_at":"2026-10-24","featured":false,"last_checked":"2026-10-24","http_status":200,"archive_url":null}
|
| 160 |
{"id":"cloudflare-verified-bots-continuous-accountability","title":"Continuous accountability for Verified bots","publisher":"Cloudflare","authors":[],"date_published":"2026-10-16","url":"https://blog.cloudflare.com/verified-bots-accountability/","type":"announcement","category":"safety-security","status":"news","summary":"Cloudflare describes a system that keeps evaluating Verified bots after they have identified themselves (for example via Web Bot Auth request signatures). It measures whether a bot honors robots.txt and responds to direct feedback, and turns this into an explainable trust band. Cloudflare says it plans to publish these scores on Radar.","tags":["identity","web-agents","security","http"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
| 161 |
{"id":"arxiv-approve-what-exactly-agent-step-up-authorization","title":"Approve What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up Authorization","publisher":"arXiv","authors":["Sai Varun Kodathala","Prashanth Pollishetty","Jaylen Cargill"],"date_published":"2026-10-15","url":"https://arxiv.org/abs/2610.21063","type":"research-paper","category":"safety-security","status":"research","summary":"The paper defines twelve attacks on the human-approval path of agent actions (such as decoy recipients, amount cancellation and threshold splitting) and runs them against AP2, Microsoft's action-bound approval design and MCP elicitation. An audit of ten agent runtimes finds no third-party verifiable approval record. The authors propose ASU, a gateway that renders the approval card from a canonical effect descriptor and has a user passkey sign its digest, and they verify it formally with Tamarin.","tags":["security","ap2","mcp","identity","research"],"verified_at":"2026-10-21","featured":false,"last_checked":"2026-10-21","http_status":200,"archive_url":null}
|
data/tags.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
-
"generated_at": "2026-
|
| 4 |
"count": 70,
|
| 5 |
"tags": [
|
| 6 |
{
|
|
@@ -20,7 +20,7 @@
|
|
| 20 |
},
|
| 21 |
{
|
| 22 |
"tag": "agent-wallets",
|
| 23 |
-
"count":
|
| 24 |
"json_url": "https://agentpaywire.com/api/library/tag/agent-wallets.json"
|
| 25 |
},
|
| 26 |
{
|
|
@@ -150,7 +150,7 @@
|
|
| 150 |
},
|
| 151 |
{
|
| 152 |
"tag": "lightning",
|
| 153 |
-
"count":
|
| 154 |
"json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
|
| 155 |
},
|
| 156 |
{
|
|
@@ -255,7 +255,7 @@
|
|
| 255 |
},
|
| 256 |
{
|
| 257 |
"tag": "research",
|
| 258 |
-
"count":
|
| 259 |
"json_url": "https://agentpaywire.com/api/library/tag/research.json"
|
| 260 |
},
|
| 261 |
{
|
|
@@ -275,7 +275,7 @@
|
|
| 275 |
},
|
| 276 |
{
|
| 277 |
"tag": "security",
|
| 278 |
-
"count":
|
| 279 |
"json_url": "https://agentpaywire.com/api/library/tag/security.json"
|
| 280 |
},
|
| 281 |
{
|
|
@@ -300,12 +300,12 @@
|
|
| 300 |
},
|
| 301 |
{
|
| 302 |
"tag": "stablecoins",
|
| 303 |
-
"count":
|
| 304 |
"json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
|
| 305 |
},
|
| 306 |
{
|
| 307 |
"tag": "standards",
|
| 308 |
-
"count":
|
| 309 |
"json_url": "https://agentpaywire.com/api/library/tag/standards.json"
|
| 310 |
},
|
| 311 |
{
|
|
@@ -350,7 +350,7 @@
|
|
| 350 |
},
|
| 351 |
{
|
| 352 |
"tag": "x402",
|
| 353 |
-
"count":
|
| 354 |
"json_url": "https://agentpaywire.com/api/library/tag/x402.json"
|
| 355 |
}
|
| 356 |
]
|
|
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
+
"generated_at": "2026-11-03T00:00:00Z",
|
| 4 |
"count": 70,
|
| 5 |
"tags": [
|
| 6 |
{
|
|
|
|
| 20 |
},
|
| 21 |
{
|
| 22 |
"tag": "agent-wallets",
|
| 23 |
+
"count": 22,
|
| 24 |
"json_url": "https://agentpaywire.com/api/library/tag/agent-wallets.json"
|
| 25 |
},
|
| 26 |
{
|
|
|
|
| 150 |
},
|
| 151 |
{
|
| 152 |
"tag": "lightning",
|
| 153 |
+
"count": 43,
|
| 154 |
"json_url": "https://agentpaywire.com/api/library/tag/lightning.json"
|
| 155 |
},
|
| 156 |
{
|
|
|
|
| 255 |
},
|
| 256 |
{
|
| 257 |
"tag": "research",
|
| 258 |
+
"count": 22,
|
| 259 |
"json_url": "https://agentpaywire.com/api/library/tag/research.json"
|
| 260 |
},
|
| 261 |
{
|
|
|
|
| 275 |
},
|
| 276 |
{
|
| 277 |
"tag": "security",
|
| 278 |
+
"count": 32,
|
| 279 |
"json_url": "https://agentpaywire.com/api/library/tag/security.json"
|
| 280 |
},
|
| 281 |
{
|
|
|
|
| 300 |
},
|
| 301 |
{
|
| 302 |
"tag": "stablecoins",
|
| 303 |
+
"count": 28,
|
| 304 |
"json_url": "https://agentpaywire.com/api/library/tag/stablecoins.json"
|
| 305 |
},
|
| 306 |
{
|
| 307 |
"tag": "standards",
|
| 308 |
+
"count": 29,
|
| 309 |
"json_url": "https://agentpaywire.com/api/library/tag/standards.json"
|
| 310 |
},
|
| 311 |
{
|
|
|
|
| 350 |
},
|
| 351 |
{
|
| 352 |
"tag": "x402",
|
| 353 |
+
"count": 33,
|
| 354 |
"json_url": "https://agentpaywire.com/api/library/tag/x402.json"
|
| 355 |
}
|
| 356 |
]
|