New answers tagged

0

This is an old question but since no answer: the last number of the derivation path is to be changed to generate a new address: 0 is the first address, that you get with path m/44'/60'/0'/0/0, then use m/44'/60'/0'/0/1, then m/44'/60'/0'/0/2 ...


0

Logs are included in the transaction receipt. Unless you use some wrapper around the contract to get the logs they will be encoded. Then you will have to use something like web3.api.abi.decodeLog.


0

Error: "Transaction ran out of gas. Please provide more gas: This happens when you want to execute a transaction that requires X amount of gas for successful execution but you send gas less than X. Solution: On Ganache: the default gasLimit is 6721975 you can pass that value as the gasLimit for the execution of your transaction. On other networks say ...


0

JSONRPC doesn't require gasLimit or gasPrice by default. But if these fields are not set correctly, transaction underpriced error is occured. Because default gasPrice and gasLimit is too low. In my case, I encoded params twice. The signed result was valid JSONRPC format, but there's no field about gasLimit or gasPrice. Check your signed result using ethereum-...


0

You should probably ask yourself how else would the transaction revert without being executed. It doesn't change any of the state variables which the contract function is designated to. But it is still executed to the point where the require statement is rejected, and a REVERT opcode along with the error-message is sent from the node back to your ...


0

Other nodes simply don't care about the bad block and continue with some other block. The bad miner has two options: either continue mining on top of the bad block or try to mine a valid block. If he continues on top of the bad block no other node still won't accept any of those blocks as even if subsequent blocks are valid they are based on an invalid block ...


2

After reviewing how ethereumjs-block:Block.genTxTrie() does it, I managed to figure it out: const trie = new Trie() await Promise.all(transactionsRaw.map((t, i) => new Promise(resolve => { trie.put( rlp.encode(i), new Transaction(t).serialize(), resolve ) }) )) or const trie = new Trie() const put = util.promisify(trie....


0

Of course you can sign a transaction with any private key that you want. But when you finally execute it, the gas required for this transaction (as well as the amount of ether that you have set in the value field) will be taken from the account corresponding with that key. And if you just choose a random key, then this account will have 0 Ether with a ...


0

This code does sign the transaction, but how do I verify that the transaction has been correctly signed? How is it possible to verify that the signature is correct? web3 has an estimateGas method you can use to estimate the gas required for the transaction and If signature is incorrect, that means the transaction is going to fail then it will simply ...


1

Please check this tool. You need to make your javascript browser compatible to use require() features.


Top 50 recent answers are included