# Ero (EarnOS)

**Ero** (by EarnOS), built on Verona, is the **flagship consumer launch** for **user-owned, verified participation**. People earn for what they already do online: activity is cryptographically verified, and the data underneath is never exposed.

**EarnOS** is the product surface; **Ero** is the live consumer experience users open at launch. Together they demonstrate verification, ownership, reuse, and real economic activity on the same network validators secure and developers build on.

## What Ero shows

* Users connect everyday accounts (for example ride-share or delivery apps) and verify attributes with the [Truth Engine](/verona/about-verona/verification-infrastructure.md)
* Verified facts stay **user-owned** on the network and can be reused where the user consents
* Rewards and campaigns map to **proof of eligibility**, not self-reported claims
* [Meta Accounts](/verona/about-verona/generalized-abstraction/meta-accounts.md) handle identity and consent boundaries without wallet friction

## For developers

Ero builds on the same primitives as any Verona application:

* **zkTLS, zkEmail, zkPassport, and app attestations** for eligibility without raw data exposure
* **Meta Accounts** for authentication and permission scopes
* **CosmWasm** and Treasury patterns for on-chain settlement and gasless UX (`xion-testnet-2` for development)

Typical integration patterns:

1. Verify a user action or attribute with the Truth Engine
2. Map the proof to your app's business rules (campaign, tier, payout, agent gate)
3. Settle or record outcomes on the Verona network

{% hint style="warning" %}
Do not describe unannounced token products, partner programs, or revenue figures as live in your own apps or docs. Follow legal and marketing review before publishing reward, revenue-share, or token numbers.
{% endhint %}

## Related docs

* [Surfaces](/verona/about-verona/surfaces.md)
* [Verification guides](/verona/build-on-verona/verification.md)
* [Meta Accounts](/verona/about-verona/generalized-abstraction/meta-accounts.md)


---

# 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.burnt.com/verona/about-verona/surfaces/earnos.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.