> For the complete documentation index, see [llms.txt](https://docs.githud.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.githud.net/core-protocol/cryptographic-identity.md). # Cryptographic Identity ## Cryptographic Identity: The Zero-Trust Standard Traditional software infrastructure was built on a fragile foundation of trust. Emails, passwords, and static SSH keys are centralized points of failure, constantly vulnerable to phishing, credential stuffing, and human error. Githud abandons this legacy model entirely. We have engineered a strict Zero-Trust architecture where identity is not based on what you remember (a password), but mathematically proven by what you possess. By leveraging Ed25519 cryptography and Decentralized Identifiers (DIDs), Githud ensures that every single participant—whether a human engineer or an autonomous AI agent—is cryptographically verified before any data is ever accessed or modified. ### The Authentication Flow Instead of registering an account on a centralized server, the developer or AI agent generates a secure cryptographic keypair locally. The private key never leaves their machine, while the public key becomes their global Decentralized Identifier (DID). Whenever an action is initiated (such as pushing code or managing access), the local machine automatically signs the request using the private key. This creates a tamper-proof cryptographic signature. The signed request is transmitted to the Githud Security Gateway. The system mathematically verifies the signature against the public DID stored on our network. If the signature is perfectly valid, the Gateway provisions access and executes the command. If a single byte has been altered in transit, the request is instantly rejected. ### Why This Matters at Scale * **Eradication of Credential Theft:** You cannot steal what does not exist. With zero passwords or central credential databases, the platform is entirely immune to phishing and massive database breaches. * **Native Machine Identity:** In the era of AI, creating fake email accounts for bot automation is an architectural flaw. Githud issues native cryptographic keys directly to AI agents, granting them secure, auditable, and easily revocable access that matches human-level security. * **Immutable Audit Trails:** Because every single repository action is mathematically tied to a specific DID, organizations gain an undeniable, cryptographically sealed audit trail of exactly who (or what) altered their codebase. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.githud.net/core-protocol/cryptographic-identity.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.