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

# Verification and source

## Where the source lives

* Repository: [github.com/polydash-labs/Polydash](https://github.com/polydash-labs/Polydash), MIT license.
* Deployed `.sol` sources under `src/` and `polypad/contracts/src/` match the verified deployments and are not edited in place. `forge fmt` ignores `src/**/*.sol` so formatting cannot change the metadata hash.
* Some NatSpec headers still read "DRAFT - not reviewed, not deployed". They are left unchanged on purpose, because editing them would change the metadata hash of verified code.
* The four NFT contracts (factory, curve factory, marketplace, token link) are deployed and verified, and their source is not in the repository.

## What "Sourcify match" means

Sourcify compares the published source against deployed bytecode.

* **Exact match.** Creation and runtime bytecode match, including the metadata hash.
* **Match.** Creation and runtime bytecode match, but the metadata hash does not, for example because the code was compiled with `bytecode_hash = none`.

Both are bytecode checks. **Neither is a review of what the code does.**

## Compiler settings

| Modules                                                                                | Compiler                                | EVM      |
| -------------------------------------------------------------------------------------- | --------------------------------------- | -------- |
| Staking V1 and V2, NFT staking, vesting, bonds, gated mints, treasury, tokenized funds | solc 0.8.24, optimizer 200 runs, via-IR | `paris`  |
| Floor vault, buybacks, Polypad launchpad                                               | solc 0.8.26, optimizer 200 runs, via-IR | `cancun` |

OpenZeppelin v5.0.2 and Uniswap v4-core v4.0.0 are included as submodules.

## Tests and checks in the repository

* Foundry unit, fuzz, invariant, and fork tests. Fuzz tests run 1,000 times by default and 5,000 times in CI.
* Fork tests read Robinhood Chain state and do not broadcast.
* CI runs an advisory Slither job. Slither findings and a green run are **not a review**, and they do not remove risk.
* A bytecode comparison script checks that locally compiled staking V2 code matches on-chain code.

## Reproduce a check

```bash
git clone --recursive https://github.com/polydash-labs/Polydash.git
cd Polydash
forge build
forge test
```

Fork tests need `FORK_RPC=https://rpc.mainnet.chain.robinhood.com` and `FOUNDRY_PROFILE=fork`.

## Report a problem

See [Report a vulnerability](https://polydash.gitbook.io/polydash-docs/security-and-risk/report-a-vulnerability.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://polydash.gitbook.io/polydash-docs/smart-contracts/verification-and-source.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
