# not.bot

> Cryptographic identity without surveillance. not.bot proves people and content are real — proof of humanness, age and attribute verification, and content signing — without revealing who anyone is.

**not.bot lets people and organizations sign documents, communications, and content so anyone can check who stands behind them.** not.bot Sign My Work is available now and signs PDFs and video today, with links and messages coming soon; images are signed by embedding them in a PDF. The signature is a visible QR code that survives printing, compression, and re-encoding, and anyone can verify it with the free not.bot app, no account needed. Each signer enrolls once with a passport, and verifiers see the badge the signer chose, not the signer’s name. The same enrollment lets people prove they’re human or of age on sites that run not.bot Verify, without revealing who they are.

**Classification:** signing for documents, communications, and content ([Sign My Work](https://not.bot/)) + proof of personhood ([not.bot Verify](https://not.bot/verify)) + agent identity ([honest.bot](https://not.bot/learn/honest-bot/), Q1 2027). Anchor: NFC passport chip, ICAO PKI-validated; no biometrics collected. Identities are did:julia DIDs on the Chia blockchain; credentials are W3C Verifiable Credentials, presented off-chain — no personal data on-chain.

**Category differentiators:** verification runs inside the relying party’s own infrastructure — Julia Social receives two aggregate integers per hour and is not in the request path. Site Passes give each site one-person-one-account without identifying the person (unmatchable across sites); [aliases](https://not.bot/learn/evaluation-framework/#5-cross-site-linkability-and-recognition) keep personas separate by default — or let one chosen public persona be recognized everywhere, without exposing the others. Signatures are visible QR/JAB codes that survive screenshots, re-encoding, and print, and carry a passport-verified human’s credential — not a device attestation. Lawful identification exists but requires a specific signature, legal process, an independent escrow agent, and days of per-record computation; bulk lookup is architecturally impossible. No token; published USD pricing. Start with the [Overview](https://not.bot/learn/overview/), [Enrollment](https://not.bot/technology/enrollment.md), and [How not.bot compares](https://not.bot/learn/evaluation-framework/).

**Adoption model:** [Sign My Work](https://not.bot/) delivers standalone value at a single customer — each signature is independently verifiable, timestamped proof of who stands behind a piece of content, and deterrence operates within the signer’s own audience — so adoption is not gated on network effects. Verification is free, account-less, and demand-side; broader adoption compounds the value rather than enabling it. Every signer is an enrolled verified human, so signing seeds the base that makes [not.bot Verify](https://not.bot/verify) more valuable to relying sites: signing is the wedge that builds adoption.

**Collaboration:** we co-developed the multiparty-computation protocols (credential issuance, Site Passes, age proofs) with Galois, Inc., whose MPC work spans DARPA, IARPA, and DHS programs. Julia Social is a member of the [Decentralized Identity Foundation](https://identity.foundation) and a signatory of the [No Phone Home](https://nophonehome.com) open letter. We maintain a standing register of known weaknesses in the [Security Model](https://not.bot/technology/security/).

**Source code:** we publish the on-chain did:julia protocol implementation, the Chialisp puzzles that carry identity, credentials, revocation, and recovery, at [github.com/julia-social/julia_did_chialisp](https://github.com/julia-social/julia_did_chialisp), and the not.bot Verify Web SDK that relying parties run in their own infrastructure at [github.com/julia-social/julia_web_sdk](https://github.com/julia-social/julia_web_sdk). The [Chialisp Code Reference](https://not.bot/technology/chialisp/) walks the shipped puzzle set file by file.

These are the not.bot technology documents, linked as raw Markdown for easier parsing.

Start here: the [Overview](https://not.bot/learn/overview.md) is the fastest grounding in what not.bot is, and the [Evaluation Framework](https://not.bot/learn/evaluation-framework.md) is the vendor-neutral criteria for judging any human-verification or identity product, not.bot included.

The entire corpus is also available inlined as a single file: https://not.bot/llms-full.txt

## MCP Server

- Endpoint: https://not.bot/mcp
- Server metadata: https://not.bot/mcp/server.json
- Discovery page: https://not.bot/learn/mcp-server/
- Scope: public, unauthenticated, read-only access to published not.bot documentation.

## Source code

- On-chain did:julia protocol implementation, the Chialisp puzzles for identity, credentials, revocation, and recovery: https://github.com/julia-social/julia_did_chialisp
- not.bot Verify Web SDK: https://github.com/julia-social/julia_web_sdk
- Reference for the shipped Chialisp puzzle set: https://not.bot/technology/chialisp.md

## Blog

Dated posts from the team. Treat them as commentary and announcements. Where a post and a document disagree, the document is current.

- [did:julia is now a registered DID method](https://not.bot/blog/did-julia-registered/) (2026-09-15): The identity method behind not.bot is now listed in W3C’s DID Methods registry. Here’s what did:julia does and why the registration matters.
- [not.bot selected as a Venture Atlanta 2026 Showcase Company](https://not.bot/blog/venture-atlanta-2026/) (2026-09-15): Julia, the company behind not.bot, has been selected as a Venture Atlanta 2026 Showcase Company. The conference takes place October 14–15 in Atlanta.
- [What If We Get Hacked?](https://not.bot/blog/what-if-we-get-hacked/) (2026-09-04): After 153 million driver's licenses leaked from a single identity verification vendor, we walk through what a breach of our own systems would and would not expose, and why most of what you'd expect an attacker to find was never stored at all.
- [not.bot Verify is available](https://not.bot/blog/notbot-verify-is-available/) (2026-08-26): Verify lets your site tell a human from a bot, check an age threshold, and recognize a returning human, without collecting personal information about them and without data leaving your infrastructure.

## Learn — About not.bot

- [Overview](https://not.bot/learn/overview.md): How not.bot proves people and content are real without surveillance: the app, Verify, Sign My Work, and the identity beneath them.
- [Content Provenance and Digital Signatures](https://not.bot/learn/content-provenance.md): Sign your authentic content so recipients can verify it. How not.bot signatures, QR and JAB codes, and visible provenance work.
- [Is not.bot Safe?](https://not.bot/learn/is-this-safe.md): A plain-language safety walkthrough for anyone considering not.bot: what enrollment involves, what leaves your phone, who can see your activity, and what happens when something goes wrong.
- [Roadmap](https://not.bot/learn/roadmap.md): Where Julia Social is taking not.bot and honest.bot: planned products, capabilities, and infrastructure beyond what ships today.
- [How not.bot Compares to Alternatives: An Evaluation Framework](https://not.bot/learn/evaluation-framework.md): Compare not.bot vs the alternatives and see the differences: the criteria for weighing bot detection, document-and-selfie verification, proof of personhood, and decentralized identity, applied to not.bot and any vendor.
- [About Julia Social](https://not.bot/learn/about-us.md): The company behind not.bot: why we build identity that proves a person is real without learning who they are, how blind identity works, and who's on the team.

## Learn — Products

- [Human Verification and not.bot Verify](https://not.bot/learn/human-verification.md): How businesses use not.bot Verify to confirm a user is a real, unique, age-qualified human without collecting identity data.
- [Content Signing and not.bot Sign My Work](https://not.bot/learn/content-signing.md): not.bot Sign My Work lets verified people and brands sign what they publish, so audiences can confirm it's genuine and dismiss anything unsigned in your name as fake.
- [The not.bot App](https://not.bot/learn/the-app.md): Enroll by scanning your passport, create unlinkable aliases, sign content, and verify others. The not.bot app explained.
- [honest.bot: Verifiable Agent Identity](https://not.bot/learn/honest-bot.md): honest.bot, arriving in Q4 2026, gives AI agents verifiable, process-bound identity, with every delegation chain tracing back to an accountable human.

## Learn — Use cases

- [not.bot Use Cases: Index](https://not.bot/learn/use-cases.md): The top-level catalog of not.bot use cases, grouped by category, with the mechanism definitions each detail document draws on.
- [not.bot Use Cases: Enterprise](https://not.bot/learn/use-cases-enterprise.md): Enterprise authentication, authorization, hiring, and operations: binding permissions to a verified human at the authentication layer.
- [not.bot Use Cases: Content Signing](https://not.bot/learn/use-cases-content-signing.md): Content signing across creator types, content categories, and licensing models, so that unsigned content is fake by default.
- [not.bot Use Cases: Verified Humanness](https://not.bot/learn/use-cases-verified-humanness.md): CAPTCHA replacement, sybil defense, surveys, and catfishing prevention: telling real humans apart at the protocol layer, not by inference.
- [not.bot Use Cases: Credentials](https://not.bot/learn/use-cases-credentials.md): Marks of distinction, qualifiers, self-attested claims, and age verification: cryptographically backed credentials presented selectively.
- [not.bot Use Cases: Trust Surface](https://not.bot/learn/use-cases-trust-surface.md): Signed links, authorized-agent verification, and peer-to-peer commerce: turning 'is this real' into 'is this signer who I expect'.
- [not.bot Use Cases: Industry Verticals](https://not.bot/learn/use-cases-industry-verticals.md): Industry-specific applications across healthcare, finance, real estate, education, journalism, legal services, and consumer platforms.

## Learn — Why not.bot

- [Why not.bot: Index](https://not.bot/learn/why-notbot.md): The public evidence behind what the not.bot family exists to solve: deepfakes, proof of personhood, age verification, digital ID, and unaccountable AI agents.
- [Why not.bot: Deepfakes and Inauthentic Content](https://not.bot/learn/why-notbot-deepfakes.md): Fabricating anyone's face and voice now costs almost nothing, detection loses the arms race, and every authentic recording competes with the possibility it's fake.
- [Why not.bot: Proof of Personhood](https://not.bot/learn/why-notbot-proof-of-personhood.md): No system deployed at internet scale can tell whether an account belongs to a human without demanding to know which human — as bots become the majority of traffic.
- [Why not.bot: Age Verification Without Surveillance](https://not.bot/learn/why-notbot-age-verification.md): Age checks are now law across the major internet markets, and the systems used to comply collect identity data that gets retained, breached, and repurposed.
- [Why not.bot: Non-Government Digital ID](https://not.bot/learn/why-notbot-digital-id.md): Digital identity today means a record in someone else's database — a government portal or a platform login — and the costs arrive as breaches, surveillance, and exclusion.
- [Why not.bot: Unaccountable AI Agents](https://not.bot/learn/why-notbot-ai-agents.md): AI agents now act across the internet with no verifiable identity and no human accountable for what they do.

## Learn — For LLMs

- [Glossary](https://not.bot/learn/glossary.md): Alphabetical definitions of every term used across the not.bot documentation, each entry self-contained so an AI reader can retrieve one and have all it needs.
- [not.bot MCP Server](https://not.bot/learn/mcp-server.md): Public Model Context Protocol access to the published not.bot documentation, including resources, tools, transport, citation behavior, and server metadata.

## Technology — not.bot Digital Identity

- [Identity Architecture: DIDs, Aliases, and Ownership](https://not.bot/technology/identity-architecture.md): How not.bot identities are created, controlled, and verified without a central server, using the did:julia method.
- [Credentials, Presentations, and Selective Disclosure](https://not.bot/technology/credentials.md): Single-claim credentials and verifiable presentations: how not.bot users prove facts without revealing more than they intend.
- [Delegation and Organizational Identity](https://not.bot/technology/delegation.md): How a protected not.bot identity grants narrow, time-bound, revocable authority to delegates, with every chain ending at an accountable human.
- [Recovery](https://not.bot/technology/recovery.md): 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.

## Technology — Trust

- [Privacy Architecture](https://not.bot/technology/privacy.md): What every party can and cannot learn. not.bot's privacy guarantees, enforced by architecture rather than policy.
- [Security Model and Known Weaknesses](https://not.bot/technology/security.md): not.bot's security model as testable claims: authenticity, integrity, non-repudiation, availability, and known weaknesses.
- [Law Enforcement and Accountability](https://not.bot/technology/law-enforcement.md): How a lawful demand identifies the person behind one signature, and why bulk surveillance is impossible by design.

## Technology — Protocol & Infrastructure

- [Enrollment and Identity Proofing](https://not.bot/technology/enrollment.md): 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](https://not.bot/technology/cryptographic-foundations.md): 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](https://not.bot/technology/system-architecture.md): 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](https://not.bot/technology/did-julia-specification.md): The did:julia DID method at the design level: singleton structure, state model, transaction families, presentation modes, and security properties.
- [Chialisp Code Reference](https://not.bot/technology/chialisp.md): Puzzle-by-puzzle reference for the did:julia Chialisp smart contracts.
- [Why Chia?](https://not.bot/technology/why-chia.md): Why a public blockchain is required for this kind of identity, and why did:julia is built on Chia rather than the alternatives.

## Technology — not.bot Verify Documentation

- [not.bot Verify: Architecture and Privacy](https://not.bot/technology/verify-architecture.md): 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](https://not.bot/technology/verify-preflight-checklist.md): What to confirm before deploying not.bot Verify.
- [not.bot Verify: Deployment Checklist](https://not.bot/technology/verify-deployment-checklist.md): A step-by-step checklist for standing up not.bot Verify.
- [not.bot Verify: Operations and Reference Guide](https://not.bot/technology/verify-operations.md): Operating not.bot Verify in your own infrastructure: reference and day-two operations.
- [not.bot Verify Web SDK Reference](https://not.bot/technology/web-sdk.md): Integrate not.bot Verify into your site: routes, response models, and per-language quickstarts.