ethers.js send tx's slower than Metamask. Why???

[misiek-eth]

Hello!
I've written simple send Tx's script and have problem with sending speed. When I execute this script it takes about 20-30s (sometimes even 1-2min) while my Tx appears in Mempool (checking by Mempool Explorer).
Also tried with web3.js and have the same problem.
If I use Metamask, Tx appears immediately (in about 1s)
I have no idea why???

I'll be grateful for any help :)

That's my code:

const url = 'https://spring-polished-frost.quiknode.pro/[MY_API_KEY]/';
let provider = new ethers.providers.JsonRpcProvider(url);
let privateKey = "[MY_PRIVATE_KEY]";
let wallet = new ethers.Wallet(privateKey, provider);
console.log("Address: " + wallet.address);

const tx = {
    from: wallet.address,
    to: "[MY_OTHER_WALLET]",
    value: ethers.utils.parseEther("0.001"),
    gasLimit: 25000,
    maxFeePerGas: 30000000000,
    maxPriorityFeePerGas: 1000000000,
}

wallet.sendTransaction(tx).then((txObj) => {
    console.log('txHash', txObj.hash)
})```

[ricmoo]

Can you include two example transactions on Etherscan? One from MetaMask and one from ethers? My guess would be the base and priority fee you are using, but I need examples to further investigate.

[misiek-eth]

Hi ricmoo!

Thank you for answering :)
It's not a matter of gas fees and confirmation time of Tx, I think.
I'm running Mempool Explorer and filter my account. So, I see that moment, when Tx appears in mempool as "Pending".
If I run script - it takes about 20s
If I simply click "send" on Metmask - it takes about 1s

I can record movie, if it's necessary.

What do you think?

[ricmoo]

I mean, I have zero data to dig into and am unfamiliar with those tools. A movie won’t really help, since it’s not that I don’t believe you, I just don’t have anything to work from. :)

Ethers doesn’t do anything special, it instantly send when you call sendTransaction. So it must be the node you are talking to.

Have you tried using the default provider instead of your custom rpc? Maybe it isn’t broadcasting promptly or hasn’t got an awesome set of peers. You can try the InfuraProvider, which is identical to what MetaMask uses.

[misiek-eth]

Yes, I understood that is a very strange problem... (I've checked infura RPC already and have the same issue)

Could you tell me, if my code is ok or is possible to speed-up?

[ricmoo]

The code looks fine, except for the hard-coding of the fee data. I would recommend (in general) leaving the maxFeePerGas and maxPriorityFeePerGas out, as ethers will automatically populate that with the current best recommended values, which accounts for uncle risk and MEV-incentives.

But if you are sure it isn't a fee issue, nothing else looks out of the ordinary.

[misiek-eth]

Thanks! Fees are constant only for testing purpose ;)

Is possible to sign Tx locally and then send? (maybe it's problem with signing not sending)

[ricmoo]

You can use wallet.signTransaction, in which case you need to provide all the needed properties (such as nonce, maxFeePerGas, etc). You can use wallet.populateTransaction to fill in anything needed you don't provide.

There can't really be any problem with signing and not sending. There is no delay. Here is the code that signs and sends the transaction used by Wallet.

Hard-coding fee data can absolutely cause delays though. When you send with MetaMask, are you hard-coding the same values? I recommend comparing your fast MetaMask transaction and the slow ethers transaction fees on Etherscan. Keep in mind fee data is fluid and changes every 15 seconds, so what was fast one moment can change for the next.

[misiek-eth]

Thanks! Yes, in Metamask I'm putting the same values and use the same RPC.
It's not a problem of confirming Txs - confirmation time is dependent of gas, of course.
My issue is that Tx send from Metamask is appearing as "pending" immediately, but send from script after 20-30 sec
Maybe I have problem with OS or JS configuration?

[misiek-eth]

There was a problem with broadcasting. I've set up private RPC on Infura and working fine - sending Tx's in about 300-400ms :)
Thank you for your help and patience ricmoo!!!