Skip to content
Anomaly

Protocol Reference

Intended scope

Section titled “Intended scope”
  • Channel 0xFE envelope — tunnel over Mirror, per-(hub × Mirror-channel) monotonic counter, 128-bit sliding replay window for unordered channels, protocol-version byte, AES-GCM body.
  • Handshake flow (Mermaid diagram) — client identity ECDSA key, server challenge, X25519 exchange, AES-GCM session, AnomalyProtocol.CurrentVersion agreement.
  • Message registry — FNV-1a hash of MessageName, collision detection at startup.
  • Message table — name, direction, channel, payload fields, one-line purpose. Covers:
    • Auth/handshake messages (Anomaly.Shared.Auth).
    • File-transfer: FileManifestMessage, FileChunkMessage, FileTransferCompleteMessage.
    • Asset lifecycle: spawn/despawn/override.
    • Gameplay: BlendShapes, BoneTransforms, VoiceMessage, etc.
  • Version drift policy — how mixed-version clients/servers reject each other cleanly (platform doc §7 resolution note, 2026-04-22).

Sources

Section titled “Sources”
  • Anomaly.Shared\Networking\ — all message DTOs and AnomalyChannel / AnomalyProtocol / AnomalyMessageRegistry.
  • Anomaly.Shared\Auth\ — handshake primitives.
  • E:\Projects\AnomalyLabs\Anomaly\Anomaly.Client.Api\Networking\NETWORKING.md.
  • Platform doc §7 “Resolved” block on replay protection.