ipns

Publish signed IPNS records with key management and republish scheduling.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/MysticRyuujin/spirens --skill ipns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ipns
Source: https://github.com/MysticRyuujin/spirens/tree/main/ipns
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill ipns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IPNS provides mutable pointers for IPFS content, enabling stable URLs even as content changes, but it can be slow and DNS-backed names (dnslink) are often a better default solution.

Core Features & Use Cases

  • IPNS publishing and key management to assign permanent pointers to rotating IPFS content.
  • Republish scheduling and TTL awareness to keep records fresh and resolvable.
  • Optional Pubsub-assisted IPNS for faster, real-time updates across nodes.
  • DNSLink as a faster, DNS-native alternative when you control a domain.

Quick Start

Publish a signed IPNS record for your current IPFS content by generating a key and running ipfs name publish with the CID.

Frequently Asked Questions about ipns

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

FAQPage Schema
How do I create stable URLs for IPFS content that changes over time?

IPNS publishing creates mutable pointers for IPFS content, enabling stable URLs even as the underlying CIDs change. You generate a key and run ipfs name publish with the CID to assign a permanent pointer to rotating content.

Why is IPNS resolution slow and how can I speed it up?

IPNS resolution can be slow in environments without reliable DNS. You can enable optional Pubsub-assisted IPNS for faster, real-time updates across nodes, or switch to DNSLink as a faster, DNS-native alternative when you control a domain.

What is the difference between IPNS and DNSLink for content pointers?

IPNS provides mutable signed pointers without requiring a domain, while DNSLink is a faster, DNS-native alternative that relies on standard DNS records. DNSLink is often the better default solution when you control a domain.

How do I manage IPNS keys and republish scheduling?

IPNS key management involves generating keys to sign records, while republish scheduling and TTL handling keep those records fresh and resolvable. This ensures long-lived URLs remain valid as content updates over time.

Can I expose IPNS content through an HTTP gateway?

Yes, IPNS supports HTTP gateway exposure to serve mutable content over standard web protocols. This allows long-lived URLs to resolve correctly through gateways without requiring direct IPFS node access.

When should I not use IPNS for publishing IPFS content?

You should avoid IPNS when you control a domain and need faster resolution, as DNSLink is often a better default. IPNS can also be problematic in environments without reliable DNS due to slow resolution times.