EVM Contract
The program is designed to interact with smart contracts in Ethereum networks and other EVM-compliant blockchains. Below is a description of all fields presented in the interface:
Basic settings
Name
An arbitrary name for identification in the interface.
Example: test
.
Module
Program module: EvmContract
.
Contract Address
Address of the smart contract in the Ethereum network or other EVM-compatible chain.
Format: 0x... (hexadecimal).
Example: 0xEC290740CB391970359A238DBD45e065c4F6D8c5
.
Wallet
The address of the user's wallet used to sign transactions.
Rpc
The RPC node to connect to the blockchain.
You can use more than one, then the transactions will be interleaved.
Use appropriate RPCs and wallets to work with ethereum-based networks
Transaction parameters
Value
The amount of native currency (e.g. ETH, APE) sent with the transaction.
Example: 0,000033
- value in number format with decimal separator.
Set the value value correctly. For example, if you have configured the mint function for 2 nft, remember to increase the value
Function Signature (optional)
Example: mint(uint32,bytes32[])
Function signature, not to be confused with function selector
Function Parameters (optional)
Parameters passed to the contract function call. Filled in according to the function signature. Each argument is separated by a ;
Example: 1;[]
Values for data types are filled in as follows:
intX: integer
Example: -1
intX[]: array of intX
Example: [-1, -2, -3]
uintX: positive integer
Example: 1
uintX[]: array of uintX
Example: [1, 2, 3]
address: hex address
Example: 0x0
(0x000..00) or 0x02fBc2Dd28288c16889Ec321dda3a74177a027ED
address[]: array of addresses
Example: [0x02fBc2Dd28288c16889Ec321dda3a74177a027ED, 0x02fBc2Dd28288c16889Ec321dda3a74177a027ED
]
bytes: hex string Example: 0x
bytes[]: array of bytes
Example: [0x, 0x]
bytes32: bytes of length 32
Example: 0x0000000000000000000000000000000000000000
bytes32[]: array of bytes32
Example: [0x0000000000000000000000000000000000000000]
bool: boolean value
Example: true
or false
Hexdata (optional)
Serialized transaction data in hexadecimal format. Includes function selector and parameters.
Example:
0x107af24b000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000
Specify either function signature and function parameters or hexdata
Gas
Ethereum gas and fees overview
Make sure that the wallet has a sufficient balance to pay for gas.
You can specify higher values for gas, unused money will be refunded. However, you must have these funds in your wallet.
Gas Limit
Gas Priority (a.k.a. priority fee)
Gas Fee Cap (a.k.a. max fee)
Timer (optional)
Time to start sending requests.
Tx Count (optional)
How many transactions to send, no limit by default.
Delay (optional)
Time between sending transactions.
Examples
Contract from LaunchMyNFT. Since Gas Fee Cap is set to 400,000
gwei. This means we should have at least 0.0004 + 0.000165
eth on the wallet. The formula is gasLimit*gasFeeCap
.
Since not all of the gas was used, the funds were refunded.
Last updated