> For the complete documentation index, see [llms.txt](https://whitepaper.silencio.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.silencio.network/technical-overview/on-chain-consent.md).

# On-Chain Consent

<figure><img src="/files/3fGaQg0r5zrXdRRc3TxJ" alt=""><figcaption></figcaption></figure>

### On-Chain Consent

### Consent as a verifiable asset

Most data companies ask you to trust that consent was given. Silencio lets you verify it. Every meaningful action on the network is recorded on-chain, so both contributors and the buyers licensing their data can independently confirm that every dataset was collected with explicit, provable permission. This is the mechanism that turns Silencio's ethical principles into something a regulator can audit and a buyer can defend.

### How it works

When someone joins the network, they create a self-custodial wallet and a sensor account abstraction wallet through Particle Network by agreeing to the platform's terms. **The seed phrase is stored securely on the device and never leaves it.** From that point, the wallet issues verifiable, on-chain consent, powered by the Peaq Network, for each category of participation: **microphone access for voice contribution, deliberately granted, never assumed**, voice and audio contributions through Silencio Voice AI across scripted prompts, free speech, conversation, and commands, the environmental measurements behind Sound Check, and network actions such as raffles and bounties.

### What gets recorded

Each consent action is **immutably recorded on-chain, specifying the type of data authorized, the device ID, and the time of contribution.** The result is a tamper-proof audit trail tied to a non-identifying machine ID, the exact provenance the EU AI Act now demands, captured at the moment of contribution rather than reconstructed afterward. The same architecture holds whether a person contributes through the mobile app or through the browser-based Voice AI platform, which requires no download yet carries identical on-chain consent.

### Why it matters

For contributors, this is ownership made real: their permission is recorded, scoped, and theirs. For buyers, it is the difference between data they can deploy and data that becomes a liability the moment a regulator asks where it came from. As detailed in On-Chain Proof and Data Privacy in Depth, consent here is not a checkbox in a database Silencio could quietly alter. **It is a public record neither we nor anyone else can rewrite.**


---

# 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://whitepaper.silencio.network/technical-overview/on-chain-consent.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.