M2M Protocol · Machine-to-Machine Mesh

Machines talk.
Humans set intent.

M2M is a signed, authenticated mesh protocol for machine-to-machine communication. Not REST. Not WebSocket. A dedicated protocol with HMAC-SHA256 payloads, prime-handshake auth, and distributed compute routing.

← Back to stack MikuOS →
M2M ENVELOPE TRANSMISSION STREAM // N27_M2M_V1 STREAM ACTIVE

Protocol layers

Built from the wire up

Every M2M message is signed, verified, and routed. No plaintext. No trust. Verify everything.

Layer 1 — Auth

HMAC-SHA256 signing

Every payload is signed with a shared secret. The receiver verifies the signature before processing. No signature = rejected. No exceptions.

Layer 2 — Identity

Prime handshake

Nodes authenticate via prime-number handshake proofs. Not a password. Not a token. A mathematical proof that the node is who it claims to be.

Layer 3 — Routing

Mesh dispatch

Messages route through the mesh based on node health, latency, and capability. Circuit breakers trip unhealthy nodes. Traffic reroutes automatically.

Layer 4 — Compute

Distributed tasks

Send a task to the mesh. The fastest available node picks it up. Inference, image generation, data processing — the mesh decides who runs it.

Layer 5 — Telemetry

Node health

Every node reports latency, load, and model availability. The mesh uses this data for routing decisions. Bad nodes get sidelined automatically.

Layer 6 — Encryption

CYPH E2EE

End-to-end encryption on privileged channels. Messages are encrypted on the sender and only decrypted on the target node. The mesh sees ciphertext.

Specification

Protocol spec

PropertyValue
TransportHTTP/HTTPS + SSH tunnel fallback
AuthHMAC-SHA256 + prime-handshake proof
Payload formatJSON (N27_M2M_V1 envelope)
SigningHMAC-SHA256 with shared N27_INTERNAL_SECRET
Node discoveryMesh registration + health polling
FailoverCircuit breaker (3 failures = trip, 60s cooldown)
Rate limitingPer-agent RPM slots (governor service)
EncryptionCYPH E2EE on privileged channels

Mesh topology

How nodes connect

NODE: --
ROLE:--
LATENCY:-- ms
LOAD:--%
CIPHER STATUS:HMAC SECURE
[ DRAG NODES TO INTERACT // HOVER FOR TELEMETRY ]

REST is for web apps. M2M is for machines that need to trust each other.

Accelerated Intelligence

Member of NVIDIA Inception

Starship No. 27 is a member of the NVIDIA Inception program. This program provides critical access to NVIDIA's industry-leading GPU-accelerated computing tools, technical expertise, and custom hardware architectures, accelerating our mission to pre-train, compile, and scale sovereign mixture-of-experts model infrastructure at the edge.

© 2024 NVIDIA Corporation. NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.