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
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...
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.