> For the complete documentation index, see [llms.txt](https://hypotheca.gitbook.io/hypotheca-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypotheca.gitbook.io/hypotheca-docs/hypotheca/technology/erc-8004.md).

# ERC-8004

How Hypotheca uses ERC-8004 identity and reputation registries to establish persistent, verifiable agent identity.

Before Hypotheca evaluates whether an agent can borrow, it needs to establish who the borrower is.

Hypotheca uses ERC-8004 identity and reputation infrastructure to create a persistent on-chain identity context for autonomous agents. This is the first layer of the verification stack. It is not the complete credit decision.

### Identity verification

An agent passes the identity layer only when it satisfies every required condition:

* It holds a valid ERC-8004 identity token.
* Its identity is active and not revoked.
* A reputation log exists.
* Its wallet is distinct from the deployer or protocol wallet.
* It is not flagged as part of a coordinated Sybil cluster.

These requirements provide the starting context for credit evaluation. Identity establishes accountability. Reputation supplies historical context. Wallet separation reduces direct control overlap.

Sybil-cluster checks address cases where fabricated identities might appear to be independent borrowers. They are part of Hypotheca's verification requirements. They do not establish unique identity or eliminate Sybil activity.

### ERC-8004 registries

Hypotheca references two ERC-8004 registries on Robinhood Chain.

#### Identity Registry

The Identity Registry verifies the agent's identity and active status.

`0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`

#### Reputation Registry

The Reputation Registry establishes that a reputation history exists for the agent.

`0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`

**Network:** Robinhood Chain\
**Chain ID:** `4663`

### Identity gate logic

The identity layer applies conjunctive logic:

```
Identity_Pass =
Valid_ERC8004_Identity
AND Identity_Active
AND Reputation_Log_Exists
AND Wallet_Separated
AND Not_Sybil_Cluster
```

Failure of any required condition prevents the agent from passing this layer. A successful identity check only satisfies one prerequisite within the larger Credit Gate.

### Role in the credit gate

ERC-8004 provides the identity foundation on which the remaining checks operate:

```
Agent Request
        →
ERC-8004 Identity Verification
        →
Security Verification
        →
Payment Verification
        →
Asset Allowlist
        →
Oracle Check
        →
LTV Check
        →
v4 Hook Approval
        →
Borrow Execution
```

Identity verification occurs first because it gives the protocol a persistent borrower context. Security, economic activity, and transaction-level conditions remain separate checks.

### Identity is not credit

{% hint style="warning" %}
A valid ERC-8004 identity does not automatically grant borrowing access.
{% endhint %}

Hypotheca still requires:

* A current qualifying security report.
* Verified payment receipts.
* An approved asset.
* A healthy oracle state.
* An LTV within the permitted limit.

Identity establishes the borrower context. The subsequent checks determine whether the requested borrowing action can proceed.

### Conceptual verification sequence

The identity layer follows this documentation-level sequence:

```
1. Read agentId.
2. Verify the ERC-8004 identity exists and is active.
3. Confirm a reputation log exists.
4. Verify the borrower wallet is separated from the deployer or protocol wallet.
5. Check for coordinated Sybil-cluster flags.
6. Return pass or reject with the applicable verification failure.
```

This sequence describes the required checks without defining implementation-specific contract methods.

### Why identity comes first

A credit system for autonomous agents needs more than a wallet address. Hypotheca starts with persistent identity and reputation context before evaluating security posture, economic activity, and borrowing conditions.


---

# 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://hypotheca.gitbook.io/hypotheca-docs/hypotheca/technology/erc-8004.md?ask=<question>&goal=<endgoal>
```

`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.