> For the complete documentation index, see [llms.txt](https://docs.nearby.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearby.finance/protocol-layers/proof-of-location-location-layer/device-attestation.md).

# Device Attestation

### Why Device Attestation Matters

Privacy alone is not sufficient for secure geolocation systems.

The protocol must also establish confidence that proofs originate from authentic devices operating in trusted environments.

Without this assurance, malicious actors could generate fraudulent location claims using modified software or emulated devices.

Device Attestation addresses this challenge.

### What Is Device Attestation

Device Attestation is a hardware-backed verification process that confirms:

* The device is genuine
* The operating environment is trusted
* Security protections remain intact
* Critical application components have not been modified

The result is a cryptographic guarantee regarding the integrity of the device generating a proof.

### Attestation Process

When a user initiates proof generation:

1. The device produces an attestation report.
2. Hardware-backed security components sign the report.
3. The protocol verifies device integrity.
4. Proof generation proceeds only if validation succeeds.

This process establishes trust before any geolocation proof is created.

### Security Benefits

Device Attestation helps mitigate:

* Application tampering
* Software emulation
* Device impersonation
* Unauthorized modifications
* Certain classes of spoofing attacks

### Relationship to Proof Generation

Attestation does not validate location itself.

Instead, it validates the environment responsible for generating location proofs.

Combined with Trusted Execution Environments and zero-knowledge verification, Device Attestation strengthens the overall security model of the Proof of Location Layer.

By establishing trust at the hardware level, the protocol reduces reliance on centralized verification authorities.


---

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

```
GET https://docs.nearby.finance/protocol-layers/proof-of-location-location-layer/device-attestation.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.