faq-general
How does CueCrux prevent anonymous or spoofed agent activity?
General FAQ · Privacy and identity
bind
The session handshake binds every connection to a passport. No anonymous writes.
carry
Every tool call rides the passport. RCX mints short-lived capability tokens against it.
earn
Verified receipts accrue as reputation. Five tiers climb the capability ladder.
answer
Any receipt, any time later, resolves back to who acted, at what tier, under which grants.
trust is a ledger, not a checkbox: what a passport earns in step 3 changes what step 2 allows
There are no anonymous writes, structurally. Every connection to the daemon binds to a passport, and every tool call carries it. An action without an identity is not logged-and-flagged; it simply cannot enter the store.
On top of that binding:
- Reputation is earned, not asserted. Verified receipts accrue to a passport as reputation across five trust tiers. A new agent starts at the bottom and earns standing from its record.
- Grants are scoped to the identity. RCX capability tokens tie what an agent may do to who it is and what tier it holds.
- Everything resolves back. Any receipt, months later, resolves to who acted, at what tier, under which grants.
Spoofing therefore requires a passport's Ed25519 signing key, not just network access. If a key is compromised, revocation propagates with per-agent acknowledgements and an attestation when zero holders remain.