Skip to content

Invalid params from contract deployment #1970

Answered by emclab
emclab asked this question in Q&A
Discussion options

You must be logged in to vote

Here is the Besu network log reporting the invalid params, unrecognized field "type". What is field "type" in tx submitted?

2021-08-30 04:50:46.788+08:00 | vert.x-eventloop-thread-0 | DEBUG | B3PropagatorExtractorMultipleHeaders | Invalid TraceId in B3 header: null'. Returning INVALID span context.
2021-08-30 04:50:46.790+08:00 | vert.x-worker-thread-1 | DEBUG | JsonRpcHttpService | JSON-RPC request -> eth_estimateGas
2021-08-30 04:50:46.790+08:00 | vert.x-worker-thread-1 | DEBUG | JsonRpcHttpService | Invalid Params
org.hyperledger.besu.ethereum.api.jsonrpc.internal.exception.InvalidJsonRpcParameters: Invalid json rpc parameter at index 0
	at org.hyperledger.besu.ethereum.api.jsonrpc.int…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@emclab
Comment options

Answer selected by zemse
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant