Description

Overview

The observer is not a part of Mishti network. However, it is a component of the Clean Stack for programmable privacy, used for GDPR-compliant storage of encrypted user data with the DecryptBabyJubJub method for KYC.

The observer is a primary component in the Clean Hands stack with Zeronym. To interact with the observer, a user generates a ZKP they have passed sanctions checks, and this ZKP outputs the ciphertext of the user's personal identifiable information (PII) and the user's associated blockchain address. The Observer's role in this system is to verify ZKPs, issue attestations to users with valid ZKPs, and to store the public outputs of these ZKPs so that the ciphertext can be decrypted if Mishti network permits.

Endpoints

POST /observations

This endpoint does the following.

• Verify the Clean Hands ZKP. Uses this circuit to verify a proof which should have been generated using this package.

• Make sure the encryption key output by the circuit is Mishti Network’s public key.

• Make sure the issuer address output by the circuit is the configured clean hands issuer.

• Make sure the conditions contract signed by the user is on our whitelist.

• Verify the user’s signature of the conditions contract.

• Store the ZKP’s public values, user's address, user's signature, and signed access contract in the observations collection.

• Issue an attestation on Sign Protocol.

GET /observations?user_address=<address>

This endpoint queries the database for an observation for the provided user address and returns the result.

Schemas

pub struct ObservationSchema {
    /// Distinct from _id. This is a hash of the fields of the observation. Allows for 
    /// more efficient lookups to make sure we don't store the same observation twice.
    pub id: String,
    pub user_address: String,
    pub signature: String,
    pub access_contract: String,
    pub zkp_public_values: Vec<String>,
}