Parex Network
Block ExplorerCommunityParex NetworkDAO
  • 🦝Parex Network Docs
  • Welcome
    • 🚩Quick Start
      • Parex Network in a nutshell
      • Connect to Mainnet and Testnet
      • Deploy and verify a contract
        • Deploy with Remix IDE
          • ERC-20 smart contract
        • Deploy with thirdweb
        • Verify with Parex Block Explorer
      • Run a Parex Chain Node
      • Become a Validator
        • Run a Validator node
        • Authorization of Other Validators
        • nametag for Validator
        • Validator slashing
        • Validator Locked
      • Parex Halving
  • How we Work
    • 📖Learn
      • About Parex Network
        • Tokenomics
        • Parex Networks Labs
      • Parex Bridge
        • How to bridge PRX PEP20 to BEP20
        • How to bridge PRX BEP20 to PEP20
      • Staking on Parex Chain
        • Locked Stake your PRX on dAPP
        • Unlocked Stake your PRX on dAPP
        • Staking Rewards
        • Staking PRX from your Ledger
      • Become a Validator
        • Run a Validator node
        • Authorization of Other Validators
        • nametag for Validator
        • Validator slashing
        • Validator Locked
      • Glossary
        • Blockchain
        • Consensus mechanisms
        • Governance
        • Validator
        • Staking
        • Wallet
        • PEP-20
        • Wrapped PRX (wPRX)
        • Dead Contract Wallet
      • Parex Halving
  • For Developers
    • 💻Develop
      • Basics
        • Use MetaMask
          • Install MetaMask
          • Link Parex Testnet to MetaMask
          • Link Parex Chain to MetaMask
        • Connect to Parex Chain
          • Connect using RPC
          • Run a Parex Chain Node
          • Use a hardware wallet
        • Block Explorer
        • Parex Testnet Faucets
          • Obtain testnet tokens
          • Obtain TPRX with Parex Testnet Faucet
        • Obtain wPRX or PRX
          • PRX to wPRX
          • wPRX to PRX
        • Deploy and verify a contract
          • Deploy with Remix IDE
            • ERC-20 smart contract
          • Deploy with thirdweb
          • Verify with Parex Block Explorer
        • Tips & Tricks
  • For Community
    • 🫂Community
  • information
    • 🗺️Roadmap
    • ♻️Doc updates
Powered by GitBook
On this page
  • Steps
  • Solidity (Flattened source code)
  • Solidity (Standard JSON input)
  • Vyper Contract
  • Troubleshooting
  • Verification in a dev environment

Was this helpful?

  1. For Developers
  2. Develop
  3. Basics
  4. Deploy and verify a contract

Verify with Parex Block Explorer

PreviousDeploy with thirdwebNextTips & Tricks

Last updated 1 year ago

Was this helpful?

Verifying your deployed contract using flattened source code, JSON input, Sourcify and more.

Once verified, a smart contract or token contract's source code becomes publicly available and verifiable, creating transparency and trust.

We are here reproducing part of their .

Verification is available for both Solidity and Vyper contracts. Currently, there are 6 methods for verification using the Parex Blocscan UI.

To learn more about the smart contract verification Rust microservice and verification algorithm .

Steps

  1. Once the code is deployed, you can view the transaction in detail on the .

  1. Go to the Verify contract page (Other -> Verify contract)

  1. Enter in the contract address you received during deployment. The dropdown will show you several available verification options. Select the one you would like to use and continue.

  • Solidity (Multi-part files)

  • Vyper (Multi-part files)

  • Vyper (Standard JSON input)

Solidity (Flattened source code)

INFORMATION

To verify your smart contract, keep the following details handy:

  • Contract Name

  • Compiler

  • EVM version

  • Optimisation

The following table explains New Smart Contract Verification form in detail.

Parameter
Description

Contract Address

The 0x address supplied on contract creation (added above)

Is Yul contract

Select if the contract is coded in Yul for efficiency.

Include Nightly Builds

Select if you want to show nightly builds.

Compiler

Derived from the first line in the contract pragma solidity X.X.X. Use the corresponding compiler version rather than the nightly build.

EVM Version

Optimization Enabled

If you enabled optimization during compilation, select and enter the run value. 200 is the Solidity Compiler default value. Only change if you changed this value while compiling.

Enter the Solidity Contract Code

Add Contract Libraries

Enter the name and 0x address for any required libraries called in the .sol file. You can add multiple contracts with the "+" button.

Click the Verify and Publish button.

If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called Read Contract. The contract name will now appear in BlockScout with any transactions related to your contract.

Solidity (Standard JSON input)

  1. Include nightly builds. You can choose Yes or No depending on your compiler.

  2. Compiler. Choose the compiler version used to compile your smart contract. If you selected yes for nightly builds, use the compiler version rather than the build.

Click the Verify & publish button and wait for the response.

Vyper Contract

  1. Contract Name: Name assigned to the contract.

  2. Compiler: Select the compiler version used in the source code.

  3. Contract Code: Copy and paste the contract code

  4. Click the Verify and Publish button.

If all goes well, you will see a checkmark ✅ next to Code in the code tab, and an additional tab called Read Contract. The contract name will now appear in BlockScout with any transactions related to your contract.

Troubleshooting

If you receive the dreaded There was an error compiling your contract message this means the bytecode doesn't match the supplied sourcecode. Unfortunately, there are many reasons this may be the case. Here are a few things to try:

  1. Double check the compiler version is correct.

Check all version digits - for example 0.5.1 is different from 0.5.10

  1. Check that an extra space has not been added to the end of the contract. When pasting in, an extra space may be added. Delete this and attempt to recompile.

  2. Copy, paste, and verify your source code in Remix. You may find some exceptions here.

Verification in a dev environment

Feel free to explore the Block Explorer further!

Solidity (

Solidity ()

)

Select the correctif known, otherwise use default.

You may need to flatten your solidity code if it utilizes a library or inherits dependencies from another contract. We recommend or the .

.

Standard Input JSON. Upload your Standard Input JSON file. File should follows solidity and all the sources must be in Literal Content format, not a URL.

EVM Version: Select the correctif known, otherwise use default.

The supports BlockScout. You can also choose to use the to verify with Sourcify from your hardhat environment.

💻
More information on JSON input is available here
format
EVM version
Hardhat verification plugin
Sourcify plugin
Flattened source code)
Standard JSON input
Vyper (Contract
EVM version
hardhat
POA solidity flattener
documentation for contract validation
see this page for developers
Parex Block Explorer