Saakuru Source
HomeExplorerPortalX official
  • Welcome to Saakuru Source
  • Introducing the Saakuru Labs
    • Web3 Gaming Industry
    • Web3 Game Development Business
    • Web3 Game Developer Stack
  • Saakuru (SKR) Token
    • Trade
    • Tokenomics
    • Developer Layer
    • DeFi Layer
    • Governance Layer
    • Lossless Protection Layer
    • Transparency Portal
    • Contracts
  • Saakuru Games Incubation Program (SGIP)
  • Saakuru Games Publishing Program (SGPP)
  • Saakuru Blockchain
    • The Mission
      • The Problems
      • The Solution
      • The On-Chain Effect. Web2 -> Web3
    • Explorer
    • Architecture
    • Security
    • Scam Resistance
    • Gasless Transactions
    • Environments
      • Verify Contract on Saakuru Explorer
    • Developer References
    • Adding Network to Wallet
      • Saakuru -> Saakuru App
      • Saakuru -> MetaMask
      • Saakuru -> Trust Wallet
  • Saakuru Game Developer Suite
    • Self-service Portal
    • Saakuru Blockchain
    • Wallet SDK - The Seamless Backend Wallet Solution for Games
      • FAQ: How to Choose the Right Web3 Wallet for Your Game
    • Tokens SDK - The Ultimate Asset Management Solution for Web3 Games
      • FAQ: Web3 Tokens in Gaming – Everything Game Studios Need to Know
    • Characters SDK: Morfable NFT Characters for Immersive Web3 Gaming
      • FAQ: How NFTs Work in Web3 Gaming and the Role of Charact3rs Service
    • Market SDK: Seamless In-Game Marketplace Integration (Coming 2025)
    • Collect Service: Simplifying In-Game Event Data for Web3 Gaming
    • Pricing
  • Roadmap
  • Investments to Games
  • Core Team
  • Ecosystem partners
  • Games
  • Open Job Positions
  • Appendix
    • Official Links
    • Disclaimer
    • Legal Notice
    • Marketing Kit
Powered by GitBook
On this page
  • Contract Verification
  • Configuring the Hardhat Settings File
  1. Saakuru Blockchain
  2. Environments

Verify Contract on Saakuru Explorer

PreviousEnvironmentsNextDeveloper References

Contract Verification

Verifying a contract enables public access to the code of the deployed contract. Saakuru Protocol utilizes , which is a prominent open-source explorer. Therefore, it's essential to follow its specifications. Please refer to the for guidance. We will provide you with an exact example of the configuration.

Configuring the Hardhat Settings File

I will present you with a practical example of the config file (hardhat.config.js) for our mainnet case. Please note that it's not necessary to login and generate an apiKey; any value is acceptable.

const config = {
  ...
  networks: {
    saakuruTestnet:{
      url: 'https://rpc-testnet.saakuru.network',
      chainId: 247253,
      accounts: [`0x${privateKey}`],
      live: true,
      saveDeployments: true,
      gasPrice: 0,
    },
    saakuruMainnet:{
      url: 'https://rpc.saakuru.network',
      accounts: [`0x${privateKey}`],
      chainId: 7225878,
      live: true,
      saveDeployments: true,
      gasPrice: 0,
    },
  },
  etherscan: {
    apiKey: {
      saakuruMainnet: ‘’,
      saakuruTestnet: ‘’,
    },
    customChains: [
      {
        network: ‘saakuruMainnet’,
        chainId: 7225878,
        urls: {
          apiURL: ‘https://explorer.saakuru.network/api’,
          browserURL: ‘https://explorer.saakuru.network/’,
        },
      },
      {
        network: ‘saakuruTestnet’,
        chainId: 247253,
        urls: {
          apiURL: ‘https://explorer-testnet.saakuru.network/api’,
          browserURL: ‘https://explorer-testnet.saakuru.network/’,
        },
      },
    ],
  },`
  ...
}
Blockscout
Blockscout documentation