docs

Author: skudasov

book/src/SUMMARY.md

@@ -13,6 +13,7 @@
     - [Creating your own components](./developing/developing_components.md)
     - [Fork Testing](./framework/fork.md)
     - [Quick Contracts Deployment](./framework/quick_deployment.md)
+    - [Verifying Contracts](./framework/verify.md)
     - [NodeSet with External Blockchain]()
     - [CLI](./framework/cli.md)
     - [Configuration](./framework/configuration.md)

book/src/framework/observability/blockscout.md

@@ -25,9 +25,4 @@ ctf bs -r http://host.docker.internal:8555 d
 Blockscout isn’t ideal for local, ephemeral environments, as it won’t re-index blocks and transactions on test reruns. The easiest approach is to set up Blockscout first, initialize the test environment, switch to the [cache](../components/caching.md) config, and run tests without restarting RPC nodes. 
 
 Otherwise, use `ctf bs r` each time you restart your test with a fresh docker environment.
-</div>
-
-<div class="warning">
-
-Blockscout integration is still WIP, for now Blockscout reads only one node that is on `:8545`, all our blockchain implementation expose this port by default.
-</div>
+</div>

book/src/framework/verify.md

@@ -0,0 +1,16 @@
+# Verifying Contracts
+
+Check out our [example](https://github.com/smartcontractkit/chainlink-testing-framework/blob/main/framework/examples/myproject/verify_test.go) of programmatically verifying contracts using `Blockscout` and `Foundry`. You'll need to provide:
+
+- The path to your Foundry directory
+- The path to the contract
+- The contract name
+
+```golang
+		err := blockchain.VerifyContract(blockchainComponentOutput, c.Addresses[0].String(),
+			"example_components/onchain",
+			"src/Counter.sol",
+			"Counter",
+		)
+		require.NoError(t, err)
+```

framework/.changeset/v0.3.1.md

@@ -1,2 +1,3 @@
-- Use docker cmd instead of testcontainers
+- Use docker cmd for building instead of testcontainers-go
 - Add "CHAINLINK_IMAGE" flag to override NodeSet image
+- Add Go wrapper for Blockscout verification (foundry)