New answers tagged

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

Your network timeout is very long. delete that line. It will then give you an error telling you what to do next. Probably to do with lack of reply to your infura ping.


1

Both Rinkeby and Ropsten are public networks. But they are two different ethereum networks and have two seperate blockchains. By design, a blockchain Smart Contract cannot access any outside information other than what it receives by means of the signed payload which is the transaction that invoked this Smart Contract. The Smart Contract in a blockchain is ...


0

Let's say there are two contracts TRC20 which is a token and SaleOfGoods which has the salesOfGood function. The problem is in saleOfGoods function function saleOfGoods(string memory _nameOfgood, uint _amountOfgood) public { // .... trc20.approve(address(0xeBa84a3f7d8d70955bEFF633098D8d6A3a6c18e5), msg.sender, walletOfGoods[msg.sender][_nameOfgood]....


1

The gas required exceeds allowance (8000029) or always failing transaction error consists of two parts, either one of which may have taken place: The gas required for executing the transaction exceeds the gas-limit for the given block The transaction has reverted due to require(cond) with cond evaluating to false From my experience, this error is issued ...


0

At the moment Ropsten and Rinkeby use two different version of the ethereum protocol, for this reason the differences are normal. You may remember that on Ropsten it was tested the last fork various months ago (and they discovered the bug), while nobody did that on Rinkeby. As a matter of fact there are persisting differences.


Top 50 recent answers are included