@selfxyz/contracts v0.0.8

Self Contracts

Overview

This is the implementation of contracts for verification and management of identities in Self.

⚠️Cautions⚠️

When you do the upgrade, be careful with this storage patterns

• You can not change the order in which the contract state variables are declared, nor their type.

Pls see this page for more details: https://docs.openzeppelin.com/upgrades-plugins/writing-upgradeable#modifying-your-contracts

Integration Guide

In the npm package, you'll find the following directory structure:

.
├── abstract
│   └── SelfVerificationRoot.sol # Base impl in self verification
├── constants
│   ├── AttestationId.sol # A unique identifier assigned to the identity documents
│   └── CircuitConstants.sol # Indices for public signals in our circuits
├── interfaces
│   ├── IDscCircuitVerifier.sol
│   ├── IIdentityRegistryV1.sol
│   ├── IIdentityVerificationHubV1.sol
│   ├── IPassportAirdropRoot.sol
│   ├── IRegisterCircuitVerifier.sol 
│   ├── ISelfVerificationRoot.sol
│   └── IVcAndDiscloseCircuitVerifier.sol
└── libraries
    ├── CircuitAttributeHandler.sol # Library to extract each attribute from public signals
    └── Formatter.sol # Utility functions to manage public signals to meaningful format

If you want to integrate SelfVerificationRoot.sol into your contract, you should also import these files.

import {SelfVerificationRoot} from "@selfxyz/contracts/contracts/abstract/SelfVerificationRoot.sol";

import {IVcAndDiscloseCircuitVerifier} from "@selfxyz/contracts/contracts/interfaces/IVcAndDiscloseCircuitVerifier.sol";

import {IIdentityVerificationHubV1} from "@selfxyz/contracts/contracts/interfaces/IIdentityVerificationHubV1.sol";

import {CircuitConstants} from "@selfxyz/contracts/contracts/constants/CircuitConstants.sol";

And override verifySelfProof function and write your own logic. You can take a look at these examples.

• Airdrop
• HappyBirthday

In the verifySelfProof function, you should add these validations

• Mandatory
  • scope validation
  • attestation id validation
• Optional
  • nullifier validation
  • user id validation
  • age verification with olderThan
  • forbidden countries validation
  • ofac validation

Also, if you want to play with some attributes in the passport, you should import these libraries.

import {CircuitAttributeHandler} from "@selfxyz/contracts/contracts/libraries/CircuitAttributeHandler.sol";
import {Formatter} from "@selfxyz/contracts/contracts/libraries/Formatter.sol";

CircuitAttributeHandler is the library to extract readable attributes in the passport from public signals. The formatter is responsible for converting other data included in the public signals. Use it when you want to validate information related to birthdays or the time when the proof was generated.

As an example, please refer to the following contract.

• HappyBirthday
• getReadableRevealedData function in the hub contract

Building Contracts

1. Install dependencies:

yarn install

2. Compile the contracts:

yarn run compile

Deployments

1. Deploy verifiers

yarn run deploy:allverifiers:celo

2. Deploy registry proxy and impl

yarn run deploy:registry:celo

3. Deploy hub proxy and impl

yarn run deploy:hub:celo

4. Update csca, ofac and hub address in registry

yarn run update:cscaroot:celo
yarn run update:ofacroot:celo
yarn run update:hub:celo

Testing

When you compile the circuits, make sure you set the build flag to true for these circuits:

• register_sha256_sha256_sha256_rsa_65537_4096
• dsc_sha256_rsa_65537_4096
• vc_and_disclose Go to ../circuits/scripts/build/ and change false to true for these circuits. Then you can run the following command to see the coverage.

cd ../circuits
yarn run build-all
cd ../contracts
yarn run test:coverage:local

Deployed Contract Addresses