Update hardhat and foundry information (#57)

* Update Hardhat verification documentation for v3

* Update Foundry verification documentation to newest version

* Reduce Solidity metadata Foundry and Hardhat sections to only describing where to find metadata

* Add note about Etherscan getting default with api key

* Reword Foundry support

---------

Co-authored-by: Kaan Uzdoğan <kaanuzdogan@gmail.com>

Author: manuelwedler

docs/5. Verify on Sourcify/4. Verify via Hardhat.md

@@ -4,26 +4,55 @@ slug: /verify-via-hardhat
 title: Verify via Hardhat
 ---
 
-The Hardhat plugin [@nomicfoundation/hardhat-verify](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify#verifying-on-sourcify) has official Sourcify support.
+:::info Hardhat v3
+This page covers **Hardhat v3**. For Hardhat v2, see the [hardhat-verify plugin docs](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify#verifying-on-sourcify).
+:::
 
-Sourcify verification is enabled by default in recent plugin versions.
+The [`@nomicfoundation/hardhat-verify`](https://hardhat.org/docs/plugins/hardhat-verify) plugin has built-in Sourcify support. No configuration is needed — Sourcify verification runs automatically when you run `hardhat verify`.
 
-You only need explicit config if you want to set custom endpoints (for example when using your own Sourcify instance):
+## Setup
 
-```js title="hardhat.config.js"
-sourcify: {
-  enabled: true, // Optional, true by default
-  // Optional: specify a different Sourcify server
-  apiUrl: "https://sourcify.dev/server",
-  // Optional: specify a different Sourcify repository
-  browserUrl: "https://repo.sourcify.dev",
-}
+The plugin comes pre-installed in Hardhat v3 template projects. To add it manually:
+
+```bash
+npm install --save-dev @nomicfoundation/hardhat-verify
+```
+
+```typescript title="hardhat.config.ts"
+import { defineConfig } from "hardhat/config";
+import hardhatVerify from "@nomicfoundation/hardhat-verify";
+
+export default defineConfig({
+  plugins: [hardhatVerify],
+});
 ```
 
-After deploying your contracts you can verify on Sourcify with:
+## Verification
+
+After deploying, verify on all services (Etherscan, Blockscout, Sourcify) with:
 
-```bash title="Verify a contract"
+```bash
 npx hardhat verify --network mainnet DEPLOYED_CONTRACT_ADDRESS
 ```
 
-The Hardhat plugin currently uses Sourcify's legacy verification endpoints internally. The `/v2` and `/v3` API endpoints documented elsewhere apply to direct API integrations, not to this Hardhat command.
+To verify on Sourcify only:
+
+```bash
+npx hardhat verify sourcify --network mainnet DEPLOYED_CONTRACT_ADDRESS
+```
+
+## Custom Sourcify instance
+
+If you're running your own Sourcify instance, configure the endpoints under `verify`:
+
+```typescript title="hardhat.config.ts"
+export default defineConfig({
+  plugins: [hardhatVerify],
+  verify: {
+    sourcify: {
+      // Specify a different Sourcify server here
+      apiUrl: "https://sourcify.dev/server",
+    },
+  },
+});
+```

docs/5. Verify on Sourcify/5. Verify via Foundry.md

@@ -4,30 +4,31 @@ slug: /verify-via-foundry
 title: Verify via Foundry
 ---
 
-Foundry natively supports Sourcify verification. You can verify contracts with the additional verify flags in Forge.
+Foundry natively supports Sourcify verification. Sourcify is the **default verifier** in Forge if you don't add an Etherscan API key. If you added a key you should set the verifier explicitly `--verifier sourcify`.
 
-(This is still using the legacy Sourcify API)
+## Deploy and verify
 
-```bash title="Deploy and verify a contract"
+```bash
 forge create --rpc-url <your_rpc_url> \
   --constructor-args "ForgeUSD" "FUSD" 18 1000000000000000000000 \
   --private-key <your_private_key> \
   src/MyToken.sol:MyToken \
   --verify \
-  --verification-provider sourcify
-  --verifier-url https://localhost:5555 # optional, defaults to https://sourcify.dev/server/
+  --verifier sourcify
 ```
 
-```bash title="Verify an already deployed (and compiled) contract"
+## Verify an existing contract
+
+```bash
 forge verify-contract 0x55f7d4279CE387067f12561e7E0c194f5186cFba \
   src/MyToken.sol:MyToken \
-  --chain-id 11155111 \
+  --chain 11155111 \
   --verifier sourcify
-  --verifier-url https://localhost:5555 # optional, defaults to https://sourcify.dev/server/
 ```
 
-```bash title="Check if a contract is verified"
-forge verify-check 0x55f7d4279CE387067f12561e7E0c194f5186cFba \
-  --chain-id 11155111 \
+## Check verification job status
+
+```bash
+forge verify-check 64f6f3bb-2b93-40ec-b6e8-b6e90510e6b0 \
   --verifier sourcify
 ```

docs/6. Sourcify in depth/2. Solidity metadata.md

@@ -54,47 +54,12 @@ To have the metadata in the ouput of the compilation with Solidity's [standard J
 
 ### Foundry
 
-Foundry stores the contract compilation outputs to `out/CONTRACT_NAME` folder. The `.json` file contains the metadata of the contract under `"rawMetadata"` and `"metadata"` fields. However you don't need to extract the metadata manually for verification.
+Foundry stores the contract compilation outputs to `out/CONTRACT_NAME` folder. The `.json` file contains the metadata of the contract under `"rawMetadata"` and `"metadata"` fields.
 
 You can use the `forge verify-contract` command to verify a contract. See [Foundry verification](/docs/verify-via-foundry) for more details.
 
-Simply drag and drop the output `.json` file of the contract you want to verify to the [sourcify.dev](https://sourcify.dev) UI or provide it as the metadata file to the [API](/docs/api).
-
 ### Hardhat
 
-You can use the native Hardhat [verify plugin](https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify#verifying-on-sourcify) to verify your contracts. See [Hardhat verification](/docs/verify-via-hardhat) for more details.
-
-Hardhat stores the outputs of the compilations under the `artifacts/build-info/` folder inside the project. The `.json` file under the folder contains the [Standard JSON Input-Output](https://docs.soliditylang.org/en/latest/using-the-compiler.html#compiler-input-and-output-json-description) of the Solidity compiler for all contracts.
-
-Since [v2.6.8](https://github.com/nomiclabs/hardhat/releases/tag/hardhat%402.6.8), Hardhat outputs the metadata files of each contract by default under the JSON's `.output.contracts.<contract-path>.<contract-name>.metadata` field. You don't have to extract the metadata manually. To verify via the Hardhat output you can provide the JSON containing the artifacts to Sourcify via UI or API. See [Hardhat verification](/docs/verify-via-hardhat) for more details. If the file is too large, try zippping it and uploading the zip file.
-
-### Hardhat - earlier than v2.6.8
-
-If you use an earlier version of Hardhat than 2.6.8 you can modify the `hardhat-config.js` manually to output metadata inside the `build-info/` file:
-
-```js
-// hardat-config.js
-module.exports = {
-  ...
-  solidity: {
-    settings: {
-      version: ...,
-      optimizer: {...},
-      outputSelection: {
-        "*": {
-          "*": [
-            "abi",
-            "evm.bytecode",
-            "evm.deployedBytecode",
-            "metadata", // <-- add this
-            ...
-          ]
-        },
-      },
-    },
-  },
-  ...
-};
-```
+Hardhat stores the outputs of the compilations under the `artifacts/build-info/` folder inside the project. The `.json` files under the folder contain the [Standard JSON Output](https://docs.soliditylang.org/en/latest/using-the-compiler.html#output-description) of the Solidity compiler for all contracts. Hardhat outputs the metadata files of each contract by default under the JSON's `output.contracts.<contract-path>.<contract-name>.metadata` field.
 
-In theory, if you haven't changed any of the compilation settings, it should result in the same metadata file and you should get an exact match. Otherwise you will be able to get a match only.
+You can use the native Hardhat [verify plugin](https://hardhat.org/docs/plugins/hardhat-verify) to verify your contracts. See [Hardhat verification](/docs/verify-via-hardhat) for more details.