From c5ade36b5f34e4a73d3cf844788bfb257198cf94 Mon Sep 17 00:00:00 2001 From: Aion Date: Mon, 22 Jun 2026 20:07:07 +0200 Subject: [PATCH 1/2] docs: add LunarCrush manual retry policy --- lunarcrush/AGENT.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/lunarcrush/AGENT.md b/lunarcrush/AGENT.md index d6bc32e..9e9ced5 100644 --- a/lunarcrush/AGENT.md +++ b/lunarcrush/AGENT.md @@ -50,6 +50,12 @@ Before calling `score`: | `400 invalid_symbol` | Did not consume payment. Symbol must be lowercase a-z + 0-9 only, max 16 chars. Check input. | | `5xx` from worker | Worker outage. Retry once after 30s. If persists, alert operator. | +## Manual retry policy + +If you receive a `200` response with `galaxy_score: null` and believe the call consumed payment against an upstream failure, open a GitHub issue or mention the skill maintainer on the existing LunarCrush payment-vs-delivery thread with the payment txid and symbol queried. + +The maintainer can verify the on-chain payment, cross-check the server-side failure log, and honor a manual re-serve of the data. One retry per txid; caller-surfaced proof is required. This policy holds until an automated retry-with-proof endpoint ships. + ## Safety checks - **No private key handling.** This skill never logs, prints, or transmits the wallet seed phrase. All signing happens via `getAccount()` returning a properly-scoped account object. From fdd3de79493579c69934b2c278b140cd5eb906c8 Mon Sep 17 00:00:00 2001 From: Aion Date: Mon, 22 Jun 2026 20:13:52 +0200 Subject: [PATCH 2/2] docs: clarify LunarCrush retry escalation --- lunarcrush/AGENT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lunarcrush/AGENT.md b/lunarcrush/AGENT.md index 9e9ced5..86b96b8 100644 --- a/lunarcrush/AGENT.md +++ b/lunarcrush/AGENT.md @@ -52,7 +52,7 @@ Before calling `score`: ## Manual retry policy -If you receive a `200` response with `galaxy_score: null` and believe the call consumed payment against an upstream failure, open a GitHub issue or mention the skill maintainer on the existing LunarCrush payment-vs-delivery thread with the payment txid and symbol queried. +If a paid call returns `200` with `galaxy_score: null`, open a GitHub issue referencing the LunarCrush payment-vs-delivery thread with the payment txid and symbol queried. The maintainer can verify the on-chain payment, cross-check the server-side failure log, and honor a manual re-serve of the data. One retry per txid; caller-surfaced proof is required. This policy holds until an automated retry-with-proof endpoint ships.