MinimalForwarder forward request to a payable function from another contract

Support Contracts
1

Hello everyone,

I am working with the MinimalForwarder and everything was looking fine... until I tried to call a payable function from another contract.
Indeed I have a contract that has a sendWithFee method which role is to split the amount of BNB ( or Ether or whatever native token of an EVM blockchain) he received and send it to transfer it to different addresses.
The thing is it looks like the forwarder contract is not even reaching the contract.
Example:

And what it should do: (called without the relayer)

It has an internal tx sending BNB to the Null address.

Do you know why ? We agree that the minimal forwarder can forward request to payable functions right ?

Thanks

Edit: It has been flagged and hidden by the community, I don't know why

2

Yes, this should work.

I can't tell what went wrong here.

Can you verify the MinimalForwarder on bscscan?

3

See this contract on testnet 0x4270f22E0A7D5d2Ce64afb1d393fF214c6c8432f, the code is verified
I can't post a link apparently...

4

And I saw this

5

What function is the transaction supposed to be calling?

It doesn't seem to be sendWithFee.

6

It is supposed to be sendWithFee actually

7

Here is the inner transaction

const sendWithFee = contract.methods.sendWithFee(
      toAddress,
      holderAddress,
      holderFee,
      companyFee,
    )

    const tx = {
      from: fromAccount.address,
      to: this.apiConfigService.bscConfig.transferBnbWithFeeSc,
      value: amountBNB,
      gas: await this.bscService.estimateGas(sendWithFee, {
        from: fromAccount.address,
        value: amountBNB,
      }),
      data: sendWithFee.encodeABI(),
    }
8

I retried to do the tx, here is the result

9

The signature is not valid.

It isn't sending any BNB and it isn't the null address, it's a call to 0x00...01, the ECRECOVER precompile.

You can see a trace for the latest transaction you shared on Tenderly where it is clear that it's throwing an error during signature validation.

10

Indeed, I didn't know about tenderly, I'll add the tool to my toolbox !
Indeed signature problem... that is weird, I'll check that.
The thing is it works for all my other methods except this one...

11

I just tried to do the same but setting the value to 0
Here is what I get

A working tx

12

I retried with BNB

From what we see, there is no error but still no BNB is sent
But from this forum, apparently we can't send BNB or ether via a relayer

13

Oh, right. That seems obvious now. There is nowhere the ETH or BNB would be taken from... The relayer isn't going to contribute their own coins, and the signer doesn't have a way to pay those back.

In theory a Forwarder contract could add this feature though.