For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Company
Open App
Introduction Chains RPC NodesChangelog
Introduction Chains RPC NodesChangelog
    • Overview
  • Getting Started
    • Deploy a Testnet
  • Supported Stacks
    • OP Stack
    • Arbitrum Orbit
    • Agglayer CDK
  • Guides
    • Customize Branding
    • Customize Domains
    • Get Testnet ETH
    • Get a Bridge UI
    • Bridge CGT (Arbitrum)
    • Trace Transactions
    • Verify Smart Contracts
    • Share Chain Info
    • Permission your Rollup
    • Indexing your Chain
  • Integrations
    • Bridged USDC
    • Blockscout
    • Bundler
LogoLogo
Company
Open App
On this page
  • FAQ
  • Why is contract verification failing when I deploy using CREATE2, and how can I resolve it?
Guides

Smart Contract Verification

Was this page helpful?
Previous

Share Chain Info

Next
Built with

Contract verification will be available within 15 minutes after network launch.

Conduit comes with a Blockscout instance, and you can verify against it with the url:

https://explorer-[your_network_id].t.conduit.xyz/api\?

Note: See this foundry issue for why you need to include \?

$forge verify-contract [address] [contract] --verifier=blockscout --verifier-url=https://explorer-[your_network_id].t.conduit.xyz/api\?

FAQ

Why is contract verification failing when I deploy using CREATE2, and how can I resolve it?

Deploying a contract with CREATE2 generates a deterministic address through an internal transaction, ensuring the same address is created regardless of the deployment’s origin. Internal indexing is highly resource-intensive. As a result, we’ve disabled internal transaction indexing in Blockscout, meaning contracts deployed via CREATE2 won’t be automatically indexed.

To resolve this, simply visit the contract address after deployment. Blockscout will fetch the contract from the RPC, recognize it, and allow verification to proceed. If needed, we can enable internal transaction indexing, but this would involve discussing pricing implications due to increased costs associated with higher growth.