Files
meshcore-spec/versions/v0.1.0/15-identity.md
T
swaitsandClaude Opus 4.7 44305a06db release: v0.1.0
First cut release. Snapshots ./src/ as ./versions/v0.1.0/ via
`just cut-version v0.1.0` (22 files: 21 chapter MDs + SUMMARY.md).
Deployed alongside `latest` at:

  https://swaits.github.io/meshcore-spec/v0.1.0/

Also:

- CHANGELOG.md adopts Keep a Changelog-style version sections.
  Future entries land under [Unreleased] and graduate to a version
  heading when cut. The existing date-stamped pass entries stay
  put as a historical record of the work captured in v0.1.0.
- README.md fixes a stale "per vX.Y.Z tag" mention left over from
  the tag-based versioning model, and links the current release
  explicitly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 10:04:40 -06:00

3.0 KiB

MeshCore Protocol Specification

Section 15: Identity

Overview

Every MeshCore node has an Ed25519 key pair. The 32-byte public key serves as the node's identity. Hashes used in routing are truncated prefixes of the public key. Shared secrets for encryption are computed via ECDH key exchange using X25519 (Ed25519 keys transposed to Curve25519).

Key Types

Type Size Description
Public Key 32 bytes (PUB_KEY_SIZE) Ed25519 public key
Private Key 64 bytes (PRV_KEY_SIZE) Ed25519 private key (seed + public)
Signature 64 bytes (SIGNATURE_SIZE) Ed25519 signature
Shared Secret 32 bytes (PUB_KEY_SIZE) ECDH shared secret

Hash Derivation

A node's routing hash is simply a prefix of its public key:

hash = pub_key[0..hash_size-1]

Where hash_size is 1, 2, or 3 bytes depending on the protocol version and path encoding (see Section 3).

For V1, PATH_HASH_SIZE is 1, meaning a node's hash is the first byte of its public key. This gives only 256 unique hash values, so hash collisions are common and expected. The protocol handles this by attempting decryption with all peers matching a given hash.

Hash Matching

To check if a hash matches a node's identity:

match = memcmp(hash, pub_key, hash_size) == 0

Ed25519 Signing

Used for advertisement signatures (see Section 5):

  1. Construct the message to sign (e.g., pub_key || timestamp || app_data).
  2. Sign using the Ed25519 private key.
  3. The 64-byte signature is included in the advertisement payload.

Verification:

  1. Extract the public key and signature from the payload.
  2. Reconstruct the message.
  3. Verify the signature using Ed25519 verification.
  4. Receivers MUST discard the packet if verification fails.

ECDH Key Exchange (X25519)

To compute a shared secret between two nodes:

  1. Convert the Ed25519 keys to X25519 (Curve25519) format.
  2. Perform X25519 Diffie-Hellman: shared_secret = X25519(my_private, their_public).
  3. The resulting 32-byte shared secret is used for:
    • AES-128 key: shared_secret[0..15]
    • HMAC-SHA256 key: shared_secret[0..31]

Identity Serialization

Identities can be serialized for storage:

  • Public Identity: 32 bytes (public key only)
  • Local Identity: 64 bytes (private key) + 32 bytes (public key) = 96 bytes

Hex representation uses uppercase characters with 2 hex digits per byte.

Cross-References

Reference Implementation

  • Identity class in src/Identity.h — Public key and verification
  • LocalIdentity class in src/Identity.h — Key pair, signing, ECDH
  • Identity::copyHashTo() — Hash derivation (prefix copy)
  • Identity::isHashMatch() — Hash comparison
  • LocalIdentity::calcSharedSecret() — ECDH key exchange