Downgrade unknown transaction log message

[dimriou]

Many chains are expected to have more than 3 types of transactions so we downgrade this log message to reduce noise.

[github-actions]

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[samsondav]

Can we get a prom metric on this so we can alert on it maybe?

[derek1287]

Adding some comments to this issue, as we've done a deep dive here in the past, while supporting our own Chainlink oracles at LinkWell Nodes:

---

As we all know, the default GasEstimator mode for Sepolia chains is "BlockHistory", which is essentially using the gas prices of recent blocks to determine what the gas price of any of our submitted DR txns should be.

There are several different "txn types" in ETH, which refers to the version of the ETH token standard that was used to submit the txn:
https://docs.infura.io/api/networks/ethereum/concepts/transaction-types

• 0x0 (0) is the legacy (original) txn format
• 0x1 (1) txns were introduced after EIP-2930
• 0x2 (2) txns were introduced after EIP-1559
• 0x3 (3) txns are now appearing on Sepolia networks

0x3 is apparently extremely new, and I see little to no discussion about it. So it could either be a malicious / spammy actor submitting unsupported txns on Sepolia networks, but more likely an EIP that I'm unaware of. There's some evidence here that 0x3 will be the standard for ETH staking withdrawals, so this may be the core devs testing out that new feature on testnet:
https://www.galaxy.com/insights/research/ethereum-all-core-developers-consensus-call-106/

Because it's rather new, when CL sees these 0x3 txns it complains, but appears to be simply ignoring them in its BlockHistory gas estimation calculations (deferring to the known 0x0, 0x1, and 0x2 txn types.

As you can see in the following CL node log snippet, gas price was successfully estimated as 2.88 gwei, despite 0x3 txns existing in these blocks:

{
   "level":"debug",
   "ts":"2024-02-28T05:04:01.531Z",
   "logger":"EVM.11155111.Txm.BlockHistoryEstimator",
   "caller":"gas/block_history_estimator.go:571",
   "msg":"Setting new default prices, GasPrice: 2.88 Gwei, TipCap: 1.76 Gwei",
   "version":"2.9.0@065ef85",
   "gasPriceWei":"2.875890299 gwei",
   "gasPriceGWei":"2.88",
   "maxGasPriceWei":"115792089237316195423570985008687907853269984665.640564039457584007913129639935 tether",
   "headNum":5378586,
   "blocks":[
      5378574,
      5378575,
      5378576,
      5378577,
      5378578,
      5378579,
      5378580,
      5378581,
      5378582,
      5378583,
      5378584,
      5378585
   ],
   "tipCapWei":"1.760224088 gwei",
   "tipCapGwei":"1.76"
}

[dimriou]

Adding some comments to this issue, as we've done a deep dive here in the past, while supporting our own Chainlink oracles at LinkWell Nodes:

As we all know, the default GasEstimator mode for Sepolia chains is "BlockHistory", which is essentially using the gas prices of recent blocks to determine what the gas price of any of our submitted DR txns should be.

There are several different "txn types" in ETH, which refers to the version of the ETH token standard that was used to submit the txn: docs.infura.io/api/networks/ethereum/concepts/transaction-types

• 0x0 (0) is the legacy (original) txn format
• 0x1 (1) txns were introduced after EIP-2930
• 0x2 (2) txns were introduced after EIP-1559
• 0x3 (3) txns are now appearing on Sepolia networks

0x3 is apparently extremely new, and I see little to no discussion about it. So it could either be a malicious / spammy actor submitting unsupported txns on Sepolia networks, but more likely an EIP that I'm unaware of. There's some evidence here that 0x3 will be the standard for ETH staking withdrawals, so this may be the core devs testing out that new feature on testnet: galaxy.com/insights/research/ethereum-all-core-developers-consensus-call-106

Because it's rather new, when CL sees these 0x3 txns it complains, but appears to be simply ignoring them in its BlockHistory gas estimation calculations (deferring to the known 0x0, 0x1, and 0x2 txn types.

As you can see in the following CL node log snippet, gas price was successfully estimated as 2.88 gwei, despite 0x3 txns existing in these blocks:

{
   "level":"debug",
   "ts":"2024-02-28T05:04:01.531Z",
   "logger":"EVM.11155111.Txm.BlockHistoryEstimator",
   "caller":"gas/block_history_estimator.go:571",
   "msg":"Setting new default prices, GasPrice: 2.88 Gwei, TipCap: 1.76 Gwei",
   "version":"2.9.0@065ef85",
   "gasPriceWei":"2.875890299 gwei",
   "gasPriceGWei":"2.88",
   "maxGasPriceWei":"115792089237316195423570985008687907853269984665.640564039457584007913129639935 tether",
   "headNum":5378586,
   "blocks":[
      5378574,
      5378575,
      5378576,
      5378577,
      5378578,
      5378579,
      5378580,
      5378581,
      5378582,
      5378583,
      5378584,
      5378585
   ],
   "tipCapWei":"1.760224088 gwei",
   "tipCapGwei":"1.76"
}

0x3 transactions are the new Blob transactions introduced in Cancun fork (EIP-4844) . We've already added a PR to support them here.