L402 edge cache for AI agents paying over Lightning
Bitcoin Stratigraphy MCP version 1.1.0 has been released as a remote-first integration repository that provides dependency-free clients and OpenAPI contracts for a hosted Bitcoin engine. The release offers a free sandbox environment for protocol discovery and two specific tool executions without requiring wallet credentials or API keys. Paid capabilities utilize L402 edge caching with macro-macaroons, allowing users to purchase batches of 100 calls via Lightning Network payments.
- ▪The release includes a free sandbox that allows users to run Node.js or Python clients to discover indexed dates and proof operations without signing or paying.
- ▪LlamaIndex execution is currently unavailable due to a security vulnerability in its NLTK dependency, while LangChain execution remains supported.
- ▪Paid tool executions require L402 authentication, where users request batch challenges and settle invoices through trusted Lightning wallets.
- ▪The registered cost for notarization is 250 sats per call, with a standard batch size of 100 calls totaling 25,000 sats.
- ▪The repository does not contain the complete settlement server and relies on connecting to a live hosted MCP endpoint or a compatible independent server.
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,603 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/CharlesStrogish/bitcoin-stratigraphy-mcp |
| Publication time | Mon, 05 Oct 2026 01:29:00 +0000 |
| Retrieval time | 2026-10-05T01:37:16.611Z |
| Last seen | 2026-10-05T01:37:16.611Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2GFXoIgwwiqr · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Bitcoin Stratigraphy MCP — Developer Distribution Release: 1.1.0 · MCP registry name: crstrogish/bitcoin-stratigraphy A standalone, remote-first integration repository for the Bitcoin Stratigraphy MCP engine: registry metadata, OpenAPI contracts, dependency-free clients, and native framework agent examples. No Replit workspace, wallet, API key, or model provider account is needed for the free sandbox. Scope and security status This bundle connects to the hosted engine; it does not contain or claim to run the complete settlement server offline. Client sources can be run locally against the live service or an independently operated compatible MCP endpoint. There are no workspace aliases, vendored credentials, private signing keys, operator state, or dependency on a parent repository.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.