New answers tagged contract-invocation
0
This can also work:
> eth.getCode("CONTRACT ADDRESS")
"0x60806040526004361061..."
After getting the Byte code, remove the "0x" at the beginning and then use this Solidity decompiler, https://ethervm.io/decompile, to decompile the bytecode.
0
Usually smart contract's source code must be validated by Etherscan to let it understand all functions and read it correctly, but the source code for the contract you referred is not verified.
It is very likely that contract does not follow the standard for names and functions, so even if Etherscan can vaguely understand that it represents a ERC-721 token, ...
0
One transaction is always one call from an EOA (Externally Owned Account) to either another EOA (Ether transfer) or to one single smart contract.
So what you can do is create your own contract which does what you need. So your contract creates a reference to other contracts and calls them in specific order. Here are some references on how to do that: https://...
0
To batch different call in one transaction you will need to use smart contract.
For your smart contract, you have two possibilities.
On chain batch definition
Define the set of actions in your contract.
import "./Target1.sol";
import "./Target2.sol";
contract Test {
Target1 target1;
Target2 target2;
constructor(address ...
1
For anyone wondering the same thing, I ended up reading the yellow paper.
Turns out in p.35 they add G_{newaccount} to the gas cost, which is G_{newaccount}: Paid for a CALL or SELFDESTRUCT operation which creates an account (25000).
I couldn't find anywhere the definition of 'creating an account' which is odd (e.g. just tested: sending only an ERC-20 token ...
Top 50 recent answers are included
