# Verification key generation

The constraints and trade-offs discussed in the [noise insertion](/inferix-whitepaper/implementation/noise-insertion.md) and the [noise spreading](/inferix-whitepaper/implementation/adaptive-noise-spreading.md) are to ensure the *fidelity* of rendered results and the *robustness* of the verification, but they do not concern the security. Indeed, any attacker knowing the algorithm and parameters including trade-offs, can straightforwardly generate (without rendering the graphics scene) forged images with the same spectral characteristics, finally bypasses the verification. The security is supported using verification keys.

Each rendering task has a secret key, in current implementation, this key is also the task identification number $$J\_{\mathtt{id}}$$. When embedding the noise vector $$W$$ into the scene $$G$$, this number is used to compute distortion regions $$k\_i$$ for all $$1 \leq i \leq n$$, the vector $$\left(k\_i\right)\_{1 \leq i \leq n}$$ is called verification key. The computation is modeled as a function:

$$
K\_{\mathtt{verif}} \colon \left(S,W,J\_{\mathtt{id}}\right) \mapsto \left(k\_i\right)\_{1 \leq i \leq n}
$$

In the operation of the rendering network, the leak of used verification keys is unavoidable. For instance, a *worker* may register itself to become a *verifier* node; when got accepted, it will be assigned verification tasks containing verification keys, then will be able to collect used keys. Even worse, colluding *workers* may exchange collected keys so that each of them will possess a much larger collection [\[12\]](/inferix-whitepaper/references.md#12). Another possibility is the malicious *workers* may get verification keys from some compromised *verifiers*.

Hence $$K\_{\mathtt{verif}}$$ must be designed so that the knowledge about used keys does not leak any information about the next generated keys. The following proposition is necessary for the security of ANGV.

***Proposition 3.*** $$K\_{\mathtt{verif}}$$ is a cryptographic hash function.


---

# 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.inferix.io/inferix-whitepaper/implementation/verification-key-generation.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.