Actions27
- Contract Event Actions
- Contract Method Actions
- Prompt Actions
- Transaction Actions
- Wallet Actions
- X402 Request Actions
- Chain Actions
Contract Method → Execute Batch as Delegator
AI-generatedOverview
This node operation allows users to execute a batch of contract methods on an EVM blockchain on behalf of a delegator using the 1Shot API. It is useful for scenarios where multiple contract method calls need to be executed atomically or in a batch, with delegation capabilities. For example, a user can execute multiple token transfers or contract interactions in a single batch transaction, specifying the delegator's address or delegation details to authorize the execution.
Use Case Examples
- Executing multiple contract methods in a batch as a delegator to automate complex workflows.
- Performing batch token transfers or contract interactions on behalf of another user or entity using delegation.
Properties
| Name | Meaning |
|---|---|
| Contract Methods | A collection of contract methods to execute in the batch. Each contract method includes the method name or ID, parameters as a JSON object, and delegation details such as delegator address, delegation ID, or delegation data. |
| Wallet Name or ID | Select the wallet to use for executing the contract methods batch. |
| Additional Fields | Additional optional settings for the batch execution, such as atomic execution (all transactions must succeed or rollback), memo text, authorization list for ERC-7702, and gas limit. |
Output
JSON
json- The JSON response from the batch execution of contract methods as a delegator.
Dependencies
- 1Shot API
- An API key credential for 1Shot OAuth2 authentication
Troubleshooting
- Ensure only one of delegatorAddress, delegationId, or delegationData is provided per contract method to avoid conflicts.
- Verify that the wallet ID selected has the necessary permissions and funds to execute the batch.
- Check that the parameters JSON for each contract method is correctly formatted and matches the contract method's expected inputs.
- If the batch is set to atomic, any failure in one transaction will roll back the entire batch; consider setting atomic to false if partial success is acceptable.
- Gas limit should be set appropriately; if too low, the batch execution may fail due to out-of-gas errors.