New answers tagged gas-limit
0
I think you can find the answer in following link
It seems like they use a binary search to calculate estimated gas based on the opcodes.
1
Although I was unable to deploy/migrate via Truffle/Infura with plenty ETH, the contract was finally deployed/migrated via Remix/Metamask by setting GAS LIMIT=800000 and VALUE=0 at a non-peak time.
See https://etherscan.io/tx/0xde603058609d800d0ee2ccc5cf4cfa086a7161a25b9ce774cabae52a7514282c
0
The contract you are trying to deploy has a non-payable constructor and you are sending a 0.00000008 Ethers.
From the transaction trace
[1] 0 PUSH1 238732 3 1
[2] 2 PUSH1 238729 3 1
[3] 4 MSTORE 238726 12 1
[4] 5 CALLVALUE 238714 2 1
[5] 6 DUP1 238712 3 1
[6] 7 ISZERO 238709 3 ...
1
The problem is that Launchpad transfers ethers to Layerx using .transfer, so the receiver has 2300 gas stipend
payable(_stakeFeeAddress).transfer(stakeFeeAmount);
Since Layerx fallback modifies storage it requires more than the 2300 and it cause out of gas error making setupLiquidity revert
function() external payable {
ethToNextStake = ethToNextStake....
Top 50 recent answers are included
Related Tags
gas-limit × 289gas × 148
solidity × 55
gas-price × 48
gas-estimate × 40
out-of-gas × 36
go-ethereum × 33
transactions × 31
remix × 29
web3js × 22
private-blockchain × 20
contract-development × 17
contract-deployment × 17
truffle × 11
openethereum × 11
mining × 10
ropsten × 10
ganache × 10
blocks × 10
genesis × 10
contract-design × 9
ether × 8
metamask × 7
evm × 6
blockchain × 5