Using the Delegated Prover
To reduce proof time computation time
Last updated
Was this helpful?
To reduce proof time computation time
Last updated
Was this helpful?
Each transaction to the privacy pool must be proven. The process is a heavy-computation process performed by the transaction sender. The library supports three proving modes:
Local
- The most secure case where no sensitive data sent to the 3rd parties. The hard computation is performed during the transaction proving on the user's device. This can take a long time with low performance devices. Moreover the proving parameters must be downloaded before transaction creation (~70 Mb).
Delegated
- An external proving machine is used (aka Delegated Prover). In this case the unencrypted transaction is sent to the delegated prover to perform hard computations outside of the user's device. Using a properly configured heavy-duty dedicated server can significantly decrease proving time. The client shouldn't download proving parameters.
A transaction will be rejected if the external prover is unavailable when theDelegated
proving mode selected.
DelegatedWithFallback
- Combines the Delegated and Local modes (external prover is used as the primary one).
The following command sets the specified prover mode. The proving mode is set for the current pool only. If you switch to a new pool the previously selected mode on the new pool will be used (if it wasn't set yet - the mode from the old pool will selected).
mode
: proving mode (a member of enum)
No return value but you must wait until the switch is completed before the next library interaction.
The following routine gets the current prover mode:
enum member.