clip-reference

Reference CLIP protocol event structures and signature verification for Nostr Lightning nodes.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/feelancer21/nodestr --skill clip-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clip-reference
Source: https://github.com/feelancer21/nodestr/tree/main/.claude/skills/clip-reference
Command: npx skills add https://github.com/feelancer21/nodestr --skill clip-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a definitive reference for the CLIP protocol, ensuring correct implementation and validation of Lightning node information exchanged over Nostr.

Core Features & Use Cases

  • Protocol Reference: Detailed Go implementation of CLIP event structures, validation rules, and signature verification.
  • Signature Validation: Implements strict verification for Lightning node signatures on Nostr events.
  • Use Case: Developers implementing CLIP clients or servers can use this reference to ensure their code accurately mirrors the official Go implementation, preventing interoperability issues and security vulnerabilities.

Quick Start

Refer to the event.go file for the exact structure and validation logic of CLIP events.

Frequently Asked Questions about clip-reference

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

FAQPage Schema
How do I validate Lightning node signatures on Nostr?

The CLIP protocol reference provides strict cryptographic signature verification for Lightning node signatures on Nostr events, ensuring correct implementation and preventing security vulnerabilities.

What is the CLIP protocol for Lightning nodes on Nostr?

The CLIP protocol defines event structures, validation logic, and a trust model for exchanging Lightning node information over Nostr, ensuring interoperability between clients and servers.

How do I serialize and sign CLIP events correctly?

Serialize and sign CLIP events by following the event serialization and signing procedures based on the official Go reference code, ensuring your implementation accurately mirrors the official standard.

Does this CLIP protocol reference include validation logic for interoperability?

Yes, this CLIP protocol reference includes comprehensive validation logic derived from the Go implementation, ensuring clients and servers accurately mirror the official standard to prevent interoperability issues.

Why does my CLIP implementation fail signature verification?

Your CLIP implementation likely fails signature verification due to incorrect event serialization or deviations from the strict signing procedures defined in the Go reference code, causing validation errors.