Support issue for matic/maticmum

[OsmanYagc]

Hi @ricmoo,

I am trying to deploy a smart contract. My RPC provider is Alchemy and I am working on Polygon and Mumbai. You have said that you have fixed the problem on "Support for matic #1546". However when I try to deploy a contract on mumbai or polygon, it gives "getDefaultProvider does not support matic/maticmum" error .

After that, I tried to change the variable I am passing to getDefaultProvider function. Initially it was;

getDefaultProvider(matic, ..);

, and I have made it;

getDefaultProvider( {
name: 'matic',
chainId: 137,
_defaultProvider: (providers) => new providers.JsonRpcProvider('alchemy-rpc-url')
},
....,
);

Then it worked and deployed the contract. However, now, when I try to call a function on my smart contract like setBaseTokenUri, MintTo, or any functionality I added to my smart contract, it gives "transaction underpriced" error and cancel the operation.

When I tried the same contract and functions on rinkeby, everything works perfectly fine.

I do not understand why it is giving "getDefaultProvider" error when "matic" is sent as a paramater to getDefaultProvider and the "transaction underpriced" error after I changed the paramater "matic" passed to getDefaultProvider.

Appreciate your response,

Have a nice day!

**Note: I have used latest version 5.6.2 of ethers.js.

[zemse]

Hey @OsmanYagc, you can pass a maxPriorityFeePerGas

await contract.methodName(arg1, arg2, {
  maxPriorityFeePerGas: ethers.utils.parseUnits('50', 'gwei') // you can check on polygon scan what priority fee to use
})

You may also try the workarounds mentioned in #2828.

[OsmanYagc]

Thanks a lot @zemse, I will try them all

Have a nice day!