error when submitting 1559 transactions

[ligi]

unfortunately I cannot reopen: #25
also it is a bit different now - it is not the regexp as before anymore - we seem to be one step further now - but still cannot send 1559 transactions:

✓ ~ curl -X POST -H  "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0x02f86a0507849502f900849502f90582520894381e247bef0ebc21b6611786c665dd5514dcc31f8080c001a04c23103dda68fc3287b9972f0b105752e8c79e6f3135ba631db65102202a563fa07a3c44a30ac5aa24f5e259317bda094fb594d652c8808e72d7557f6457f9ed27"],"id":1}' https://in3-v2.slock.it/goerli/nd-1
{"jsonrpc":"2.0","id":1,"result":null,"error":{"code":-32602,"message":"Invalid params: Invalid bytes format. Expected a 0x-prefixed hex string with even length."},"stats":null,"in3":{"lastValidatorChange":0,"lastNodeList":5339558,"execTime":10,"rpcTime":9,"rpcCount":1,"currentBlock":5346459,"version":"2.1.0"}}

a bit weird though - it is 0x prefixed and has a even length

also sending it to a dappnode with no problem:

✓ ~ curl -X POST -H  "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0x02f86a0507849502f900849502f90582520894381e247bef0ebc21b6611786c665dd5514dcc31f8080c001a04c23103dda68fc3287b9972f0b105752e8c79e6f3135ba631db65102202a563fa07a3c44a30ac5aa24f5e259317bda094fb594d652c8808e72d7557f6457f9ed27"],"id":1}' http://goerli-geth.dappnode:8545
{"jsonrpc":"2.0","id":1,"result":"0x9b66419b1484b0045fe457adb63a377e09d7bb6a4ea57f93c9d8bf94f7dc4f29"}

[leonardotc]

Yeah. This one will require some debugging. As you said this seems to be stopping on the server but not quite at the validator on the verifier. We will check it out.

[ligi]

Thanks! Please keep me updated!

[leonardotc]

Hello again Ligi,

My bad, this was the last week before a new release (at this point internal only) so things have been chaotic for the whole in3 team. The error is caused by a side effect of (what looks like) a quick fix. A little before dispatching the request to the rpc endpoint, the server changes the payload which becomes invalid. Since that is there for years, I will have to do some investigation of what the thing is actually fixing (seems to be geth specific).

[ligi]

thanks for the info! Would be happy on any updates on this one.

[leonardotc]

Hello Ligi. Yeah, this will require further investigation (thats why its taking so long) but we will push a fix later today.

[leonardotc]

Btw Ligi, the fix was deployed on the last Friday. Please let me know if you find any more issues.