> 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.md).

# Technology

Explore the technical infrastructure behind Hypotheca, from ERC-8004 identity and reputation to security reports, payment verification, and Uniswap v4 execution controls.

Hypotheca does not rely on a single trust signal. Its verification architecture combines identity and reputation, security posture, economic activity, and execution-level enforcement.

These components turn verified evidence into borrowing conditions. Evidence is not merely stored as metadata. It becomes part of the decision and execution path.

### Four connected layers

```
ERC-8004 Identity
        →
Security Evidence
        →
Payment Evidence
        →
Risk Controls
        →
v4 Hook Enforcement
        →
Borrow Execution
```

#### 1. Identity & reputation

ERC-8004 provides the identity and reputation infrastructure. It establishes a persistent, verifiable identity context and associated reputation history for an agent.

#### 2. Security verification

Security verification evaluates the agent's latest audit report. The process checks report freshness, IPFS content integrity, risk score, and revocation status.

#### 3. Payment verification

Payment verification establishes evidence of real on-chain economic activity. It evaluates transaction hashes, approved facilitators, payer diversity, receipt amounts, and recency requirements.

#### 4. Execution enforcement

A custom Uniswap v4 Hook controls borrow-related execution. It applies the verification gate, asset allowlist, oracle status, and LTV checks before a transaction can proceed.

### Evidence becomes access

Each layer has a distinct role. ERC-8004 establishes identity and reputation context. Security verification evaluates the current software and security posture. Payment verification provides economic evidence.

The Uniswap v4 Hook enforces the resulting decision at execution time. These mechanisms are connected, but they are not interchangeable.

{% hint style="info" %}
Identity, security, and payment evidence become enforceable borrowing conditions.
{% endhint %}

### Explore the components

#### [ERC-8004](/hypotheca-docs/hypotheca/technology/erc-8004.md)

The identity and reputation infrastructure used by Hypotheca.

#### [Security Verification](/hypotheca-docs/hypotheca/technology/security-verification.md)

How audit reports are validated, scored, and checked for freshness and integrity.

#### [Payment Verification](/hypotheca-docs/hypotheca/technology/payment-verification.md)

How on-chain payment receipts are validated and used as economic evidence.

#### [Uniswap v4 Hook](/hypotheca-docs/hypotheca/technology/uniswap-v4-hook.md)

How the Hook enforces verification, allowlists, oracle checks, and LTV limits at execution time.


---

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