eth_call not working when sender is set to contract address

[kylesmartin]

I am having issues running eth_call when from is set to a contract address, e.g.

const providerURL = "<https://moonriver.public.blastapi.io";>

const provider = new ethers.JsonRpcProvider(providerURL, {
    chainId: 1285,
    name: 'moonriver'
});

const result = await provider.call({
    to: "0x22977D497Bc83591aA7FafD5152586fa91e2E30D",
    from: "<CONTRACT_ADDRESS (e.g. a multisig wallet)>",
    data: "0x6057361d0000000000000000000000000000000000000000000000000000000000000005",
})

where 0x22977D497Bc83591aA7FafD5152586fa91e2E30D is a simple storage contract and data calls store with a value of 5.

The code above results in the following error.

info: {
    error: {
        code: -32603,
        message: 'execution fatal: Module(ModuleError { index: 51, error: [10, 0, 0, 0], message: None })'
    },
    payload: { method: 'eth_call', params: [Array], id: 2, jsonrpc: '2.0' }
}

[crystalin]

@tgmichel I believe this is a known issue, possibly already solved ?

[tgmichel]

Yes it is already fixed and it will be included in the next RT upgrade.

Fix check of EIP-3607 transaction for internal calls

[kylesmartin]

Cool, I'll close the issue then. Thank you!

[atillabirer]

Yes it is already fixed and it will be included in the next RT upgrade.

Fix check of EIP-3607 transaction for internal calls

when will this materialize? We're having issues using moonbeam safe multisig.