Proof generation for EVM circuit fails with error: RootCircuit::new: Transcript(Other, "Identity point in preprocessed or proof is not yet supported")

[AronisAt79]

What command(s) is the bug in?

No response

Describe the bug

Proof request for block consisting of single l2 transaction
Proof request options:

('{"jsonrpc":"2.0", "method":"proof", '
'"params":[{"block":33,"circuit":"evm","aggregate":true,"mock":false,"mock_feedback":true,"rpc":"http://leader-testnet-geth:8545/", '
'"retry":false}], "id":33}')

Error:
RootCircuit::new: Transcript(Other, "Identity point in preprocessed or proof is not yet supported")

Circuit Commit: https://github.com/privacy-scaling-explorations/zkevm-circuits.git@branch=main
Chain Commit: eaab99aeb31b92ed8870548414c37148e18ac78d

Concrete steps to reproduce the bug

No response

[AronisAt79]

Full logs: https://zkevm-chain-testing.s3.eu-central-1.amazonaws.com/proveSingeCrossChainTx_evm_True_367-maronis.tar.gz

[ed255]

This error comes from the Root Circuit not supporting empty witness/fixed columns. Our halo2 fork always fills witness columns with blinding factors, so we rule out the possibility of having an empty witness column. This means we probably have a fixed column that is all 0s (which means that the column isn't used). Removing this column / assigning some values to it should solve this issue.

[ed255]

I have identified a fixed column which had no assignment when taking the EVM Circuit as a standalone circuit. I've fixed it here 54f2643

@AronisAt79 whenever you have some time, could you try running the real prover test with EVM Circuit + Root circuit on that commit?