You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To learn about the Verity Verifier in detail, please refer to the [official documentation](https://docs.verity.usher.so/), specifically the [Verity Verifier](https://docs.verity.usher.so/build/verifier) section.
4
4
5
-
**The following is from the Docs as of *23rd of January 2025*.**
5
+
**The following is from the documentation as of *23 January 2025*.**
6
6
7
7
## Local Deployment
8
8
9
-
**Disclaimer:** Deployment of the canister (ic/managed/verifier) to the Mainnet is not advised. This is to ensure compliance with licensing agreements and to maintain security compatibility with the wider Verity Network. We recommend using our Managed Verifier and interfacing over XNET `async`call or wallet-to-IC update `direct`call for optimal security and performance.
9
+
**Disclaimer:** Deployment of the canister (`ic/managed/verifier`) to mainnet is not recommended. This is to ensure compliance with licence agreements and to maintain compatibility and security with the broader Verity Network. We recommend using our Managed *General Purpose MPC-TLS*Verifier and interfacing via an inter-canister `async`calls or a wallet‑to‑IC `direct`calls for optimal security and performance.
10
10
11
11
### Prerequisites
12
12
13
-
1.**Ensure Rust is configured for for`wasm32-wasip1` target.**
13
+
1.**Ensure Rust is configured for the`wasm32-wasip1` target.**
14
14
15
15
```bash
16
16
rustup target add wasm32-wasip1
17
17
```
18
18
19
-
2. Install `wasi2ic`
19
+
2. Install `wasi2ic`:
20
20
21
21
```bash
22
22
cargo install wasi2ic
23
23
```
24
24
25
-
3. Install `binaryen`
25
+
3. Install `binaryen`:
26
+
27
+
With Homebrew:
28
+
29
+
```bash
30
+
brew install binaryen
31
+
```
32
+
33
+
From the releases page:
26
34
1. Download [Binaryen](https://github.com/WebAssembly/binaryen/releases) from the releases page.
27
-
2. Extract the files - `tar -xzf binaryen-version.tar.gz`
28
-
3. Move to a directory - `sudo mv binaryen-version/bin/wasm-opt /usr/local/bin/`
29
-
4.`wasm-opt --version`
35
+
2. Extract the files: `tar -xzf binaryen-version.tar.gz`.
36
+
3. Move the binary to your PATH: `sudo mv binaryen-version/bin/wasm-opt /usr/local/bin/`.
37
+
4.Verify the installation: `wasm-opt --version`.
30
38
31
39
### Deployment
32
40
@@ -35,50 +43,51 @@ To deploy the canister locally, follow these steps:
35
43
1.`dfx start --clean`
36
44
2.`dfx deploy`
37
45
38
-
### Test
46
+
### Testing
39
47
40
48
1.`pnpm prep`
41
49
2.`pnpm test --run`
42
50
43
-
### Performance Benchmarks
51
+
### Performance benchmarks
44
52
45
53
We have benchmarked the following functions to provide insight into their performance:
46
54
47
-
#### verify_proof_async and verify_proof_async_batch
55
+
#### `verify_proof_async` and `verify_proof_async_batch`
48
56
49
-
-**Execution Time:** Constant time, regardless of input size(~2100ms).
50
-
-**DFX Cycle Cost:**Ranges between 550-720 per TLS data bytes/length.
57
+
-**Execution time:** Constant, regardless of input size (~2100 ms).
58
+
-**DFX cycle cost:**Approximately 550–720 cycles per byte of TLS data.
51
59
52
-
#### verify_proof_direct and verify_proof_direct_batch
60
+
#### `verify_proof_direct` and `verify_proof_direct_batch`
53
61
54
-
-**Execution Time:** Linear time, calculated as 3x the execution time of `verify_proof_async` plus Signing Time (L).
55
-
-**DFX Cycle Cost:**Almost the same as `verify_proof_async` and `verify_proof_async_batch`.
62
+
-**Execution time:** Linear; approximately 3× the execution time of `verify_proof_async` plus signing time (L).
63
+
-**DFX cycle cost:**Roughly the same as `verify_proof_async` and `verify_proof_async_batch`.
56
64
57
65
### Caveats
58
66
59
67
#### `clang` dependency
60
68
61
-
**On macOS:** If you are experiencing issues during `cargo build` where the `ring` library fails to compile, this is typically due to `clang` not being found.
69
+
**On macOS:** If you experience issues during `cargo build` where the `ring` library fails to compile, this is typically because `clang` is not found.
70
+
71
+
To resolve this:
62
72
63
-
To resolve this, you can install `clang` using Homebrew.
73
+
1. Install `clang` using Homebrew.
64
74
65
75
```bash
66
-
brew install clang llvm
76
+
brew install llvm
67
77
```
68
78
69
-
Alternatively, you can set the following environment variables:
The `etherum_pk` field in the `PublicKeyReply` struct is the Ethereum address derived from the Sec1 public key. This is done using the `get_address_from_public_key` function in the `ethereum` module.
87
+
The `etherum_pk` field in the `PublicKeyReply` struct is the Ethereum address derived from the SEC1 public key. This is obtained using the `get_address_from_public_key` function in the `ethereum` module.
0 commit comments