Meta ID comes as a mobile app (or Dapp) and has access to a local private certificate generated for a citizen of Meta. This app can also share documents which are signed by an authority of Meta, which will is an incentive for nodes to pin (store locally) those distributed files (given their hardware requirements).

Those documents will be cached by the Dapp, but generally their copies are stored by the nodes. In addition Meta offers a key/value database, where Dapp can backup their settings and retrieve those as required.

Those assumptions allows us to conclude that Dapp comes with private document and database storage, which is automatically replicated and synced between various instances of Dapp.

One document is required for an app user to be considered a "citizen" of meta country. This document can be issued by a Validator. User will keep this document securely encrypted in their app. In addition to a scanned document, all document fields are stored in multiple records:

Such Meta ID is given to all citizens and Dapp can individually provide a proof that MetaID is associated with a valid ID backed by a validator. Whoever requests the proof cannot actually verify the real identity of AnonymousMetaID holder. They can be sure, however, that only one such code can be traced to a citizen at any given time.

MetaID is like social security number in U.S. or person's code. This code is not possible to change, so its use and exposure must be as minimal as possible. Each person must protect their MetaID.

For this reason, Anonimizers are created. Provided with MetaID to an Anonimizer, it will return the following:

The record can only be decrypted by owner of MetaID. Invoking this again with same MetaID will give the same response. Anonimizer also creates a private key but it's not exposed.

Anonimizer will keep private key secure until "valid_until" date and then it will expose "address=&gt;private_key" pairs.

Anonimizer will not expose associations between MetaID and addresses.

Voting citizen will first use anonimizer to acquire public key. They can then cast vote by encrypting it with this public key, attach their address and store it in Ballot Box. When vote is over, anonimizer will expose private keys, so votes can be decrypted and results can be counted.&nbsp;

Anonimizers also guarantee that a single MetaID owner can only acquire one address and therefore cannot cast multiple votes.

A voting system may partition voters by splitting them amongst multiple anonimizers. A poll will have a unique Poll ID as well as number of anonimizers in the pool.&nbsp;

For example, general election vote can be making use of 10 anonimizers - 1 of each is hosted by each candidate and other 5 held by other countries to guarantee fairness. The ID of a poll is "ABC123" so the following would be used to determine which anonimizer citizen can use:

Anonimizers will only accept citizens if their metaID fall into their allocated number.&nbsp; This takes care of the situation where same MetaID could acquire multiple "addresses" by using multiple anonimizers.

In order to interact between anonimizer and MetaID, the following loop happens:

dApp for ID will forward this information to a voting dApp including poll_id.

When time arrives, anonimizers will publish private keys, however they will share those keys only with people who run the vote including observers.

MB MetaID-Voting integration