> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uniblock.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# DAO Dashboards and Governance

> Build DAO dashboards with treasury visibility, governance-token monitoring, and event-driven contract tracking.

# DAO Dashboards and Governance

DAO tooling usually needs visibility into treasury wallets, governance-token movement, and contract events rather than a single endpoint category. Uniblock works well as a read and monitoring layer across those requirements.

## Best-fit workflows

* Treasury dashboards
* Governance token monitoring
* Contract-event monitoring for voting or execution contracts
* Contributor and wallet activity tracking

***

## Recommended APIs

* [Token API overview](/reference/unified-api/api-overview-token)
* [Transaction API overview](/reference/unified-api/api-overview-transaction)
* [Webhooks overview](/reference/webhook/webhooks-overview)
* [JSON-RPC overview](/reference/unified-api/overview-jsonrpc)

Useful starting points:

* `GET /token/balance`
* `GET /token/activity`
* `GET /token/allowances`
* `GET /transactions`
* contract-event webhooks

***

## Suggested implementation flow

### 1. Build treasury visibility

Start by indexing known treasury and operational wallets. Use token balances and transactions to create:

* treasury composition views
* outflow and inflow reports
* multisig activity summaries

### 2. Track governance token movement

Use token activity and transfer data to monitor:

* whale movement
* delegate or contributor wallet changes
* unusual governance-token concentration shifts

### 3. Monitor governance contracts

Use contract-event webhooks for:

* proposal creation
* execution events
* protocol-specific governance actions

This is especially useful when the DAO runs custom contracts and you want event-driven automation around them.

### 4. Use JSON-RPC where contract-level detail matters

If the governance flow depends on contract state reads that are not modeled in the Unified API, use JSON-RPC for contract calls while keeping Uniblock as the shared routing layer.

***

## Common pitfalls

<Warning>
  Governance data is often split between token movement and contract state. Do
  not assume one source alone is enough for a full DAO dashboard.
</Warning>

<Warning>
  Allowance data can be important for operational wallets. If your DAO uses
  treasury automation, include approvals and permissions in reviews.
</Warning>

***

## Related docs

* [Contract event webhook type](/reference/webhook/webhook-types/event-trigger-contract-event)
* [Token API overview](/reference/unified-api/api-overview-token)
* [Authentication guide](/guides/uniblock/authentication)