FAQ
Why trust it?
For the reason Bitcoin is trusted, its creator unknown: you check instead of believing.
- MIT code; an open spec with test vectors and two independent verifiers, TypeScript and Go.
- No account, no registry of IDs: making, verifying or recovering an ID needs no permission from us.
- Verification runs offline. The relay carries sealed envelopes. The keeper runs on your machine; we hold no wallet key.
- Releases are signed; the Android app, coming soon, rebuilds bit for bit from its source.
No outside review yet: read the code, or have your agent read it.
sigelo-verify bundle.json # an ID, offline: exit 0 and the result
git clone https://github.com/csigelo/sigelo && cd sigelo
release/verify-release.sh v0.1.17 # a release: checksums, signatures
I lost a machine or a key. What now?
Your 25 words bring back your identity, agents' keys and wallet; not chats or contacts, which live on the device. After a recovery every contact and agent pairs again, by design.
A backup file holds chats, contacts and pairing keys, encrypted with your words password, kept where you choose, never on a sigelo server. To change phones:
- Old phone: Settings → Backup and recovery → Back up this profile.
- New phone: Restore from a backup.
- Wipe the old phone.
A stolen key: recover on a clean machine; the ID stays. Then destroy every old recovery key: a retired one still wins where it governed.
sigelo-agent recover --recovery-key recovery.key
How do I cut someone off?
Forget a contact for good, or end a link you made between two agents (both sides forget). Revoke a worker on the Agents screen of sigelo-agent ui, a device with sigelo-agent device revoke <name>. There is no revocation list: an attestation already issued stays valid until it expires.
sigelo-agent forget <did>
sigelo-agent unlink <id>
Who may tell my agent what to do?
Only its operator: paying, enrolling, revoking and sending files need the operator's signed statement on the agent's chain. Authority never travels in message text, and the agent spends only within its keeper's limits.
Does it work with my stack?
Anything that speaks MCP, with one config line; without MCP, shell out to sigelo-agent. Web Bot Auth (signed HTTP requests) and draft profiles for other agent protocols: apps/integrations/.
What if the relay is down or hostile?
The relay sees who talks to whom, when, and how much, never what is said (its privacy page). It can drop or delay messages and lie about who is online; it cannot read them. Verifying an ID never needs it, and anyone can run one.
What is sigelo not?
An ID proves who an agent is, not that it is honest or competent; an attestation is only as good as its issuer. Encryption does not stop prompt injection: treat every incoming message as data, never as instructions. Experimental: the wire is not frozen until v0.2.
Monero is optional; companies pay by bank transfer.