Files
proxmox/docs/archive/historical/CHAINID_138_BLOCKSCOUT_INTEGRATION.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
2026-01-06 01:46:25 -08:00

4.2 KiB

ChainID 138 Blockscout Integration Summary

Date: $(date)
Purpose: Summary of Blockscout integration and configuration for ChainID 138
Status: Complete


Overview

ChainID 138 uses Blockscout (self-hosted) as its block explorer. This document summarizes all Blockscout-related configurations and documentation updates.


Completed Updates

1. API Keys Documentation

File: docs/CROSS_CHAIN_BRIDGE_ADDRESSES.md

  • Added ChainID 138 (Blockscout) to the API Keys section
  • Included Blockscout URL: https://explorer.d-bis.org
  • Added API endpoint: https://explorer.d-bis.org/api
  • Noted that no API key is required (self-hosted instance)
  • Added reference to verification guide

2. Contract Verification Guide

File: docs/BLOCKSCOUT_VERIFICATION_GUIDE.md (NEW)

  • Created comprehensive Blockscout verification guide
  • Documented verification methods (Foundry script, manual, foundry.toml)
  • Included verification examples with constructor arguments
  • Added troubleshooting section
  • Documented manual verification via Blockscout UI

3. Deployment Documentation Updates

File: docs/CONTRACT_DEPLOYMENT_GUIDE.md

  • Updated deployment examples with Blockscout verification flags
  • Added proper --verifier blockscout and --verifier-url flags
  • Clarified Blockscout verification requirements

File: docs/SOURCE_PROJECT_CONTRACT_DEPLOYMENT_INFO.md

  • Updated Foundry configuration notes
  • Clarified Blockscout usage instead of Etherscan
  • Added verification command examples

📋 Configuration Details

Block Explorer Information

  • Name: Blockscout (Self-hosted)
  • URL: https://explorer.d-bis.org
  • API Endpoint: https://explorer.d-bis.org/api
  • Chain ID: 138
  • API Key: Not required

Foundry Verification Configuration

For Foundry contract verification, use:

--verifier blockscout --verifier-url https://explorer.d-bis.org/api

Or configure in foundry.toml:

[etherscan]
chain138 = { 
  url = "https://explorer.d-bis.org/api",
  verifier = "blockscout"
}

Primary References

  1. Blockscout Verification Guide: docs/BLOCKSCOUT_VERIFICATION_GUIDE.md

    • Complete guide for verifying contracts on ChainID 138
    • Verification methods and examples
    • Troubleshooting tips
  2. Cross-Chain Bridge Addresses: docs/CROSS_CHAIN_BRIDGE_ADDRESSES.md

    • API Keys section includes ChainID 138 Blockscout info
    • Reference to verification guide
  3. Contract Deployment Guide: docs/CONTRACT_DEPLOYMENT_GUIDE.md

    • Updated with Blockscout verification examples
  4. Source Project Deployment Info: docs/SOURCE_PROJECT_CONTRACT_DEPLOYMENT_INFO.md

    • Foundry configuration notes
    • Blockscout verification setup

📝 Quick Reference

Verify Contract After Deployment

forge verify-contract \
  <CONTRACT_ADDRESS> \
  <CONTRACT_NAME> \
  --chain-id 138 \
  --rpc-url https://rpc-core.d-bis.org \
  --verifier blockscout \
  --verifier-url https://explorer.d-bis.org/api \
  --compiler-version <VERSION>

View Contract on Explorer

  • Contract Page: https://explorer.d-bis.org/address/<CONTRACT_ADDRESS>
  • Manual Verification: Navigate to contract → "Verify & Publish" tab

Blockscout API Endpoints

  • API Base: https://explorer.d-bis.org/api
  • Contract Info: GET /api/v2/smart-contracts/<ADDRESS>
  • Verification: POST /api/v2/smart-contracts/<ADDRESS>/verification

🎯 Next Steps

With Blockscout integration complete:

  1. Documentation: All Blockscout-related documentation updated
  2. Verification Guide: Comprehensive guide created
  3. API Keys: ChainID 138 added to API keys section
  4. Deployment Examples: Updated with Blockscout verification

Ready for contract deployment and verification on ChainID 138!


📚 Additional Resources


Last Updated: $(date)
Status: All Blockscout integration tasks complete