Actions3
Overview
This node interacts with the Etherscan API to retrieve information about Ethereum smart contracts. Specifically, for the "Get Contract Creator and create Tx Hash" resource with the "Get" operation, it fetches the deployer address and the transaction hash of contract creation for up to five contract addresses at a time. This is useful for blockchain developers, auditors, or analysts who want to trace the origin of smart contracts by identifying who deployed them and the transaction details of their deployment.
Practical examples include:
- Verifying the creator of a smart contract to ensure authenticity.
- Auditing contract deployment transactions for security reviews.
- Tracking multiple contracts' origins in batch for portfolio analysis.
Properties
| Name | Meaning |
|---|---|
| Address(es) | One or more contract addresses (Ethereum addresses) separated by commas, up to 5 addresses. |
Output
The node outputs JSON data containing details about each provided contract address, including:
- The deployer address (creator) of the contract.
- The transaction hash corresponding to the contract creation.
This output allows users to programmatically access and use the contract creator and deployment transaction information.
The node does not output binary data.
Dependencies
- Requires an API key credential for the Etherscan API to authenticate requests.
- The node sends HTTP GET requests to the Etherscan API endpoint:
https://api.etherscan.io/api. - No additional external dependencies beyond the Etherscan API and proper API key configuration in n8n.
Troubleshooting
Common issues:
- Providing more than 5 contract addresses may result in errors or incomplete data since the API limits to 5 addresses per request.
- Invalid or malformed Ethereum addresses will cause the API to return errors or empty results.
- Missing or incorrect API key credentials will lead to authentication failures.
Error messages:
- Authentication errors indicating invalid API key: Ensure the API key credential is correctly set up in n8n.
- Rate limit exceeded errors: The Etherscan API enforces rate limits; consider upgrading your API plan or adding delays between requests.
- Invalid address format errors: Verify that all contract addresses are valid Ethereum addresses and properly comma-separated.