Destinations

Explains Reticulum destination addressing including types, encryption, and hash calculations.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/torlando-tech/reticulum-skills --skill destinations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Destinations
Source: https://github.com/torlando-tech/reticulum-skills/tree/main/reticulum-protocol/skills/destinations
Command: npx skills add https://github.com/torlando-tech/reticulum-skills --skill destinations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill clarifies how Reticulum represents and addresses destinations, turning human-friendly app names into cryptographic destination hashes used for routing and secure communication.

Core Features & Use Cases

  • Destination types: SINGLE, GROUP, PLAIN, and LINK with their encryption and routing properties.
  • Hashing and naming: How name hashes, identity hashes, and destination hashes are derived and combined.
  • Use cases: Understanding how destinations are chosen for private messaging, group communication, or broadcasts in a Reticulum network.

Quick Start

Experiment with a sample destination name to conceptualize how the rules produce a destination hash.

Frequently Asked Questions about Destinations

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

FAQPage Schema
How does Reticulum destination addressing work?

Reticulum destination addressing converts human-readable app names into cryptographic destination hashes used for routing and secure communication. The system derives name hashes, identity hashes, and final destination hashes based on destination type (SINGLE, GROUP, PLAIN, or LINK) and applies encryption properties specific to each type.

What are the different Reticulum destination types and their encryption properties?

Reticulum supports four destination types: SINGLE for private encrypted communication, GROUP for multi-recipient encrypted messaging, PLAIN for unencrypted broadcasts, and LINK for direct peer connections. Each type has distinct encryption and routing characteristics that determine how messages are secured and delivered.

How do name hashing and destination hash calculations work in Reticulum?

Destination hashes are derived by combining name hashes and identity hashes according to type-specific rules. The hashing process transforms destination names into fixed-length cryptographic identifiers that enable routing while maintaining the relationship between human-friendly names and network addresses.

When should I use SINGLE vs GROUP vs PLAIN destinations in Reticulum?

Use SINGLE destinations for private one-to-one encrypted messaging, GROUP for encrypted communication with multiple recipients, and PLAIN for unencrypted broadcasts or public data. Choice depends on whether you need encryption, number of intended recipients, and privacy requirements in your Reticulum application.

How do I map an application name to a Reticulum destination hash?

Apply the destination hashing rules for your chosen destination type to the application name. The process combines the name hash with identity information according to type-specific conventions, producing the cryptographic destination hash used for routing and secure communication in the Reticulum network.