lnurl-test

Validate LNURL server endpoints for LUD-16, LUD-06, and LUD-21 flows.

55|5|Updated Feb 1, 2024
One-click install
npx skills add https://github.com/MakePrisms/agicash --skill lnurl-test-makeprisms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lnurl-test
Source: https://github.com/MakePrisms/agicash/tree/main/.claude/skills/lnurl-test
Command: npx skills add https://github.com/MakePrisms/agicash --skill lnurl-test-makeprisms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightning Address integrations often expose multiple LNURL endpoints (LUD-16, LUD-06, LUD-21) that must be validated to prevent misrouting payments or failed invoices. This Skill provides an automated checks workflow to confirm endpoint contracts and response formats.

Core Features & Use Cases

  • Endpoint validation for LUD-16: verify the callback, minSendable, maxSendable, metadata, and tag fields.
  • Invoice flow testing for LUD-06: ensure the generated invoice, verify URL, and routes array behavior.
  • Payment verification for LUD-21: validate the final status against the invoice and ensure settlement signals.
  • Use Case: QA developers can run lnurl-test against local dev servers or production endpoints after making LNURL route changes to ensure compatibility.

Quick Start

Run the lnurl-test with a username and optional base URL to validate LNURL endpoints against LUD-16, LUD-06, and LUD-21.

Frequently Asked Questions about lnurl-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate LNURL endpoints for Lightning Address?

You can validate LNURL endpoints by providing a base URL and username to test LUD-16, LUD-06, and LUD-21 flows. This enforces endpoint structure, required fields, and JSON response formats to prevent misrouting payments or failed invoices.

What is the difference between LUD-16, LUD-06, and LUD-21 LNURL flows?

LUD-16 verifies callback and sendable limits, LUD-06 tests the generated invoice and routes array behavior, and LUD-21 validates final payment settlement signals. Each LNURL flow enforces distinct endpoint contracts and JSON response formats.

How do I test Lightning Address LNURL server endpoints in QA?

To test LNURL server endpoints in QA, run validation against local dev servers or production URLs using a specific username. This checks endpoint contracts and response formats after making LNURL route changes to ensure compatibility.

Does LNURL validation check callback and metadata fields?

Yes, LNURL validation checks the callback, minSendable, maxSendable, metadata, and tag fields. It enforces endpoint structure and required JSON response formats for Lightning Address integrations.

What do I need to test LNURL pay requests?

You need a base URL and a user identifier to test LNURL pay requests. No external dependencies are required to validate the endpoint structure, JSON response formats, and invoice flow behavior.

Why does my Lightning Address integration fail invoice generation?

Invoice generation may fail if the LNURL endpoint does not enforce required fields or proper JSON response formats. Validating LUD-06 and LUD-21 flows ensures the generated invoice, verify URL, and settlement signals behave correctly.