Polygon – Estimating Gas for Reverted Transactions Using 0x Protocol V4

0xpolygon

Whenever I try to estimateGas from a ERC1155Order I got a transaction revert, using Polygon Mumbai with Alchemy.

let sellOrder = new ERC1155Order({
    direction: TradeDirection.SellNFT,
    maker: alice.address,
    taker: bob.address,
    expiry: expirationTimeTS,
    nonce: 11,
    erc20Token: WETHAddress,
    erc20TokenAmount: 1, 
    fees: [],
    erc1155Token: ERC1155Address, 
    erc1155TokenId: "22897246053033895809978563905910150239444766161035846617439399460178038358017",
    erc1155TokenProperties: [],
    erc1155TokenAmount: 1,
    chainId: 80001,
});

const contractWrappers = new ContractWrappers(provider, {chainId: 80001});
let zeroEx = contractWrappers.exchangeProxy;
let txValidate = await zeroEx.getERC1155OrderHash(sellOrder).estimateGasAsync({ from: bob.address });

At alchemy I got this payload:

{
  "method": "eth_estimateGas",
  "params": [
    {
      "data": "0x1de3a7ac00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000329f61caefea1df01c60d7d0eafd9cdae91c853c00000000000000000000000004ebdfca9c91d299dcb312d23e58ac0cdeef418e000000000000000000000000000000000000000000000000000000006384e91000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009c3c9283d3e44854697cd22d3faa240cfb032889000000000000000000000000000000000000000000000000002386f26fc10000000000000000000000000000000000000000000000000000000000000000018000000000000000000000000088b48f654c30e99bc2e4a1559b4dcf1ad93fa656329f61caefea1df01c60d7d0eafd9cdae91c853c0000000000000e0000000001000000000000000000000000000000000000000000000000000000000000018000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000",
      "to": "0xdef1c0ded9bec7f1a1670819833240f027b25eff",
      "from": "0x04ebdfca9c91d299dcb312d23e58ac0cdeef418e"
    }
  ],
  "id": 42,
  "jsonrpc": "2.0"
}

And the response:

{
  "jsonrpc": "2.0",
  "id": 42,
  "error": {
    "code": 3,
    "message": "execution reverted",
    "data": "0x734e6e1c1de3a7ac00000000000000000000000000000000000000000000000000000000"
  }
}

Best Answer

The revert error you're receiving is a "NotImplementedError." I don't think ERC1155Orders has been or will ever be deployed to Polygon Mumbai. Ropsten is the preferred testnet for 0x contracts.

Related Solutions

Polygon – Transaction Reversed When FillOrder on 0x Protocol

Finally was ablt to execute fillOrder suscesfully. Actually initial code was almost correct wit few errors - token number should be in encodeERC721AssetData call and token amount (1) - is a value of makerAssetAmount field. And also increase value in the fillOrder call. Here is code sample: const erc721ProxyAddr = deployments[chainId].erc721Proxy; const erc20ProxyAddr = deployments[chainId].erc20Proxy;

    const exchangeAddr = deployments[chainId].exchange;
    const exchange = new web3Taker.eth.Contract(artifacts.Exchange.compilerOutput.abi, exchangeAddr);
    
    const polyNFTAddr = deployments[chainId].polyNFT;
    const polyNFTinstance = new web3Maker.eth.Contract(PolyNFT.abi, polyNFTAddr);       

    const polyTest20Addr = deployments[chainId].polyTest20;
    const polyTest20Instance = new web3Taker.eth.Contract(PolyTest20.abi, polyTest20Addr);

    const makerAssetData = OrderUtils.assetDataUtils.encodeERC721AssetData(polyNFTAddr, BigNumber(tokenId));
    const takerAssetData = OrderUtils.assetDataUtils.encodeERC20AssetData(polyTest20Addr);

    const order = {
        makerAddress: process.env.MAKER_ADDRESS,        // seller
        takerAddress: process.env.TAKER_ADDRESS,        // buyer
        senderAddress: NULL_ADDRESS,
        feeRecipientAddress: NULL_ADDRESS,
        makerAssetAmount: '1',                            // how many tokens to sell
        takerAssetAmount: '100000', //   amount,                       // price
        makerFee: '0',
        takerFee: '0',
        expirationTimeSeconds: '1938807983', // expiry,                                    
        salt: '125',                                      // random number
        makerAssetData: makerAssetData,
        takerAssetData: takerAssetData,       //  await devUtils.encodeERC20AssetData(erc20.address),
        makerFeeAssetData: NULL_BYTES,
        takerFeeAssetData: NULL_BYTES,
      
        chainId: chainId,
       exchangeAddress: exchangeAddr,
    };

   console.log(order);

   const sOrder = await OrderUtils.signatureUtils.ecSignOrderAsync(localKeyProviderMaker, order, process.env.MAKER_ADDRESS);

    let isValid = await exchange.methods.isValidOrderSignature(order, sOrder.signature).call();
    if (!isValid)
        return;

    let isApproved1 = await polyTest20Instance.methods.approve(erc20ProxyAddr, amount).send({from: takerAccount});
    if (!isApproved1) 
            return;
            
    let isApproved2 = await polyNFTinstance.methods.approve(erc721ProxyAddr, tokenId).send({from: makerAccount });
    if (!isApproved2)
          return;

    let res = await exchange.methods.fillOrder(order, amount, sOrder.signature)
                        .send({from: takerAccount, value: '3000000000000000', gas:18000000});

0x – Problem with 0x Protocol Goerli API

As of Jan 10, 2023, there is no token symbol support on Goerli, and limited token symbol support on Mainnet. The request works on Mainnet but fails on Goerli for this reason

For Goerli, you will need to use token addresses instead of token symbols. For example:

https://goerli.api.0x.org/swap/v1/quote?buyToken=0x07865c6e87b9f70255377e024ace6630c1eaa37f&sellToken=0xb4fbf271143f4fbf7b91a5ded31805e42b2208d6&sellAmount=100000000000000000

Related Topic