> For the complete documentation index, see [llms.txt](https://waodao.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waodao.gitbook.io/docs/development/smart-contracts.md).

# Smart contracts

WAODAO uses public blockchain infrastructure for token ownership, NFT provenance, treasury coordination and liquidity. Wherever possible, we rely on battle-tested standards and widely used protocols instead of unnecessary custom smart contract logic.

### Core Ethereum contracts

WAODAO’s main Ethereum contracts are based on established [OpenZeppelin standards.](https://docs.openzeppelin.com/contracts/4.x/) Actual library source is available on [github](https://github.com/OpenZeppelin/openzeppelin-contracts/).

**WAO token contract**

WAO DAO token contract ([ERC20 standart](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/)): [0xc3ad687c8ecb352d56393c77d19018b93a6ad21a](https://etherscan.io/token/0xc3ad687c8ecb352d56393c77d19018b93a6ad21a) You can find contract technical description [here](https://docs.openzeppelin.com/contracts/4.x/erc20).

WAO is the ecosystem token of WAODAO. The Ethereum ERC-20 deployment is the source token for the broader cross-chain WAO ecosystem.

**WAODAO NFT contract**

WAO DAO NFT contract ([ERC721 standart](https://eips.ethereum.org/EIPS/eip-721)): [0x3b9a62c6dd4d93f8a6fa4a350da32d28fac80863](https://etherscan.io/token/0x3b9a62c6dd4d93f8a6fa4a350da32d28fac80863) You can find contract technical description [here](https://docs.openzeppelin.com/contracts/4.x/erc721).

This contract represents the daily WAODAO ArtChain archive. Each final artwork of the day is minted as an NFT on Ethereum and can be discovered through OpenSea and Ethereum explorers.

### Solana deployment

WAO also has a Solana SPL Token deployment connected to the Ethereum WAO token through Wormhole bridge infrastructure.

Standard: SPL Token\
Network: Solana\
Mint address: [`8VXHSGipWfvkA4zueP42YrexbhcWDQKRT1uXZTFEZUn7`](https://solscan.io/token/8VXHSGipWfvkA4zueP42YrexbhcWDQKRT1uXZTFEZUn7)

The Solana deployment does not create separate WAODAO tokenomics. It extends WAO liquidity into the Solana ecosystem and supports faster, lower-cost Friendly Pools and partner liquidity routes.

### Treasury and multisig

For Treasury management we use [Gnosis safe](https://gnosis-safe.io/) smart contracts with 2/4 signatures threshold.&#x20;

Our Ethereum Gnosis safe: [0x6551DA3a016eE12a14aE4435B615222d71BEA778](https://etherscan.io/address/0x6551da3a016ee12a14ae4435b615222d71bea778)

Safe is used because it is a widely adopted multisig standard in the Ethereum ecosystem and is trusted by many major Web3 teams. It helps reduce single-key risk and makes treasury operations more transparent.

### Liquidity infrastructure

In addition to WAODAO’s own token and NFT contracts, the ecosystem also interacts with third-party DEX contracts and pool accounts.

Current WAO liquidity exists across Ethereum and Solana through Uniswap, Balancer and Meteora. These pools are not custom WAODAO smart contracts, but they are important public on-chain infrastructure for WAO price discovery, Friendly Pools and market access.

Examples include:

* WAO / ETH on Uniswap;
* WAO / WBTC on Uniswap;
* WAO / UNI on Uniswap v4;
* WAO / LINK on Balancer;
* WAO / HOT on Uniswap v4;
* WAO / SOL on Meteora;
* WAO / BABA on Meteora;
* WAO / Simulation on Meteora.

Some DEX entries are represented by contract addresses, while others are represented by pool identifiers, position IDs or Solana pool accounts depending on the protocol architecture.

### Security approach

WAODAO’s security approach is based on four principles:

1. Use proven standards where possible, such as OpenZeppelin-based ERC-20 and ERC-721 contracts.
2. Use established treasury infrastructure such as Safe / Gnosis Safe.
3. Keep core contract logic simple and avoid unnecessary custom mechanisms.
4. Make important on-chain addresses public, so users, investors and AI agents can independently verify token deployments, NFT provenance and liquidity routes.

No blockchain infrastructure is completely risk-free. Smart contracts, bridges, wallets, DEX pools, marketplaces and multisig operations all carry different types of technical and operational risk. WAODAO treats security as an ongoing process and expands to new infrastructure only when it adds clear utility to the ecosystem.


---

# 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://waodao.gitbook.io/docs/development/smart-contracts.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.
