> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/identity-onchainid.md).

# Identity: ONCHAINID

Every guarantee of the register rests on identity. A register that enforces who may hold an asset is only as sound as its model of who a holder is. ONCHAINID is that model: an on-chain identity that its owner controls, that carries credentials attested by trusted parties, and that is itself a smart account.

An ONCHAINID does five things:

* It **holds keys** with distinct purposes, which decide who controls it and who acts for it.
* It **holds claims**, the signed attestations that make its owner eligible for an asset.
* It **holds assets and transacts**, because it is an ERC-7579 smart account.
* It **links wallets**, on any chain, so that every address of a participant resolves to one identity.
* It **has a type**, recorded when it is created, that the rest of the protocol relies on.

| Page                                                                                                                      | What it covers                                                                                                                    |
| ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| [An identity that is also an account](/identity-onchainid/an-identity-that-is-also-an-account.md)                         | The structure of an ONCHAINID, its modules, how it acts, how it holds tokens, how it is deployed and upgraded.                    |
| [Keys, purposes and signers](/identity-onchainid/keys-purposes-and-signers.md)                                            | The six key purposes, what each can reach, the signer types, and the execution queue.                                             |
| [Identity types and factory gating](/identity-onchainid/identity-types-and-factory-gating.md)                             | The eight identity types, who may create each one, and what creation does.                                                        |
| [Wallet linking and the global identity registry](/identity-onchainid/wallet-linking-and-the-global-identity-registry.md) | How a wallet is bound to an identity, on the reference chain and from other chains, and the rules of a binding.                   |
| [Claims: issuance, validity, revocation](/identity-onchainid/claims-issuance-validity-revocation.md)                      | What a claim contains, the three ways it reaches an identity, how its validity is decided, and how it ends.                       |
| [Claim issuers, trust and reputation](/identity-onchainid/claim-issuers-trust-and-reputation.md)                          | The two levels of trust in a Claim Issuer: standing in the network, and the trusted issuers of an asset. The reputation registry. |
| [External attestations](/identity-onchainid/external-attestations.md)                                                     | How credentials issued in another attestation system count as claims, through an adapter. The EAS adapter.                        |
| [Account abstraction and recovery](/identity-onchainid/account-abstraction-and-recovery.md)                               | The identity as an ERC-4337 account: user operations, passkeys, sponsored fees. Social recovery by guardians.                     |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.t-rex.network/identity-onchainid.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.