ZVQ Contract Verification
SMART CONTRACT TRANSPARENCY

Verify source against deployed bytecode.

This guide exposes only the public verification capabilities reported by the Explorer. Supported compilers and verification modes must be read from the live verification configuration rather than assumed.

Verification service

Live capability probe:

GET /api/v2/smart-contracts/verification/config
Checking
Reading live public configuration…

Verified contract feed

Discover contracts already carrying public verification evidence.

GET /api/v2/smart-contracts
Open Verified Contracts

Recommended verification flow

  1. Deploy the contract and wait until its transaction and address are indexed.
  2. Open the contract address in Explorer and confirm bytecode is present.
  3. Read the live verification configuration to determine supported compiler/language/method combinations.
  4. Submit source, compiler settings and constructor metadata only through supported public verification mechanisms.
  5. After success, re-open the address and confirm source/ABI visibility.
  6. Use the verified contract page as the public reference for integrations.
Never submit secrets: source verification does not require a wallet seed phrase, private key, keystore password, validator credential, treasury credential, or signing secret. If any workflow requests those values, stop.

Before verification

Preserve the exact compiler version, optimizer state/runs, source tree, library addresses and constructor arguments used for deployment. Bytecode mismatch is commonly caused by a build setting mismatch rather than an Explorer failure.

After verification

Check the public address detail for source code, ABI, contract name and available read/write panels. Treat write operations as wallet-signed transactions and review the target address, method and value before confirmation.