tiny.peer

Overview · API · Code relationships · Verification · Audit

Overview

Provides peer identities, network addresses, and bootstrap tickets used to find other nodes. A node is named by an Ed25519 public key stored as 32 bytes and represented in text as 43 base64url characters: the peer identifier. Because this key names the node itself, identity remains valid wherever the node is reachable.

An address represents an endpoint as an IPv4 or IPv6 address with a port, or a relay host name with a port. Nodes exchange addresses using a ticket, a bootstrap record prefixed with tiny-peer: in text that pairs one peer identifier with a list of address hints. Nothing in a ticket is signed or authenticated. Verifying the peer key and securing the session belong to the transport handshake that runs later.

The caller selects the address capacity for a ticket and supplies the backing storage. Because operations write into caller buffers, encoding and decoding allocate nothing.

Definitions

Actions

Public operations.

• encode
• decode

Types and contracts

Public types and contracts.

• TicketStorage
• PeerId
• Relay
• Capacity
• Identity
• Limits
• Ticket
• Address

Values and defaults

Public values and defaults.

• address_text_bytes_max
• peer_id_text_bytes
• ticket_address_count_max: The largest number of addresses one ticket can carry.

Code relationships

Direct static dependencies extracted from parsed source by semantic graph analysis.

Uses: tiny.chant, tiny.hypothesis
Used by: tiny.preserves

Verification

No verification records are cataloged for this module in this build.

Audit