Arkworks EIP-4844 implementation

[belijzajac]

This is a hacky implementation for Arkworks because Arkworks doesn't support loading precomputed trusted setups other than generating them from a secret value.

As a result, EIP-4844 tests for this implementation have been disabled, and it's recommended to rely on benchmark results to gauge real Arkworks' performance relative to other ECC backend libraries that incorporate EIP-4844.

Refer to issue arkworks-rs/poly-commit#111 for more information.

[belijzajac]

Local benchmark results with the mainnet trusted setup¹ and the parallel feature:

benchmark	times slower than blst-from-scratch
blob_to_kzg_commitment	5.08x
compute_kzg_proof	1.98x
verify_kzg_proof	3.81x
compute_blob_kzg_proof	1.94x
verify_blob_kzg_proof	2.25x
verify_blob_kzg_proof_batch/1	2.34x
verify_blob_kzg_proof_batch/2	1.57x
verify_blob_kzg_proof_batch/4	1.30x
verify_blob_kzg_proof_batch/8	1.18x
verify_blob_kzg_proof_batch/16	1.12x
verify_blob_kzg_proof_batch/32	1.14x
verify_blob_kzg_proof_batch/64	1.13x

I think it's weird that blob_to_kzg_commitment is 5 times slower while all its work happens inside the g1_linear_combination function; and verify_kzg_proof just calls internal Arkworks function for proof verification.

Footnotes

1. Arkworks generates trusted setups dynamically containing either 4096 or 4 G1 points. ↩