add-explorer

Integrate a blockchain explorer API into diffyscan for contract verification.

142|19|Updated Apr 22, 2023
One-click install
npx skills add https://github.com/lidofinance/diffyscan --skill add-explorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-explorer
Source: https://github.com/lidofinance/diffyscan/tree/main/.claude/skills/add-explorer
Command: npx skills add https://github.com/lidofinance/diffyscan --skill add-explorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers to extend diffyscan by integrating a new blockchain explorer API for contract verification.

Core Features & Use Cases

  • Provides a structured approach for adding a new explorer, including endpoint discovery, dispatcher routing, fetcher implementation, and payload normalization.
  • Enables end-to-end testing and config setup to validate contract name, source code, compiler version, and metadata across explorers.
  • Offers a repeatable process that ensures consistent integration with minimal code changes for existing explorers.

Quick Start

Follow the guide to implement a new explorer fetcher, update the dispatcher, and create a config sample plus tests.

Frequently Asked Questions about add-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new blockchain explorer API to diffyscan for contract verification?

To add a new blockchain explorer to diffyscan, you implement a dedicated fetcher for endpoint discovery, update the explorer dispatcher routing, build solc inputs from explorer data, and create a config sample with tests to verify contract metadata.

What steps are required to integrate a new explorer fetcher into a blockchain verification tool?

Integrating a new explorer fetcher requires updating the dispatcher routing, implementing payload normalization, building solc inputs from the explorer data, and creating end-to-end tests to validate contract name, source code, and compiler version across configurations.

Does diffyscan support token-based access when fetching contract source code from explorers?

Yes, when adding a new explorer integration, you can implement a dedicated fetcher that includes optional token-based access to authenticate API requests for retrieving contract source code and related metadata.

How do I test contract verification after extending diffyscan with a new explorer API?

You test contract verification by creating end-to-end tests that validate the fetched contract name, source code, compiler version, and related metadata against expected values across different explorer configurations.

What is payload normalization when building solc inputs from blockchain explorer data?

Payload normalization is the process of transforming raw contract data fetched from a blockchain explorer API into the standardized format required to build solc inputs for accurate contract verification.

Why do I need to update the explorer dispatcher when adding a new blockchain explorer?

Updating the explorer dispatcher is necessary to correctly route contract verification requests to the newly integrated explorer fetcher, ensuring the diffyscan tool queries the appropriate blockchain API endpoint.