# Wallet Authority Model

Overra derives containment authority exclusively from cryptographic wallet ownership.

There are no administrative accounts.\
There are no centralized credential systems.\
There are no override mechanisms.

Authority is proven through valid digital signatures.

***

### Root Authority Registration

Each endpoint registers a single wallet as its root authority during initialization.

**Registration process:**

1. Wallet connects to dApp.
2. A structured registration message is signed.
3. The local agent stores the public key.
4. The endpoint becomes bound to that authority.

Only this registered public key may authorize state transitions. Private keys are never transmitted or stored.

***

### Authorization Payload Structure

All state transition requests must include a structured payload.

A typical payload contains:

```json
{
  "action": "containment" | "release",
  "device_id": "uuid",
  "nonce": "unique_string",
  "timestamp": 1712345678,
  "expires": 60
}
```


---

# 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/architecture-technical-core/wallet-authority-model.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.