Skip to content

docs: add LunarCrush manual retry policy #402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aionathenea-eng wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: add LunarCrush manual retry policy #402

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5ade36
docs: add LunarCrush manual retry policy
Jun 22, 2026
fdd3de7
docs: clarify LunarCrush retry escalation
Jun 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions lunarcrush/AGENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down