Technology
The protocol and architecture beneath not.bot — the identity model, the privacy and security guarantees, the cryptographic foundations, and developer references. For what it's all for, in plain language, see Learn.
FAQ
Why a blockchain at all?
A signature must stay verifiable by anyone, forever, without asking us. That takes a public, append-only record that no one, Julia Social included, can rewrite or turn off. A database we operate would make us the gatekeeper. Read the full argument in Why Chia?
not.bot Digital Identity
- Identity Architecture: DIDs, Aliases, and Ownership — How not.bot identities are created, controlled, and verified without a central server, using the did:julia method.
- Credentials, Presentations, and Selective Disclosure — Single-claim credentials and verifiable presentations: how not.bot users prove facts without revealing more than they intend.
- Delegation and Organizational Identity — How a protected not.bot identity grants narrow, time-bound, revocable authority to delegates, with every chain ending at an accountable human.
- Recovery — How a not.bot identity survives lost or stolen keys: recover on a new phone with a passport re-scan and your recovery password, behind a fixed 48-hour delay. There is nothing to set up in advance beyond that password.
Trust
Co-developed with Galois. We co-developed the multiparty-computation protocols at the core of not.bot (age proofs, credential issuance, key operations) with Galois, the formal-methods and cryptography research firm whose MPC work spans DARPA, IARPA, and Department of Homeland Security programs. Read the protocol design in the docs below, and check the standing register of known weaknesses in the Security Model.
- Privacy Architecture — What every party can and cannot learn. not.bot's privacy guarantees, enforced by architecture rather than policy.
- Security Model and Known Weaknesses — not.bot's security model as testable claims: authenticity, integrity, non-repudiation, availability, and known weaknesses.
- Law Enforcement and Accountability — How a lawful demand identifies the person behind one signature, and why bulk surveillance is impossible by design.
Protocol & Infrastructure
- Enrollment and Identity Proofing — How a person becomes a verified human in not.bot: the passport-scan enrollment flow, what it proves, and what a relying party learns from an enrolled identity.
- Cryptographic Foundations — The cryptography not.bot depends on: BLS12-381 signatures and aggregation, multiparty computation, on-device key management, and revocation — and why each was chosen.
- System Architecture and Degraded-Mode Operation — The components of the not.bot system, the trust boundaries between them, and what keeps working when any one component fails.
- did:julia Technical Specification — The did:julia DID method at the design level: singleton structure, state model, transaction families, presentation modes, and security properties.
- Chialisp Code Reference — Puzzle-by-puzzle reference for the did:julia Chialisp smart contracts.
- Why Chia? — Why a public blockchain is required for this kind of identity, and why did:julia is built on Chia rather than the alternatives.
not.bot Verify Documentation
- not.bot Verify: Architecture and Privacy — How not.bot Verify runs entirely inside your infrastructure: its components, the verification flow, DID-based trust, and what each party can and cannot see.
- not.bot Verify: Preflight Checklist — What to confirm before deploying not.bot Verify.
- not.bot Verify: Deployment Checklist — A step-by-step checklist for standing up not.bot Verify.
- not.bot Verify: Operations and Reference Guide — Operating not.bot Verify in your own infrastructure: reference and day-two operations.
- not.bot Verify Web SDK Reference — Integrate not.bot Verify into your site: routes, response models, and per-language quickstarts.