Identity Database

Type: component
PROBLEM

All registered human identity records need to live somewhere that is accessible, auditable, and not a single point of failure.

SOLUTION

The Identity Database is the distributed ledger and relational database hybrid architecture that stores and serves all Human Registrar identity records across a globally replicated node network operating under the open-specification governance framework. Each identity record is stored as an encrypted blob anchored to the registrant's biometric hash, with all personally identifiable fields encrypted at rest under a per-record key that the registrant theoretically controls. The database is append-only, meaning no record is ever deleted — it is only marked inactive — which provides a complete audit trail of every identity event in the system and also means that whatever you put in there is in there. The open-specification governance structure means any compliant third-party system can query the verification endpoint to confirm a registered identity without accessing the underlying record, returning only a match confidence score and the registrant's publicly disclosed verification tier. The database was designed by engineers who have read the ICANN bylaws and found them aspirational.

Inputs
Outputs
TREE
AVAILABLE INPUTS
AVAILABLE OUTPUTS
Schema
                            {
    "id": "comp_identity_database",
    "name": "Identity Database",
    "type": "component",
    "inputs": [],
    "outputs": [],
    "passthru": [],
    "children": [],
    "extends": null,
    "problem": "All registered human identity records need to live somewhere that is accessible, auditable, and not a single point of failure.",
    "description": "The Identity Database is the distributed ledger and relational database hybrid architecture that stores and serves all Human Registrar identity records across a globally replicated node network operating under the open-specification governance framework. Each identity record is stored as an encrypted blob anchored to the registrant's biometric hash, with all personally identifiable fields encrypted at rest under a per-record key that the registrant theoretically controls. The database is append-only, meaning no record is ever deleted \u2014 it is only marked inactive \u2014 which provides a complete audit trail of every identity event in the system and also means that whatever you put in there is in there. The open-specification governance structure means any compliant third-party system can query the verification endpoint to confirm a registered identity without accessing the underlying record, returning only a match confidence score and the registrant's publicly disclosed verification tier. The database was designed by engineers who have read the ICANN bylaws and found them aspirational.",
    "template": "component"
}

Universe Alpha