> For the complete documentation index, see [llms.txt](https://autopilot-5.gitbook.io/autopilot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://autopilot-5.gitbook.io/autopilot/protocol/markdown/verification-and-transparency.md).

# Verification & Transparency

Autopilot is designed to be verifiable by design.

All core actions including voting, reward allocation, and withdrawals are executed on-chain and can be independently audited by anyone using a blockchain explorer. No backend systems, manual overrides, or off-chain processes are involved.

The system uses deterministic logic, fixed reward formulas, and structured events to ensure that every outcome is transparent and reproducible.

***

#### On-Chain Verification

All user data and protocol activity is publicly accessible on Base and compatible with any EVM block explorer.

**Verifiable Components:**

* **veAERO Ownership**\
  Deposited NFTs are tracked in:

  ```solidity
  solidityCopyEditmapping(address => LockInfo[])
  ```

  Users can confirm which NFTs are active, how much voting power they hold, and when they were deposited.
* **Voting Activity**\
  Every `vote()` transaction records:
  * Target pools
  * Vote weights
  * Block timestamp\
    This allows anyone to confirm that votes were cast as expected by the strategy logic.
* **Reward Calculations**\
  All distributions follow fixed math based on vote weight.\
  No randomness, admin override, or off-chain logic affects the result.\
  Users can independently verify their rewards using public contract state.
* **Snapshot Events**\
  Before each vote, claim, or user action, Autopilot emits a `Snapshot` event.\
  This locks in voting weight for the epoch and ensures consistent reward tracking.

> All protocol logic is on-chain and deterministic. Nothing requires off-chain trust or manual intervention.

***

#### 🧾 Event-Based Audit Trail

Autopilot emits on-chain events for every critical action. These logs form a permanent and machine-readable record for use in explorers, dashboards, or analytics tooling.

**Event Types:**

* **Deposit**\
  Emitted when an NFT is deposited. Includes:
  * NFT ID
  * Voting power
  * Timestamp
* **VotingCompleted**\
  Emitted after batch voting. Includes:
  * List of gauges
  * Vote weights
  * Gas used
* **RewardsSnapshot**\
  Emitted at the start of each epoch. Includes:
  * Total rewards claimed
  * Voting weight snapshot
  * Final USDC distribution value
* **Withdraw**\
  Emitted when a user exits. Includes:
  * NFT ID
  * Final voting power
  * Final claim state (if applicable)

***

#### 📂 Use Cases

* **Auditing**\
  Third parties can verify reward distribution, vote timing, and system integrity without internal access.
* **Community Oversight**\
  LPs, DAOs, or funds can monitor how Autopilot allocates voting power and confirm alignment with their interests.
* **Reporting and Integration**\
  Structured logs allow Autopilot to serve as a backend for funds, vaults, or aggregators — with full traceability.


---

# 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://autopilot-5.gitbook.io/autopilot/protocol/markdown/verification-and-transparency.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.