tx type issue.... gasPrice being present along with maxFeePerGas etc

[C0D3O]

I'm listening mem pool on zksync era but it's not important
here are some examples from the provider listener

type: 2,
gasLimit: 603996n,
gasPrice: 33750000n,
maxPriorityFeePerGas: 0n,
maxFeePerGas: 33750000n,

type: 0,
gasLimit: 978604n,
gasPrice: 25000000n,
maxPriorityFeePerGas: 25000000n,
maxFeePerGas: 25000000n,

type: 2,
nonce: 707,
gasLimit: 603996n,
gasPrice: 33750000n,
maxPriorityFeePerGas: 0n,
maxFeePerGas: 33750000n,

type: 113,
gasLimit: 1404347n,
gasPrice: 25000000n,
maxPriorityFeePerGas: 0n,
maxFeePerGas: 25000000n,

etc
and the question

why type 2 txs contains defined gasPrice and type 0 contains maxFeePerGas and maxPriorityblabla

if I try sending a tx with ethers it won't allow me to define gasPrice with maxFeePerGas, it will throw an error, but at the same time the provider show txs with all the keys defined ??????? How? Why?
Thank you

[ricmoo]

That is weird. Can you verify the RPC response from the provider includes those (you can use provider.on("debug", console.log) to check the responses).

My guess is they have modified their node to return everything, trying to be helpful, but in reality it just confuses things. Just a guess though.

But including those all cause compatibility issues, because they can’t all be used when sending a transaction.

[C0D3O]

so I could find only 1 tx in the logs where eip1559 are null.... ( the second to last screenshot )

[ricmoo]

Actually, I think I’m confused. What is the error you are getting? Or just that those values are populated in a transaction?

[C0D3O]

the problem is this, one of the problems
the full code

import { JsonRpcProvider, Wallet, WebSocketProvider } from 'ethers';

const listen = async (signer: Wallet) => {
	console.log('Listening...');
	provider.on('pending', async (tx) => {
		try {
			const txRes = await provider.getTransaction(tx);

			await signer.sendTransaction({
				...txRes,
				from: signer.address,
			});
			// ERROR eip-1559 transaction do not support gasPrice
		} catch (error: any) {
			console.log(error.message);
		}
	});
};

// const provider = new WebSocketProvider('wss://mainnet.era.zksync.io/ws');
const provider = new JsonRpcProvider('https://fabled-attentive-emerald.quiknode.pro/791f0420fd870047c869971fcbfc1463f60fb6ae/');
const signer = new Wallet('0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80', provider);

listen(signer);

the private key is from localhost whatever, so no worries:D

[C0D3O]

I just take a tx, and I cannot send it as it is... but somehow it appeared in the mempool...ehm...

[C0D3O]

@ricmoo could you comment on that? is this an ethers bug?

[C0D3O]

so I guess it's a bug and for now you need to manually remove values from the received tx params depending on the tx type..

I wanna make logic to replace tx if they are still not mined after the timeout is reached. I guess the tx.wait() method doesn't support it?