# Why Overra?

### The Endpoint Problem in Web3

Web3 security innovation has primarily focused on:

* Key management
* Hardware wallet support
* Transaction simulation
* Smart contract auditing

These are necessary — but incomplete.

Most real-world compromises occur at the endpoint level:

* Browser drainer scripts
* Malicious wallet approvals
* Session persistence exploits
* Local malware
* Delayed exploit execution
* Network-level manipulation

Wallet signatures confirm intent. They do not enforce system isolation.

When compromise is suspected, response mechanisms today are manual and reactive:

* Revoke approvals
* Rotate keys
* Disconnect sessions
* Shut down the device

These processes lack:

* Deterministic enforcement
* Cryptographic authorization binding
* Structured state transitions
* Transparent auditability

***

### The Structural Gap

There is no native infrastructure that allows a wallet to deterministically control the containment state of the endpoint.

This creates a separation between:

Cryptographic ownership\
and\
Execution environment integrity.

Overra exists to bridge this gap.

***

### The Overra Response Model

Instead of relying on centralized dashboards or administrative override systems, Overra introduces:

Wallet-authorized containment.

This means:

* A wallet signs a structured authorization message.
* A local agent verifies that signature.
* The endpoint transitions state deterministically.
* All actions are logged immutably.

No third party executes enforcement. No centralized service holds authority.

The power to contain resides with the cryptographic authority itself.

***

### Why This Matters

As Web3 adoption increases:

* Endpoints hold increasing asset value.
* Attack vectors become more sophisticated.
* Institutional participants demand deterministic response mechanisms.

Web3 requires infrastructure-level enforcement.

Overra provides that layer.


---

# Agent Instructions: 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:

```
GET https://overra.gitbook.io/overra-docs/introduction/why-overra.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.