Closed praetoriansentry closed 2 weeks ago
From @cffls , this might be an issue with the pool manager rather than cdk-erigon. Leaving this open for now.
Labelling for Polygon given the comment above until we can confirm. Helps with organising tasks at Gateway side.
Update: Fix for pool manager to support type 2 transactions available to test now @praetoriansentry
Verified type2 tx works with zkevm-pool-manager:v0.1.2
cast send --private-key "0x12d7de8621a77640c9241b2595ba78ce443d05e94090365ab3bb5e19df82c625" --value 5ether 0x5f5dB0D4D58310F53713eF4Df80ba6717868A9f8 --gas-limit 50000 --rpc-url $ETH_RPC_URL
blockHash 0xef2ad356780df87daf0943fd398c52e7b22e63a2728ba6a23b7368268b0411c0
blockNumber 30
contractAddress
cumulativeGasUsed 21000
effectiveGasPrice 920822199
from 0xE34aaF64b29273B7D567FCFc40544c014EEe9970
gasUsed 21000
logs []
logsBloom 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
root
status 1 (success)
transactionHash 0x66ea2e9a1bfe0153582f22b65eb6e908ef5f43c9e8dfb6514daef39327ba4c74
transactionIndex 0
type 2
blobGasPrice
blobGasUsed
authorizationList
to 0x5f5dB0D4D58310F53713eF4Df80ba6717868A9f8
I'm guessing since you have a receipt that cdk-erigon was also happy with the TX 🤞 ?
Yes, it is included in block 30:
cast block 30 --rpc-url $(kurtosis port print cdk cdk-erigon-rpc-001 rpc)
baseFeePerGas 24466815
difficulty 0
extraData 0x
gasLimit 30000000
gasUsed 21000
hash 0xef2ad356780df87daf0943fd398c52e7b22e63a2728ba6a23b7368268b0411c0
logsBloom 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
miner 0x5b06837A43bdC3dD9F114558DAf4B26ed49842Ed
mixHash 0x0000000000000000000000000000000000000000000000000000000000000000
nonce 0x0000000000000000
number 30
parentHash 0xaca344f9f0945ec598cc6b3a3e46bbb6253155c532ccf295a055daa32bac1650
parentBeaconRoot
transactionsRoot 0xeec406694ff8875f473c1639bc42f549b3ba859255a6b30ecfe45d51a071f0b3
receiptsRoot 0xf78dfb743fbd92ade140711c8bbc542b5e307f0ab7984eff35d751969fe57efa
sha3Uncles 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347
size 673
stateRoot 0x377b561b9ab785b0a8677501ff59333340db8e7d8e92d3fedf1fbf06a5656754
timestamp 1731009313 (Thu, 7 Nov 2024 19:55:13 +0000)
withdrawalsRoot 0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421
totalDifficulty 0
blobGasUsed 0
excessBlobGas 0
requestsHash
transactions: [
0x66ea2e9a1bfe0153582f22b65eb6e908ef5f43c9e8dfb6514daef39327ba4c74
]
Confirmed fixed here as well
I'm running a test network like this:
I was expecting that I would be able to send normal transactions now, but that doesn't seem to work. This works fine:
This returns an error:
server returned an error response: error code -32000: RPC error response: error getting from address