Sync library snapshot 2026-11-06 (174 entries; Alby Hub v1.24.6, x402 Python SDK 2.27.0, protocol-facts Solana transactionVersions)
Browse files- README.md +8 -8
- data/library.json +48 -27
- data/protocol-facts.json +6 -1
- data/sources.csv +2 -1
- data/sources.jsonl +2 -1
- data/tags.json +3 -3
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-11-
|
| 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,7 +44,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
|
|
| 44 |
| category | entries |
|
| 45 |
| --- | --- |
|
| 46 |
| bitcoin-lightning (featured) | 40 |
|
| 47 |
-
| payments |
|
| 48 |
| agent-protocols | 33 |
|
| 49 |
| robotics-autonomy | 4 |
|
| 50 |
| iot | 4 |
|
|
@@ -54,7 +54,7 @@ Linked pages, papers, repositories and specifications are **not** included and b
|
|
| 54 |
|
| 55 |
## Fields (`data/sources.jsonl`)
|
| 56 |
|
| 57 |
-
One JSON object per line,
|
| 58 |
|
| 59 |
| field | type | description |
|
| 60 |
| --- | --- | --- |
|
|
@@ -62,7 +62,7 @@ One JSON object per line, 173 rows, single `train` split. Dates are `YYYY-MM-DD`
|
|
| 62 |
| `title` | string | Source title, copied from the page. |
|
| 63 |
| `publisher` | string | Publisher name. |
|
| 64 |
| `authors` | list of strings | People named on the source; empty list when none are named. |
|
| 65 |
-
| `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (78 of
|
| 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. |
|
|
@@ -79,9 +79,9 @@ One JSON object per line, 173 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 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
|
|
|
|
| 26 |
|
| 27 |
# Agent Paywire Knowledge Library
|
| 28 |
|
| 29 |
+
A curated library of **174 verified sources** about how AI agents pay and get paid: machine-to-machine payment protocols (L402, x402 and others), Bitcoin and Lightning, stablecoins, agent protocols (e.g. MCP), and the surrounding security, IoT, robotics and regulation context. Each row is one source: a link to the original publication plus metadata and a short, neutral summary written for this library.
|
| 30 |
|
| 31 |
This is the Hugging Face copy of the `agentpaywire-library` dataset published by [Agent Paywire](https://agentpaywire.com), a machine-readable reference site for AI agents on agent payments.
|
| 32 |
|
|
|
|
| 36 |
|
| 37 |
- Built from the live site: https://agentpaywire.com/library (dataset card on the site: https://agentpaywire.com/datasets/agentpaywire-library/).
|
| 38 |
- `data/sources.jsonl` is byte-identical to https://agentpaywire.com/dataset/library.jsonl (and https://agentpaywire.com/library.jsonl) at the time of this snapshot.
|
| 39 |
+
- Snapshot taken 2026-11-06 (last updated 2026-11-06). `verified_at` dates: 2026-10-20 (111 rows), 2026-10-21 (9 rows), 2026-10-22 (15 rows), 2026-10-23 (6 rows), 2026-10-24 (5 rows), 2026-10-25 (2 rows), 2026-10-26 (2 rows), 2026-10-27 (1 row), 2026-10-28 (1 row), 2026-10-31 (7 rows), 2026-11-03 (7 rows), 2026-11-04 (2 rows), 2026-11-05 (4 rows), 2026-11-06 (2 rows); the library files (`library.json`, `tags.json`) report `generated_at` 2026-11-06T00:00:00Z.
|
| 40 |
- The site is rebuilt when entries are published (on publish). This Hugging Face copy is a snapshot; the live site is authoritative and may be newer. For incremental sync use https://agentpaywire.com/changelog.json (filter by `verified_at`).
|
| 41 |
|
| 42 |
### Categories (snapshot)
|
|
|
|
| 44 |
| category | entries |
|
| 45 |
| --- | --- |
|
| 46 |
| bitcoin-lightning (featured) | 40 |
|
| 47 |
+
| payments | 71 |
|
| 48 |
| agent-protocols | 33 |
|
| 49 |
| robotics-autonomy | 4 |
|
| 50 |
| iot | 4 |
|
|
|
|
| 54 |
|
| 55 |
## Fields (`data/sources.jsonl`)
|
| 56 |
|
| 57 |
+
One JSON object per line, 174 rows, single `train` split. Dates are `YYYY-MM-DD` strings in the file; the `datasets` JSON loader infers `date_published`, `verified_at` and `last_checked` as timestamps. JSON Schema: https://agentpaywire.com/schemas/library.schema.json (copy in `data/library.schema.json`).
|
| 58 |
|
| 59 |
| field | type | description |
|
| 60 |
| --- | --- | --- |
|
|
|
|
| 62 |
| `title` | string | Source title, copied from the page. |
|
| 63 |
| `publisher` | string | Publisher name. |
|
| 64 |
| `authors` | list of strings | People named on the source; empty list when none are named. |
|
| 65 |
+
| `date_published` | string or null | `YYYY-MM-DD`; null when the source shows no publication date (78 of 174 rows). |
|
| 66 |
| `url` | string | Canonical URL of the source. |
|
| 67 |
| `type` | string | One of `announcement`, `directory`, `docs`, `regulatory`, `repo`, `report`, `research-paper`, `spec`. |
|
| 68 |
| `category` | string | One of the categories above. |
|
|
|
|
| 79 |
|
| 80 |
| file | contents |
|
| 81 |
| --- | --- |
|
| 82 |
+
| `data/sources.jsonl` | Main table (default config). 174 rows. |
|
| 83 |
+
| `data/sources.csv` | Same 174 rows as CSV (lists joined with `; `). Copy of https://agentpaywire.com/dataset/library.csv. |
|
| 84 |
+
| `data/library.json` | Full library document with category list (8 categories) and 174 entries. From https://agentpaywire.com/api/library.json. |
|
| 85 |
| `data/library.schema.json` | JSON Schema for the library documents. |
|
| 86 |
| `data/tags.json` | Tag index, 70 tags with counts. From https://agentpaywire.com/api/library/tags.json. |
|
| 87 |
| `data/protocol-facts.json` | Checked facts for 11 protocols (L402, BOLT 12, BIP 21, NWC, x402, MPP, AP2, ACP, UCP, MCP, A2A). From https://agentpaywire.com/api/protocol-facts.json. |
|
data/library.json
CHANGED
|
@@ -1,13 +1,13 @@
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
-
"generated_at": "2026-11-
|
| 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/"
|
|
@@ -83,6 +83,30 @@
|
|
| 83 |
}
|
| 84 |
],
|
| 85 |
"entries": [
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 86 |
{
|
| 87 |
"id": "aperture-v0-6-0-release",
|
| 88 |
"title": "Aperture v0.6.0",
|
|
@@ -394,30 +418,6 @@
|
|
| 394 |
"http_status": 200,
|
| 395 |
"archive_url": null
|
| 396 |
},
|
| 397 |
-
{
|
| 398 |
-
"id": "getalby-hub-v1-24-3-release",
|
| 399 |
-
"title": "Release v1.24.3 Julian Assange · getAlby/hub",
|
| 400 |
-
"publisher": "GitHub (Alby)",
|
| 401 |
-
"authors": [],
|
| 402 |
-
"date_published": "2026-10-16",
|
| 403 |
-
"url": "https://github.com/getAlby/hub/releases/tag/v1.24.3",
|
| 404 |
-
"type": "repo",
|
| 405 |
-
"category": "bitcoin-lightning",
|
| 406 |
-
"status": "product_docs",
|
| 407 |
-
"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.",
|
| 408 |
-
"tags": [
|
| 409 |
-
"lightning",
|
| 410 |
-
"nwc",
|
| 411 |
-
"agent-wallets",
|
| 412 |
-
"security",
|
| 413 |
-
"tools"
|
| 414 |
-
],
|
| 415 |
-
"verified_at": "2026-10-21",
|
| 416 |
-
"featured": true,
|
| 417 |
-
"last_checked": "2026-10-21",
|
| 418 |
-
"http_status": 200,
|
| 419 |
-
"archive_url": null
|
| 420 |
-
},
|
| 421 |
{
|
| 422 |
"id": "lightning-enable-l402-is-ready",
|
| 423 |
"title": "L402 Is Ready. The Missing Layer Is Adoption.",
|
|
@@ -1042,6 +1042,27 @@
|
|
| 1042 |
"http_status": 200,
|
| 1043 |
"archive_url": null
|
| 1044 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1045 |
{
|
| 1046 |
"id": "stripe-link-cli",
|
| 1047 |
"title": "stripe/link-cli",
|
|
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
+
"generated_at": "2026-11-06T00:00:00Z",
|
| 4 |
"disclaimer": {
|
| 5 |
"text": "Not investment advice.",
|
| 6 |
"url": "https://agentpaywire.com/disclaimer.json"
|
| 7 |
},
|
| 8 |
"$schema": "https://agentpaywire.com/schemas/library.schema.json",
|
| 9 |
"license": "links + original short summaries; content belongs to publishers",
|
| 10 |
+
"count": 174,
|
| 11 |
"categories": [
|
| 12 |
{
|
| 13 |
"id": "bitcoin-lightning",
|
|
|
|
| 22 |
"id": "payments",
|
| 23 |
"label": "Payments",
|
| 24 |
"featured": false,
|
| 25 |
+
"count": 71,
|
| 26 |
"json_url": "https://agentpaywire.com/api/library/payments.json",
|
| 27 |
"markdown_url": "https://agentpaywire.com/library/payments.md",
|
| 28 |
"html_url": "https://agentpaywire.com/library/payments/"
|
|
|
|
| 83 |
}
|
| 84 |
],
|
| 85 |
"entries": [
|
| 86 |
+
{
|
| 87 |
+
"id": "getalby-hub-v1-24-6-release",
|
| 88 |
+
"title": "Release v1.24.6 Julian Assange · getAlby/hub",
|
| 89 |
+
"publisher": "GitHub (Alby)",
|
| 90 |
+
"authors": [],
|
| 91 |
+
"date_published": "2026-11-05",
|
| 92 |
+
"url": "https://github.com/getAlby/hub/releases/tag/v1.24.6",
|
| 93 |
+
"type": "repo",
|
| 94 |
+
"category": "bitcoin-lightning",
|
| 95 |
+
"status": "product_docs",
|
| 96 |
+
"summary": "Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.",
|
| 97 |
+
"tags": [
|
| 98 |
+
"lightning",
|
| 99 |
+
"nwc",
|
| 100 |
+
"agent-wallets",
|
| 101 |
+
"security",
|
| 102 |
+
"tools"
|
| 103 |
+
],
|
| 104 |
+
"verified_at": "2026-11-06",
|
| 105 |
+
"featured": true,
|
| 106 |
+
"last_checked": "2026-11-06",
|
| 107 |
+
"http_status": 200,
|
| 108 |
+
"archive_url": null
|
| 109 |
+
},
|
| 110 |
{
|
| 111 |
"id": "aperture-v0-6-0-release",
|
| 112 |
"title": "Aperture v0.6.0",
|
|
|
|
| 418 |
"http_status": 200,
|
| 419 |
"archive_url": null
|
| 420 |
},
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 421 |
{
|
| 422 |
"id": "lightning-enable-l402-is-ready",
|
| 423 |
"title": "L402 Is Ready. The Missing Layer Is Adoption.",
|
|
|
|
| 1042 |
"http_status": 200,
|
| 1043 |
"archive_url": null
|
| 1044 |
},
|
| 1045 |
+
{
|
| 1046 |
+
"id": "x402-python-sdk-2-27-0",
|
| 1047 |
+
"title": "x402 Python SDK 2.27.0",
|
| 1048 |
+
"publisher": "x402 Foundation",
|
| 1049 |
+
"authors": [],
|
| 1050 |
+
"date_published": "2026-11-04",
|
| 1051 |
+
"url": "https://pypi.org/project/x402/2.27.0/",
|
| 1052 |
+
"type": "repo",
|
| 1053 |
+
"category": "payments",
|
| 1054 |
+
"status": "product_docs",
|
| 1055 |
+
"summary": "Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).",
|
| 1056 |
+
"tags": [
|
| 1057 |
+
"x402",
|
| 1058 |
+
"sdk"
|
| 1059 |
+
],
|
| 1060 |
+
"verified_at": "2026-11-06",
|
| 1061 |
+
"featured": false,
|
| 1062 |
+
"last_checked": "2026-11-06",
|
| 1063 |
+
"http_status": 200,
|
| 1064 |
+
"archive_url": null
|
| 1065 |
+
},
|
| 1066 |
{
|
| 1067 |
"id": "stripe-link-cli",
|
| 1068 |
"title": "stripe/link-cli",
|
data/protocol-facts.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
-
"generated_at": "2026-11-
|
| 4 |
"disclaimer": {
|
| 5 |
"text": "Not investment advice.",
|
| 6 |
"url": "https://agentpaywire.com/disclaimer.json"
|
|
@@ -415,6 +415,11 @@
|
|
| 415 |
],
|
| 416 |
"source": "https://github.com/x402-foundation/x402/tree/main/specs/schemes",
|
| 417 |
"verified_at": "2026-11-03"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 418 |
}
|
| 419 |
},
|
| 420 |
{
|
|
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
+
"generated_at": "2026-11-06T00:00:00Z",
|
| 4 |
"disclaimer": {
|
| 5 |
"text": "Not investment advice.",
|
| 6 |
"url": "https://agentpaywire.com/disclaimer.json"
|
|
|
|
| 415 |
],
|
| 416 |
"source": "https://github.com/x402-foundation/x402/tree/main/specs/schemes",
|
| 417 |
"verified_at": "2026-11-03"
|
| 418 |
+
},
|
| 419 |
+
"implementation": {
|
| 420 |
+
"value": "Python SDK 2.27.0, changelog heading 2026-11-04, says its SVM exact facilitators advertise and accept extra.transactionVersions [0, 1] by default. Clients build the highest version shared with the facilitator. Passing transaction_versions=[0] keeps that SDK on version 0. This is the Python SDK implementation. The exact scheme notes above do not say every binding must advertise transactionVersions.",
|
| 421 |
+
"source": "https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md",
|
| 422 |
+
"verified_at": "2026-11-06"
|
| 423 |
}
|
| 424 |
},
|
| 425 |
{
|
data/sources.csv
CHANGED
|
@@ -1,4 +1,5 @@
|
|
| 1 |
id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
|
|
|
|
| 2 |
aperture-v0-6-0-release,Aperture v0.6.0,Lightning Labs,,2026-11-05,https://github.com/lightninglabs/aperture/releases/tag/v0.6.0,repo,bitcoin-lightning,product_docs,"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",l402; lightning; m2m-payments; release,2026-11-05,true,2026-11-05,200,
|
| 3 |
core-lightning-v26-06-10,Core Lightning v26.06.10,Elements Project,,2026-11-04,https://github.com/ElementsProject/lightning/releases/tag/v26.06.10,repo,bitcoin-lightning,product_docs,"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",lightning; release; security,2026-11-05,true,2026-11-05,200,
|
| 4 |
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,
|
|
@@ -12,7 +13,6 @@ lightning-labs-wavelength-mainnet,Ride the Wave: Integrate Bitcoin Payments with
|
|
| 12 |
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,
|
| 13 |
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,
|
| 14 |
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,
|
| 15 |
-
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,
|
| 16 |
lightning-enable-l402-is-ready,L402 Is Ready. The Missing Layer Is Adoption.,Lightning Enable,Michael Rahel,2026-10-15,https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption,announcement,bitcoin-lightning,news,"Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.",l402; lightning; macaroons; m2m-payments,2026-10-22,true,2026-10-22,200,
|
| 17 |
lightning-labs-l402-for-agents,The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents,Lightning Labs,Michael Levin,2026-03-11,https://lightning.engineering/posts/2026-03-11-L402-for-agents/,announcement,bitcoin-lightning,news,"Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.",l402; lightning; bitcoin; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260703094933/https://lightning.engineering/posts/2026-03-11-L402-for-agents/
|
| 18 |
lightning-labs-agent-tools-launch,The Agents Are Here and They Want to Transact: Powering the AI Economy with Lightning,Lightning Labs,Michael Levin,2026-02-11,https://lightning.engineering/posts/2026-02-11-ln-agent-tools/,announcement,bitcoin-lightning,news,"Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.",lightning; l402; agent-wallets; mcp; bitcoin,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/
|
|
@@ -39,6 +39,7 @@ l402-org,"L402: native payments for MCP, AI agents, APIs and data",l402.org,,,ht
|
|
| 39 |
nostr-nip-90-data-vending-machine,NIP-90: Data Vending Machine,GitHub (nostr-protocol/nips),,,https://github.com/nostr-protocol/nips/blob/master/90.md,spec,bitcoin-lightning,spec_released,"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",nostr; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md
|
| 40 |
l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
|
| 41 |
voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
|
|
|
|
| 42 |
stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
|
| 43 |
stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
|
| 44 |
singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
|
|
|
|
| 1 |
id,title,publisher,authors,date_published,url,type,category,status,summary,tags,verified_at,featured,last_checked,http_status,archive_url
|
| 2 |
+
getalby-hub-v1-24-6-release,Release v1.24.6 Julian Assange · getAlby/hub,GitHub (Alby),,2026-11-05,https://github.com/getAlby/hub/releases/tag/v1.24.6,repo,bitcoin-lightning,product_docs,"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.",lightning; nwc; agent-wallets; security; tools,2026-11-06,true,2026-11-06,200,
|
| 3 |
aperture-v0-6-0-release,Aperture v0.6.0,Lightning Labs,,2026-11-05,https://github.com/lightninglabs/aperture/releases/tag/v0.6.0,repo,bitcoin-lightning,product_docs,"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.",l402; lightning; m2m-payments; release,2026-11-05,true,2026-11-05,200,
|
| 4 |
core-lightning-v26-06-10,Core Lightning v26.06.10,Elements Project,,2026-11-04,https://github.com/ElementsProject/lightning/releases/tag/v26.06.10,repo,bitcoin-lightning,product_docs,"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.",lightning; release; security,2026-11-05,true,2026-11-05,200,
|
| 5 |
wavelength-v0-2-1-release,Wavelength v0.2.1,Lightning Labs (GitHub),,2026-10-31,https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1,repo,bitcoin-lightning,spec_released,"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.",lightning; ark; wallet; release,2026-11-03,true,2026-11-03,200,
|
|
|
|
| 13 |
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,
|
| 14 |
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,
|
| 15 |
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,
|
|
|
|
| 16 |
lightning-enable-l402-is-ready,L402 Is Ready. The Missing Layer Is Adoption.,Lightning Enable,Michael Rahel,2026-10-15,https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption,announcement,bitcoin-lightning,news,"Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.",l402; lightning; macaroons; m2m-payments,2026-10-22,true,2026-10-22,200,
|
| 17 |
lightning-labs-l402-for-agents,The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents,Lightning Labs,Michael Levin,2026-03-11,https://lightning.engineering/posts/2026-03-11-L402-for-agents/,announcement,bitcoin-lightning,news,"Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.",l402; lightning; bitcoin; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260703094933/https://lightning.engineering/posts/2026-03-11-L402-for-agents/
|
| 18 |
lightning-labs-agent-tools-launch,The Agents Are Here and They Want to Transact: Powering the AI Economy with Lightning,Lightning Labs,Michael Levin,2026-02-11,https://lightning.engineering/posts/2026-02-11-ln-agent-tools/,announcement,bitcoin-lightning,news,"Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.",lightning; l402; agent-wallets; mcp; bitcoin,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/
|
|
|
|
| 39 |
nostr-nip-90-data-vending-machine,NIP-90: Data Vending Machine,GitHub (nostr-protocol/nips),,,https://github.com/nostr-protocol/nips/blob/master/90.md,spec,bitcoin-lightning,spec_released,"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.",nostr; lightning; m2m-payments; micropayments,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md
|
| 40 |
l402apps-com,L402 Apps,L402 Apps,,,https://www.l402apps.com/,directory,bitcoin-lightning,product_docs,Directory of apps and APIs presented as reachable through L402 payment gateways.,l402; lightning; directory,2026-10-20,true,2026-10-20,200,http://web.archive.org/web/20260615114727/https://www.l402apps.com/
|
| 41 |
voltage-cli,Voltage CLI,Voltage,,,https://github.com/voltagecloud/voltage-cli,repo,bitcoin-lightning,product_docs,"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.",lightning; bitcoin; tools; agent-wallets,2026-10-23,,2026-10-23,200,
|
| 42 |
+
x402-python-sdk-2-27-0,x402 Python SDK 2.27.0,x402 Foundation,,2026-11-04,https://pypi.org/project/x402/2.27.0/,repo,payments,product_docs,"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).",x402; sdk,2026-11-06,,2026-11-06,200,
|
| 43 |
stripe-link-cli,stripe/link-cli,Stripe (GitHub),,2026-10-29,https://github.com/stripe/link-cli,repo,payments,product_docs,"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.",agent-wallets; mcp; tools,2026-10-31,,2026-10-31,200,
|
| 44 |
stripe-treasury-for-agents,Introducing Stripe Treasury for agents,Stripe,,2026-10-21,https://stripe.com/newsroom/news/treasury-for-agents,announcement,payments,news,"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.",agent-wallets; mcp; tools,2026-10-22,,2026-10-22,200,
|
| 45 |
singularity-layer-training-lab-x402,"Training Lab, now over x402",Singularity Layer,,2026-10-21,https://www.x402layer.cc/blog/training-lab-x402,announcement,payments,news,"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.",x402; stablecoins; micropayments; tools,2026-10-22,,2026-10-22,200,
|
data/sources.jsonl
CHANGED
|
@@ -1,3 +1,4 @@
|
|
|
|
|
| 1 |
{"id":"aperture-v0-6-0-release","title":"Aperture v0.6.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-11-05","url":"https://github.com/lightninglabs/aperture/releases/tag/v0.6.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.","tags":["l402","lightning","m2m-payments","release"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
|
| 2 |
{"id":"core-lightning-v26-06-10","title":"Core Lightning v26.06.10","publisher":"Elements Project","authors":[],"date_published":"2026-11-04","url":"https://github.com/ElementsProject/lightning/releases/tag/v26.06.10","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.","tags":["lightning","release","security"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
|
| 3 |
{"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}
|
|
@@ -11,7 +12,6 @@
|
|
| 11 |
{"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}
|
| 12 |
{"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}
|
| 13 |
{"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}
|
| 14 |
-
{"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}
|
| 15 |
{"id":"lightning-enable-l402-is-ready","title":"L402 Is Ready. The Missing Layer Is Adoption.","publisher":"Lightning Enable","authors":["Michael Rahel"],"date_published":"2026-10-15","url":"https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.","tags":["l402","lightning","macaroons","m2m-payments"],"verified_at":"2026-10-22","featured":true,"last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 16 |
{"id":"lightning-labs-l402-for-agents","title":"The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents","publisher":"Lightning Labs","authors":["Michael Levin"],"date_published":"2026-03-11","url":"https://lightning.engineering/posts/2026-03-11-L402-for-agents/","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.","tags":["l402","lightning","bitcoin","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260703094933/https://lightning.engineering/posts/2026-03-11-L402-for-agents/"}
|
| 17 |
{"id":"lightning-labs-agent-tools-launch","title":"The Agents Are Here and They Want to Transact: Powering the AI Economy with Lightning","publisher":"Lightning Labs","authors":["Michael Levin"],"date_published":"2026-02-11","url":"https://lightning.engineering/posts/2026-02-11-ln-agent-tools/","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.","tags":["lightning","l402","agent-wallets","mcp","bitcoin"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/"}
|
|
@@ -38,6 +38,7 @@
|
|
| 38 |
{"id":"nostr-nip-90-data-vending-machine","title":"NIP-90: Data Vending Machine","publisher":"GitHub (nostr-protocol/nips)","authors":[],"date_published":null,"url":"https://github.com/nostr-protocol/nips/blob/master/90.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.","tags":["nostr","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md"}
|
| 39 |
{"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
|
| 40 |
{"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
|
|
|
|
| 41 |
{"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
|
| 42 |
{"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 43 |
{"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
|
|
|
| 1 |
+
{"id":"getalby-hub-v1-24-6-release","title":"Release v1.24.6 Julian Assange · getAlby/hub","publisher":"GitHub (Alby)","authors":[],"date_published":"2026-11-05","url":"https://github.com/getAlby/hub/releases/tag/v1.24.6","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Patch release published 2026-11-05T09:45:44Z, not a prerelease. The notes say it includes bug fixes and security updates, thank Project Loupe, the Bitcoin Red Team, and individual contributors for AI scans, and name no CVE. NWC create_connection errors include unsupported method names. Hub binaries disable MPTCP by default. App pubkeys that are not valid curve keys are rejected. Bundled lnd is v0.21.6-beta. This replaces the v1.24.3 row. Full changelog: https://github.com/getAlby/hub/compare/v1.24.4...v1.24.6.","tags":["lightning","nwc","agent-wallets","security","tools"],"verified_at":"2026-11-06","featured":true,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
|
| 2 |
{"id":"aperture-v0-6-0-release","title":"Aperture v0.6.0","publisher":"Lightning Labs","authors":[],"date_published":"2026-11-05","url":"https://github.com/lightninglabs/aperture/releases/tag/v0.6.0","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Release published 2026-11-05, not a prerelease. Metered pricing is opt-in per service (metered: true). A price server is called at GetPrice, ChallengeMinted, AuthorizeRequest, and ReportUsage. The release includes meterd, a reference price server, and the pricesrpc interface. docs/metering.md at tag v0.6.0 names the same four calls. The release says invoices can be minted from a Wavelength wallet instead of lnd, so a seller needs no node of their own. docs/wavelength.md at that tag describes invoices from a Wavelength wallet and also says the Wavelength backend is not in an Aperture release yet. A service with auth: l402+mpp answers an unpaid request with one 402 that carries both an L402 and a Payment challenge. Hardening includes a Payment-Receipt only for a credential that authenticated the request, TLS 1.2 or newer, and path canonicalization before authorization. The Upgrading section lists changes that can break an existing deployment. enablempp is refused at startup with the etcd backend; sqlite or postgres is required. A static price of 0 means the default price of 1 sat, not free. This replaces the lightninglabs-aperture-github row. Metering: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/metering.md. Wavelength: https://github.com/lightninglabs/aperture/blob/v0.6.0/docs/wavelength.md.","tags":["l402","lightning","m2m-payments","release"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
|
| 3 |
{"id":"core-lightning-v26-06-10","title":"Core Lightning v26.06.10","publisher":"Elements Project","authors":[],"date_published":"2026-11-04","url":"https://github.com/ElementsProject/lightning/releases/tag/v26.06.10","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Security point release published 2026-11-04T13:34:33Z, not a prerelease. The notes say it includes fixes for vulnerabilities and that the maintainers strongly recommend upgrading. The highlighted security fixes cover dual funding and splicing, including signature checks on the peer's tx_signatures, onchaind HTLC resolution, gossip resource limits, connectd, runes and commando, plugin hooks and hsmd. A peer dust_limit_satoshis above 5000 sat is refused. The notes recommend binding commando runes to a node id with an id restriction, and rotating unaccounted runes by blacklisting them and issuing new ones. The notes name no CVE. The changelog heading linked from the release is dated 2026-11-05. The release notes do not name Blockstream.","tags":["lightning","release","security"],"verified_at":"2026-11-05","featured":true,"last_checked":"2026-11-05","http_status":200,"archive_url":null}
|
| 4 |
{"id":"wavelength-v0-2-1-release","title":"Wavelength v0.2.1","publisher":"Lightning Labs (GitHub)","authors":[],"date_published":"2026-10-31","url":"https://github.com/lightninglabs/wavelength/releases/tag/v0.2.1","type":"repo","category":"bitcoin-lightning","status":"spec_released","summary":"Release published 2026-10-31, not a prerelease. The notes say changes are since v0.2.0. Clients validate Ark transaction inputs before accepting out-of-round transfers. Linux builds disable MPTCP listeners by default, and the notes say this does not replace installing a patched kernel. Received VTXO expiry timing is derived from locally confirmed chain evidence. Pay swaps reject excessive refund timelocks before funding, refund intent survives interruptions, and payments that would leave unusably small change fail promptly. Exit recovery preserves the spending policy and funding proofs. Binaries are built with Go 1.27.3. The release body says maintainers must sign manifest-v0.2.1.txt before publishing. Full changelog: https://github.com/lightninglabs/wavelength/compare/v0.2.0...v0.2.1.","tags":["lightning","ark","wallet","release"],"verified_at":"2026-11-03","featured":true,"last_checked":"2026-11-03","http_status":200,"archive_url":null}
|
|
|
|
| 12 |
{"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}
|
| 13 |
{"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}
|
| 14 |
{"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}
|
|
|
|
| 15 |
{"id":"lightning-enable-l402-is-ready","title":"L402 Is Ready. The Missing Layer Is Adoption.","publisher":"Lightning Enable","authors":["Michael Rahel"],"date_published":"2026-10-15","url":"https://docs.lightningenable.com/blog/l402-is-ready-the-missing-layer-is-adoption","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Michael Rahel writes that L402 is ready and that adoption is the missing layer. The post describes an HTTP 402 response carrying a Lightning invoice and a macaroon, then a retry that presents the token and the payment preimage.","tags":["l402","lightning","macaroons","m2m-payments"],"verified_at":"2026-10-22","featured":true,"last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 16 |
{"id":"lightning-labs-l402-for-agents","title":"The Future Is Now: Why L402 Is the Internet-Native Payments Protocol for Agents","publisher":"Lightning Labs","authors":["Michael Levin"],"date_published":"2026-03-11","url":"https://lightning.engineering/posts/2026-03-11-L402-for-agents/","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Lightning Labs post explaining how L402 puts HTTP 402 Payment Required to work by pairing it with the Lightning Network and cryptographic authentication tokens. Any Lightning-enabled client can pay for and authenticate with an L402 API instantly, with no signup, API key or prior relationship, and the post covers updates to the L402 bLIP specification.","tags":["l402","lightning","bitcoin","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260703094933/https://lightning.engineering/posts/2026-03-11-L402-for-agents/"}
|
| 17 |
{"id":"lightning-labs-agent-tools-launch","title":"The Agents Are Here and They Want to Transact: Powering the AI Economy with Lightning","publisher":"Lightning Labs","authors":["Michael Levin"],"date_published":"2026-02-11","url":"https://lightning.engineering/posts/2026-02-11-ln-agent-tools/","type":"announcement","category":"bitcoin-lightning","status":"news","summary":"Launch post for Lightning Agent Tools: seven composable open-source skills that let AI agents run Lightning nodes, pay L402-gated APIs, host paid endpoints and query nodes via MCP. It also introduces lnget, an L402-aware command-line HTTP client.","tags":["lightning","l402","agent-wallets","mcp","bitcoin"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260908091514/https://lightning.engineering/posts/2026-02-11-ln-agent-tools/"}
|
|
|
|
| 38 |
{"id":"nostr-nip-90-data-vending-machine","title":"NIP-90: Data Vending Machine","publisher":"GitHub (nostr-protocol/nips)","authors":[],"date_published":null,"url":"https://github.com/nostr-protocol/nips/blob/master/90.md","type":"spec","category":"bitcoin-lightning","status":"spec_released","summary":"Nostr spec for on-demand computation ('money in, data out'). Customers publish job requests (kinds 5000-5999), service providers return results (6000-6999) and feedback (7000), and payment is typically made over Lightning. The spec itself is marked draft and 'unrecommended'.","tags":["nostr","lightning","m2m-payments","micropayments"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20261007111747/https://github.com/nostr-protocol/nips/blob/master/90.md"}
|
| 39 |
{"id":"l402apps-com","title":"L402 Apps","publisher":"L402 Apps","authors":[],"date_published":null,"url":"https://www.l402apps.com/","type":"directory","category":"bitcoin-lightning","status":"product_docs","summary":"Directory of apps and APIs presented as reachable through L402 payment gateways.","tags":["l402","lightning","directory"],"verified_at":"2026-10-20","featured":true,"last_checked":"2026-10-20","http_status":200,"archive_url":"http://web.archive.org/web/20260615114727/https://www.l402apps.com/"}
|
| 40 |
{"id":"voltage-cli","title":"Voltage CLI","publisher":"Voltage","authors":[],"date_published":null,"url":"https://github.com/voltagecloud/voltage-cli","type":"repo","category":"bitcoin-lightning","status":"product_docs","summary":"Command-line client for the Voltage API. The README says it creates wallets and receives and sends Lightning payments, and on-chain payments where enabled, from a terminal, a script, or an AI agent. A change is only described until --execute is added. Every payment carries an ID, and the CLI never resubmits one on its own. Output is a table on a terminal and stable JSON when piped. License: MIT. Related: https://voltage.cloud/blog/prompt-to-payment-lightning-cli-agent-pack.","tags":["lightning","bitcoin","tools","agent-wallets"],"verified_at":"2026-10-23","featured":false,"last_checked":"2026-10-23","http_status":200,"archive_url":null}
|
| 41 |
+
{"id":"x402-python-sdk-2-27-0","title":"x402 Python SDK 2.27.0","publisher":"x402 Foundation","authors":[],"date_published":"2026-11-04","url":"https://pypi.org/project/x402/2.27.0/","type":"repo","category":"payments","status":"product_docs","summary":"Python package x402 2.27.0. PyPI lists the upload at 2026-11-04T20:03:25Z. The changelog heading is [2.27.0] - 2026-11-04. SVM exact payments in this SDK support Solana transaction version 1: facilitators advertise and accept extra.transactionVersions [0, 1] by default, and clients build the highest shared version. transaction_versions=[0] keeps a signer on version 0. The changelog describes this as the Python SDK, not as a requirement of every exact scheme. SIWX record_nonce runs after access is granted, and incomplete nonce-tracking is rejected. The upto Permit2 facilitator returns structured invalid_upto_evm_payload and invalid_upto_evm_required_amount errors. A throwing after_verify, after_settle, on_verify_failure, or on_settle_failure hook is logged and skipped; before_verify and before_settle still fail closed. x402[svm] requires solders>=0.29.0 and httpx and no longer installs solana. The GitHub releases API returned 404 for tag pypi-x402@v2.27.0 on 2026-11-06. Changelog: https://github.com/x402-foundation/x402/blob/main/python/x402/CHANGELOG.md. Related library entry: coinbase-x402-github (https://github.com/coinbase/x402).","tags":["x402","sdk"],"verified_at":"2026-11-06","featured":false,"last_checked":"2026-11-06","http_status":200,"archive_url":null}
|
| 42 |
{"id":"stripe-link-cli","title":"stripe/link-cli","publisher":"Stripe (GitHub)","authors":[],"date_published":"2026-10-29","url":"https://github.com/stripe/link-cli","type":"repo","category":"payments","status":"product_docs","summary":"MIT-licensed CLI. The README says it lets an agent get payment credentials for one-time purchases and recurring payments without storing the card, and that it can run as a local MCP server with command link-cli and args --mcp. It says this is available to US and Canadian Link accounts. GitHub published @stripe/link-cli 1.0.0 on 2026-10-29: generated MCP configs run the installed binary instead of npx, and balance eligibility is removed from user info. 1.0.1 on 2026-10-30 fixes MPP payments rejected after approval and adds --use-approval-policy to mpp pay. The README documents mpp pay for Machine Payments Protocol purchases. A Tempo customer story says Link balances are settled in stablecoins on Tempo and are rolling out to Instinct users in eligible US regions. It does not name USDC for that balance.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-31","featured":false,"last_checked":"2026-10-31","http_status":200,"archive_url":null}
|
| 43 |
{"id":"stripe-treasury-for-agents","title":"Introducing Stripe Treasury for agents","publisher":"Stripe","authors":[],"date_published":"2026-10-21","url":"https://stripe.com/newsroom/news/treasury-for-agents","type":"announcement","category":"payments","status":"news","summary":"Stripe announced Stripe Treasury for agents, which lets a startup use an agent to check balances, pay invoices, transfer funds, and convert currencies. The business chooses which accounts and data the agent can access, whether it can read or take action, and when money movement requires human approval; the page says creating cards is coming soon and spending limits follow in the coming weeks.","tags":["agent-wallets","mcp","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
| 44 |
{"id":"singularity-layer-training-lab-x402","title":"Training Lab, now over x402","publisher":"Singularity Layer","authors":[],"date_published":"2026-10-21","url":"https://www.x402layer.cc/blog/training-lab-x402","type":"announcement","category":"payments","status":"news","summary":"Singularity Layer's Training Lab post says an agent can request a training run, receive HTTP 402 with an exact price, and pay in USDC on Base or Solana or in USDG on Robinhood Chain. It states a limit of up to $500 per order and 3 paid runs per wallet per day over x402.","tags":["x402","stablecoins","micropayments","tools"],"verified_at":"2026-10-22","last_checked":"2026-10-22","http_status":200,"archive_url":null}
|
data/tags.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
{
|
| 2 |
"schema_version": "1",
|
| 3 |
-
"generated_at": "2026-11-
|
| 4 |
"count": 70,
|
| 5 |
"tags": [
|
| 6 |
{
|
|
@@ -270,7 +270,7 @@
|
|
| 270 |
},
|
| 271 |
{
|
| 272 |
"tag": "sdk",
|
| 273 |
-
"count":
|
| 274 |
"json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
|
| 275 |
},
|
| 276 |
{
|
|
@@ -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-06T00:00:00Z",
|
| 4 |
"count": 70,
|
| 5 |
"tags": [
|
| 6 |
{
|
|
|
|
| 270 |
},
|
| 271 |
{
|
| 272 |
"tag": "sdk",
|
| 273 |
+
"count": 4,
|
| 274 |
"json_url": "https://agentpaywire.com/api/library/tag/sdk.json"
|
| 275 |
},
|
| 276 |
{
|
|
|
|
| 350 |
},
|
| 351 |
{
|
| 352 |
"tag": "x402",
|
| 353 |
+
"count": 34,
|
| 354 |
"json_url": "https://agentpaywire.com/api/library/tag/x402.json"
|
| 355 |
}
|
| 356 |
]
|