If you can work out what is being sent you can recraft it and send the raw data with a normal transaction, just steal the function sig and pad your values correctly. Example [raw transfer][1]: [![raw transfer][2]][2] In your case you can see they have exactInputSingle(), so you can guess that and other similar Uniswap functions are also in the multicalls, search signatures in the [4byte directory][3] and break the calls down: [![searching function sig][4]][4] You could also write your own abi for that function or take from a contract with the same function and arguments. Look up sig/arguments on 4byte directory. Have done this with an unverified farming contract that was just passing pid, amount and address to withdraw. Something like: [![a minimal abi][5]][5] [1]: https://github.com/0xMaka/w3py/blob/main/raw_transfer.py [2]: https://i.sstatic.net/XpMqO.png [3]: https://www.4byte.directory/signatures/?bytes4_signature=0xbc651188 [4]: https://i.sstatic.net/9Bm0M.png [5]: https://i.sstatic.net/zjOH7.png