We have a smart contract which sends ETH to some address', but everytime we call that function, the function fails..


As you can see in the link we do however specify a much higher GAS limit that needed, but still it runs out of gas...

What is going wrong?

1 Answer 1


It seems to be a problem with one of the addresses you are forwarding ether.

If you look at the internal transactions you will see the following:

enter image description here

call_49 is failing due to "out of gas". If you inspect the target address, you will see it is a contract.

Inspecting the code the contract has, it has a fallback function that has the following code:

function() payable {
    if (!parentAddress.call.value(msg.value)(msg.data))
    // Fire off the deposited event if we can forward it  
    ForwarderDeposited(msg.sender, msg.value, msg.data);

This suggests the problem is that the contract is receiving ether and trying to send it back its parent address and this call is either throwing or actually running out of gas, making the whole transaction fail.

  • How can this be fixed? If inspect the parent address it got lots of ether etherscan.io/address/0x1522900b6dafac587d499a862861c0869be6e428. Is it needed that the original contract (the one of V. Rutten) sends value at it's invocation or does the forward owner needs to add money to it's forward contract? Dec 26, 2017 at 17:29
  • If the receiving account is throwing when trying to send ether to it, there's not much you can do. One way to fix it would be not to send ether to that one account. Dec 26, 2017 at 20:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.