wip

Author: Mr-Leshiy

docs/src/architecture/08_concepts/catalyst_voting/v2.md

@@ -24,7 +24,28 @@ This document describes a Catalyst V2 vote transaction structure.
 It is a Catalyst v2 voting transaction
 defined on top the ["Generalized Vote Transaction"](./gen_vote_tx.md#specification) structure.
 
-Following that spec need to define a format of `choice`, `proof` and `prop_id`.
+Following that spec need to define a `choice`, `proof` and `prop-id`.
+
+Also needed to define an `event` field,
+so for both public and private transaction it must be the following:
+
+```CDDL
+event = {
+    "brand_id": UUID,
+    "campaign_id": UUID,
+    "election_id": UUID,
+    "category_id": UUID,
+}
+```
+
+  * `brand_id` - a unique identifier which represents a "brand" who is running the voting,
+    e.g. Catalyst, Midnight.
+  * `campaign_id` - a unique identifier which defines a "campaign" of voting,
+    e.g. "treasury campaign".
+  * `election_id` - a unique identifier which defines an election,
+    e.g. "Catalyst Fund 1", "Catalyst Fund 2".
+  * `category_id` - a unique identifier which defines a voting category as a collection of proposals,
+    e.g. "Development & Infrastructure", "Products & Integrations".
 
 ### Public vote
 
@@ -36,6 +57,11 @@ Following that spec need to define a format of `choice`, `proof` and `prop_id`.
     ```
 <!-- markdownlint-enable max-one-sentence-per-line code-block-style -->
 
+
+```CDDL
+vote-type = #6.37(h'8DE5586CE9984B9587427BE3C8592803') ; 8de5586c-e998-4b95-8742-7be3c8592803
+```
+
 ### Private vote
 
 <!-- markdownlint-disable max-one-sentence-per-line code-block-style -->
@@ -46,17 +72,20 @@ Following that spec need to define a format of `choice`, `proof` and `prop_id`.
     ```
 <!-- markdownlint-enable max-one-sentence-per-line code-block-style -->
 
-#### Vote generation
+```CDDL
+vote-type = #6.37(h'E78EE18DF38044C1A85280AA6ECB07FE') ; e78ee18d-f380-44c1-a852-80aa6ecb07fe
+```
+
+#### Vote and Proof generation
 
-To generate a cryptographically secured `private_choice` and `zk_proof` parts you can follow this [spec](./crypto.md#vote).
+To generate a cryptographically secured `choice-data` and `zk_proof` parts you can follow this [spec](./crypto.md#vote).
 Important to note,
 that as part of [*initial setup*](./crypto.md#initial-setup) of the voting procedure,
 the following properties are used:
 
-1. Each proposal,
-   defined by the `vote_plan_id` and `proposal_index`, defines a number of possible options.
+1. Each proposal, defined by the `proposal` field, defines a number of possible options.
 2. [ristretto255] as a backend cryptographic group.
-3. A commitment key $ck$ defined as a [BLAKE2b-512] hash of the `vote_plan_id` bytes.
+3. A commitment key $ck$ defined as a [BLAKE2b-512] hash of the `proposal` bytes.
 
 ## Rationale