Quote from: DuskNetwork on July 03, 2019, 08:38:06 AM

Quote from: Rigorous on July 02, 2019, 06:41:41 PM

I tested the Dusk extension on a decade old PC and one from last year. On both PCs the extension consumes a non-negligible amount of CPU, about 8-12%. I have not measured the energy consumption yet.

However, I can already tell the most recent PC outpaces the old one in terms of Dusk accumulation. At this stage CPU performance seems to be a bottleneck for ZK proof verification.

I thought generating ZK proofs was a magnitude more CPU intensive than verifying them. What then explains the effect of CPU usage on verifier performance?

The browser nodes are helping the network with verification of various zero-knowledge proofs in order to lighten the CPU load of the full nodes. The aim is to expand these browser nodes into full fledge block generators (which will participate to the consensus and get the rewards when they produce an accepted block) or verifiers (who can verify a zero-knowledge computation on behalf of the network).

I meant if it takes 1 minute to generate a proof and less than 1 second to verify it depending on the node's CPU, how is it possible to receive a new proof so quickly? Currently they come every 4 seconds, but yesterday it seemed like the bottleneck was the node's CPU, not the proofbox.