> For the complete documentation index, see [llms.txt](https://docs.plume.org/plume/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plume.org/plume/developers/how-to-guides/how-to-verify-smart-contracts/verify-using-foundry.md).

# Verify using Foundry

## Verify your Contract

To verify your smart contract that is already deployed, refer the instructions in [Blockscout's Foundry Contract Verification](https://docs.blockscout.com/devs/verification/foundry-verification) page.&#x20;

Run the following command to verify on **Plume Testnet** for instance (switch the RPC and verifier URL to Mainnet to deploy on Plume Mainnet):

```sh
export PLUME_RPC_URL=https://testnet-rpc.plume.org
export VERIFIER_URL=https://testnet-explorer.plume.org/api/
export CONTRACT_ADDRESS=<your_contract_address>
export CONTRACT_PATH=<contract_file>:<contract_name>

forge verify-contract $CONTRACT_ADDRESS $CONTRACT_PATH \
    --rpc-url $PLUME_RPC_URL \
    --verifier blockscout \
    --verifier-url $VERIFIER_URL
```

{% hint style="warning" %}
Make sure to replace the details in the `<contract address>` and `<contract_file>:<contract_name>` with your contract details.
{% endhint %}

### Sample Output

```sh
Start verifying contract `0x4b98e3767DB95C5D30834E1261Ea4Caa96081160` deployed on 98867

Submitting verification for [src/RolexYachtMaster40.sol:RolexYachtMaster40] 0x4b98e3767DB95C5D30834E1261Ea4Caa96081160.
Submitted contract for verification:
        Response: `OK`
        GUID: `4b98e3767db95c5d30834e1261ea4caa9608116067b396ba`
        URL: https://testnet-explorer.plume.org/address/0x4b98e3767db95c5d30834e1261ea4caa96081160
```
