# Verify Source Code

Verifying source code with Remix on polyscan is a bit of an art.  I tried the official ETHERSCAN Verification plugin for Remix, but the plugin does not seem to be configurable for other chains.  I tried the regular imports which compile fine on remix `@openzeppelin...` but the import is not supported.  So then I tried the flattener plugin which did indeed do most of the leg work to flatten the solidity file, but the order was out of whack.

So to make everything really simple, I have created the flattened files for the NFT and bridge contracts.

* [atomicnft\_flat.sol](https://github.com/liquidapps-io/zeus-sdk/blob/master/boxes/groups/sample/atomictokenpeg/contracts/eth/atomicnft/atomicnft_flat.sol)
* [atomictokenpeg\_flat.sol](https://github.com/liquidapps-io/zeus-sdk/blob/master/boxes/groups/sample/atomictokenpeg/contracts/eth/atomictokenpeg/atomictokenpeg_flat.sol)

The same steps can be followed when it's time to confirm the atomictokenpeg contract.

Take the flattened file and select the single file selection and confirm the compiler type.


---

# Agent Instructions: 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.liquidapps.io/liquidapps-documentation/cross-chain-bridges/getting-started-with-liquidbridge/eosio-less-than-greater-than-evm-non-fungible-tokens/evm-side-setup/verify-source-code.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.