# 3.1 Proof of Rights vs. Proof of Identity

In the current EVM standard, `msg.sender` is the ultimate source of truth. This conflates identity (who sent this) with capability (do they have the funds). This is a privacy nightmare, as proving capability requires revealing identity (the address).

Accessth separates these into two distinct cryptographic primitives:

PRIMITIVE A: The Identity Circuit This circuit proves that the user holds a valid private key associated with a Permission Set. It outputs a simple boolean: VALID or INVALID. It reveals nothing about the user's history, total holdings, or other associated wallets.

PRIMITIVE B: The Capability Circuit This circuit proves that the Permission Set associated with the user contains sufficient value to cover the requested transaction. It utilizes a Merkle Tree structure to verify the state of the user's rights without revealing the specific leaf node (the exact balance).

By combining these, we achieve "Proof of Rights." The network knows you can spend the money, but it does not know who you are or how much money you have left.


---

# 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://docs.accessth.xyz/part-3/3.1-proof-of-rights-vs.-proof-of-identity.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.