# Performance evaluation

To evaluate the implementation on BLS signature aggregation, we measured the running time of the deVirgo prover and recursive verifier using two AMD EPYC™ 7763 CPUs. The result is summarized as follows:

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*jR_E1FM5BuA2jFiy-uki1g.png" alt="" height="151" width="700"><figcaption></figcaption></figure>

We have deployed the Ethereum full-node proof system on zkBridge. zkBridge sets Ethereum as the sender chain, and other networks such as BNB Chain and Avalanche as the receiver chain. The result shows that zkBridge can generate the Ethereum full-node proofs and verify the block header on BNB Chain and other networks within 12 seconds including the delays of all the components.

We will continue optimizing the implementation. GPU acceleration is planned in the near future, which can lower the up-front cost for better decentralization. Nevertheless the current zkBridge proof system is efficient enough to catch up with the block time of Ethereum.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zkbridge.com/proving-ethereum-full-pos-consensus-in-zk/performance-evaluation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.