Decentralized ID Registry

The ID Registry is designed with the principle that every network participant must possess a single, stable, and verifiable identity that they fully own. To ensure security and authenticity, the Griffin ID is managed and secured on-chain using smart contracts, which provide a robust framework for identity verification and management.

In the Griffin Ecosystem, identity serves several critical functions:

• Billing and payments: managing billing, payments, and remaining user balances.

• Access and services: enabling personalized model access and the application of flexible terms of service between Service Providers (SPs) and users.

• State maintenance: maintaining per-user states (for example, conversation logs for chatbots).

• Counterparty identification: identifying counterparties in the network (SPs, Client Providers (CPs), AI Agents) and validating the authenticity of their messages.

• Rating and reputation: ensuring that ratings can be attributed to a verifiable user and validating their background and service history.

Identities within Griffin AI

Identity	Description
Root Identity	The root identity is a cryptographic private/public key pair belonging to the network participant (User, Service Provider, or network operator). The private key is retained securely by the counterparty and used to sign messages within the Griffin network. While not mandatory, using a non-custodial crypto wallet to manage these keys provides a secure and user-friendly solution for managing cryptographic keys. The initial use of the root identity occurs during registration, after which it ideally remains dormant, safeguarded against exposure.
Derived Identity (Signer)	For operational convenience and security, derived identities (Signers) are used for routine network interactions. These are secondary cryptographic key pairs created under the authorization of the root identity and have predefined, limited permissions to perform specific network functions. This mechanism addresses the impracticality and security risks of continually using the root identity, particularly in environments where frequent user confirmations are cumbersome, or machine-to-machine interactions are required.
Imported Identity	A plugin system allows linking alternative identities (for example ENS Nameservice, Worldcoin ID, or Google Accounts) to a user's Root Identity. This enables users to authenticate actions across the network using familiar external identity providers.

To further enhance identity verification, the Griffin AI registry integrates with external protocols that provide proof-of-humanity or proof-of-AI. This integration helps reduce ambiguity in digital interactions by clearly identifying whether interactions are conducted by humans or AI agents, bolstering trust and transparency across the network.

Client Providers (CPs) and user onboarding

Client Providers (CPs) and the client applications they build play an important role in lowering barriers for new users. CPs:

• Manage user states and allow access to services without requiring users to immediately own a Griffin ID.

• Abstract away identity-management complexities from end users, sometimes using alternative (including centralized) authentication methods.

• Enable an identity to be created and exported later upon the user's request.

CPs enable easier onboarding by providing a path to later migrate to a full Griffin ID when users are ready to take ownership of their on-chain identity.

Last updated 1 year ago