> ## Documentation Index > Fetch the complete documentation index at: https://hedera-0c6e0218-automation-consensus-node-release-notes.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain. > Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names. > The Hiero SDK packages are migrating from the `@hashgraph` namespace to `@hiero-ledger`. Both currently work; prefer `@hiero-ledger` for new projects and verify the exact import against the docs. > Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural. > Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case. > For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias". # Import from Etherscan > Import a contract verified on an Etherscan instance or a service with Etherscan-alike API ## OpenAPI ````yaml /smart-contract-verification-api.yaml post /v2/verify/etherscan/{chainId}/{address} openapi: 3.1.0 info: version: 2.1.0 title: Sourcify APIv2 description: >- Welcome to the Sourcify's APIv2. Important differences between the deprecated legacy API and the new APIv2: - **Ticketing**: The verfication requests resolve into tickets/verification jobs. - Previously the verification happened during the HTTP request, which resulted in timeouts if compilation took longer - **Standard JSON as default**: In the current design we take the standard JSON format as our main verification endpoint. Other methods such as "multi-file" or "single-file" should be handled by frontends or tooling to format into std-json. We still support verification with metadata at `/v2/verify/metadata`. - **Lean API**: We keep the number of endpoints minimal compared to v1. We won't have a session API. - **Detailed contract response**: Prev. we only returned contract files of a contract. Now we can return details at `/contract/{chainId}/{address}`. By submitting source code for verification, you grant Sourcify (and the Argot Collective) a non-exclusive, worldwide, irrevocable, royalty-free licence to reproduce, store, and publicly display the submitted source code for the purposes of verification, archival, and public inspection. license: name: MIT url: https://github.com/argotorg/sourcify/blob/master/LICENSE contact: name: Sourcify url: https://sourcify.dev email: hello@sourcify.dev servers: - url: https://sourcify.dev/server description: Production server security: [] tags: - name: Contract Lookup description: API v2 - Tools and endpoints for looking up contract information - name: Verify Contracts description: API v2 - Submit a contract for verification - name: Verification Jobs description: API v2 - Check the status of a verification job - name: Other description: General server endpoints paths: /v2/verify/etherscan/{chainId}/{address}: post: tags: - Verify Contracts summary: Import from Etherscan description: >- Import a contract verified on an Etherscan instance or a service with Etherscan-alike API operationId: import-from-etherscan parameters: - name: chainId in: path description: The chainId number of the EVM chain required: true schema: type: string pattern: ^\d+$ minLength: 1 maxLength: 20 example: '11155111' - name: address in: path description: >- Contract's 20 byte address in hex string with the 0x prefix. Case insensitive. required: true schema: type: string pattern: (\b0x[a-fA-F0-9]{40}\b) minLength: 42 maxLength: 42 example: '0x2738d13E81e30bC615766A0410e7cF199FD59A83' requestBody: description: '' content: application/json: schema: type: object properties: apiKey: type: string description: >- API key to use when importing from the Etherscan instance or Etherscan-alike API. responses: '202': description: >- Successfully submitted the verification. The server started to process the verification. You can follow the verification status via the returned `verificationId` at `GET /v2/verify/{verificationId}` content: application/json: schema: type: object title: VerificationJob properties: verificationId: type: string format: uuid required: - verificationId '400': description: Bad request from the client content: application/json: schema: type: object title: GenericErrorResponse properties: customCode: type: string description: A string token to indicate the reason of the error example: unsupported_chain message: type: string description: The reasoning of the error example: >- The chain with chainId 3153212 is not supported for verification errorId: type: string format: uuid required: - customCode - message - errorId examples: - customCode: unsupported_chain message: The chain with chainId 9429413 is not supported errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 examples: Example 1: value: customCode: unsupported_chain message: The chain with chainId 9429413 is not supported errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 '429': description: You've reached the API key limit for the Etherscan key. content: application/json: schema: type: object title: GenericErrorResponse properties: customCode: type: string description: A string token to indicate the reason of the error example: unsupported_chain message: type: string description: The reasoning of the error example: >- The chain with chainId 3153212 is not supported for verification errorId: type: string format: uuid required: - customCode - message - errorId examples: - customCode: unsupported_chain message: The chain with chainId 9429413 is not supported errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 examples: Example 1: value: customCode: etherscan_limit message: Etherscan API key limit reached errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 '500': description: '' content: application/json: schema: type: object title: GenericErrorResponse properties: customCode: type: string description: A string token to indicate the reason of the error example: unsupported_chain message: type: string description: The reasoning of the error example: >- The chain with chainId 3153212 is not supported for verification errorId: type: string format: uuid required: - customCode - message - errorId examples: - customCode: unsupported_chain message: The chain with chainId 9429413 is not supported errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 examples: Example 1: value: customCode: internal_error message: Something went wrong errorId: 1ac6b91a-0605-4459-93dc-18f210a70192 ````