Protocol Architecture
A technical teardown of the TrustForge implementation.
Comparison: Stateful vs. Stateless
TrustForge eliminates the need for database round-trips during authorization checks.
| Feature | Legacy JWT/OAuth | TrustForge Protocol |
|---|---|---|
| Verification Latency | High (Requires DB Read / Network JWKS) | Low (<1ms in-memory calculation) |
| Cryptography | Varied / Implementation dependent | Strict Ed25519 / X25519 |
| IoT / Bare-Metal | Difficult / OS dependent | Native no_std embedded support |
Cryptographic Boundary
Session boundaries in TrustForge are secured via X25519 key agreements, signed with Ed25519 keys, and symmetrically encrypted via ChaCha20-Poly1305.
Edge Verification
When an agent presents a Capability and Proof to an edge node, the node verifies the signature against the agent's known public key. If valid, the edge node evaluates the Capability against a localized Rego policy schema. If both pass, the action is permitted.