npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@zidendev/noir-ziden

v0.0.1

Published

This is the proof-of-concept project of the Privacy-Preserving W3C verifiable credentials protocol with circuits written in Noir

Downloads

1

Readme

Noir-Ziden

This is the proof-of-concept project of the Privacy-Preserving W3C verifiable credentials protocol with circuits written in Noir

In this first version contains completent Noir circuits, test scripts as well as the TS scripts that serve the protocol's logic as specified in the Protocol-specs

Components

1. Merkle Tree & Indexed Merkle Tree

They are core data structure of the protocol, enabling succinct membership and non-membership verification, currently supporting:

  • Membership check
  • Non-membership check
  • Single insertion

See circuit

Upcoming features:

  • Variable arity
  • Batch insertion

2. Digital Signature

Digital signatures are used in the protocol as a principal authorization mechanism, this version supports 2 algorithms:

  • EdDSA
  • ECDSA

3. Protocol circuits

Run our code

Prerequisite

Installation

  • Install dependencies:
npm i
  • Compile Noir circuits:
./compile.sh

Test

  • Test claim features
npm run test-claim
  • Test indexed merkle tree features
npm run test-indexed-merkle-tree
  • Test state features
npm run test-state
  • Test claim presentation process
npm run test-claim-query

Use this as a library

  • Install as an npm dependency:
npm i @zidendev/noir-ziden@latest

Indexed Merkle Tree

  • Construct a new Indexed Merkle Tree
import {
  CryptographyPrimitives,
  IndexedMerkleTree,
  bitUtils,
  generateProofAndVerify,
  CircuitName,
} from "@zidendev/noir-ziden";

const crypto = await CryptographyPrimitives.getInstance();
const poseidon = crypto.poseidon;

// tree with depth being 3 and use Poseidon as hasher
const tree = new IndexedMerkleTree(3, poseidon);
  • Test, generate and verify ZK proof
tree.insert(3n);
var inputs = bitUtils.object2Array(tree.insert(1n));

const witness = new Map<number, string>();

inputs.forEach((input, index) => {
  witness.set(index + 1, convertToHexAndPad(input));
});

const verified = await generateProofAndVerify(
  witness,
  CircuitName.INDEXED_MERKLE_TREE
);

assert(verified == true);

Claim

Technically, a claim is an array of 8 32-byte numbers called slots, which can be constructed customizably with the following information:

  • Schema hash
  • The sequel number (in case there are multiple claims included in a single schema)
  • The expired time
  • The claim subject
  • Credential data (can be stored from slot 2 to 7)

Example:

import { ClaimBuilder } from "@zidendev/noir-ziden";

const schemaHash = BigInt("43914"); // should be the hash of the schema document
const expirationTime = BigInt(Date.now() + 60 * 60 * 1000);
const sequel = BigInt(1);
const subject = BigInt("439798"); // should be the Id of its holder

const claim = new ClaimBuilder()
  .withSchemaHash(schemaHash)
  .withExpirationTime(expirationTime)
  .withSequel(sequel)
  .withSubject(subject)
  .withSlotValue(2, BigInt("1"))
  .withSlotValue(3, BigInt("2"))
  .withSlotValue(4, BigInt("3"))
  .withSlotValue(5, BigInt("4"))
  .withSlotValue(6, BigInt("5"))
  .withSlotValue(7, BigInt("6"))
  .build();

We also can read, set information and perform logics of a claim after it is generated through its below functions:

get schemaHash() {}

get sequel() {}

get expirationTime() {}

get subject() {}

get allSlots() {}

async claimHash() {}

async eddsaSign(privateKey: BigInt){}

async ecdsaSign(privateKey: BigInt){}

getSlotValue(index: number) {}

clone() {}

set schemaHash(schemaHash: BigInt) {}

set sequel(sequel: BigInt) {}

set expirationTime(expirationTime: BigInt) {}

set subject(subject: BigInt) {}

setSlotValue(index: number, value: BigInt) {}

Holder

To create a holder in the protocol, you only need a set of either EDDSA or ECDSA public keys.

A holder can perform 2 operations to change its state

  • Add a new key
  • Revoked an existing key
import {
  keyUtils,
  Holder,
  AddAuthOperation,
  StateTransitionByEDDSASignatureWitnessBuilder,
  generateProofAndVerify,
  CircuitName,
} from "@zidendev/noir-ziden";

const {
  getEDDSAPublicKeyFromPrivateKey,
  getECDSAPublicKeyFromPrivateKey,
  stateTransitionByEDDSASignature,
} = keyUtils;
var privateKey1 = BigInt("123");
var privateKey2 = BigInt("12");
var privateKey3 = BigInt("34");

// eddsa
var pubkey1 = await getEDDSAPublicKeyFromPrivateKey(privateKey1);
var pubkey2 = await getEDDSAPublicKeyFromPrivateKey(privateKey2);

// ecdsa
var pubkey3 = getECDSAPublicKeyFromPrivateKey(privateKey3);

const holder = new Holder(3, poseidon);

await holder.addAuth(pubkey1.X, pubkey1.Y, PublicKeyType.EDDSA);

// commit key insertion through the ZK proof
var operation1: AddAuthOperation = {
  type: "addAuth",
  publicKeyX: pubkey2.X,
  publicKeyY: pubkey2.Y,
  publicKeyType: PublicKeyType.EDDSA,
};
var operation2: AddAuthOperation = {
  type: "addAuth",
  publicKeyX: pubkey3.X,
  publicKeyY: pubkey2.Y,
  publicKeyType: PublicKeyType.ECDSA,
};

var inputs = await stateTransitionByEDDSASignature(privateKey1, issuer, [
  operation1,
  operation2,
]);

const witness = new StateTransitionByEDDSASignatureWitnessBuilder(3)
  .withStateTransitionByEDDSASignatureWitness(inputs)
  .build();

const verified = await generateProofAndVerify(witness, CircuitName.STATE);

assert(verified == true);

Issuer

Apart from key sets, an issuer also maintain a set of claims it has granted for holders and a set of revoked claims.

A issuer can perform 4 operations to change its state

  • Add a new key
  • Revoked an existing key
  • Issue a new claim
  • Revoke an existing claim
import {
  keyUtils,
  Issuer,
  AddAuthOperation,
  StateTransitionByEDDSASignatureWitnessBuilder,
  generateProofAndVerify,
  CircuitName,
  ClaimBuilder,
} from "@zidendev/noir-ziden";

const {
  getEDDSAPublicKeyFromPrivateKey,
  getECDSAPublicKeyFromPrivateKey,
  stateTransitionByEDDSASignature,
} = keyUtils;
var privateKey1 = BigInt("123");
var privateKey2 = BigInt("12");
var privateKey3 = BigInt("34");

// eddsa
var pubkey1 = await getEDDSAPublicKeyFromPrivateKey(privateKey1);
var pubkey2 = await getEDDSAPublicKeyFromPrivateKey(privateKey2);

// ecdsa
var pubkey3 = getECDSAPublicKeyFromPrivateKey(privateKey3);

var schemaHash = BigInt("93819749189437913473");
var expirationTime = BigInt(Date.now() + 60 * 60 * 1000);
var sequel = BigInt(1);
var subject = BigInt("439798");
var slotValues = [
  BigInt("43818579187414812304"),
  BigInt("43818579187414812305"),
  BigInt("43818579187414812306"),
  BigInt("43818579187414812307"),
  BigInt("43818579187414812308"),
  BigInt("43818579187414812309"),
];
var claim = new ClaimBuilder()
  .withSchemaHash(schemaHash)
  .withExpirationTime(expirationTime)
  .withSequel(sequel)
  .withSubject(subject)
  .withSlotValue(2, slotValues[0])
  .withSlotValue(3, slotValues[1])
  .withSlotValue(4, slotValues[2])
  .withSlotValue(5, slotValues[3])
  .withSlotValue(6, slotValues[4])
  .withSlotValue(7, slotValues[5])
  .build();

const issuer = new Issuer(3, poseidon);

await issuer.addAuth(pubkey1.X, pubkey1.Y, PublicKeyType.EDDSA);

// commit key insertion through the ZK proof
var operation1: AddAuthOperation = {
  type: "addAuth",
  publicKeyX: pubkey2.X,
  publicKeyY: pubkey2.Y,
  publicKeyType: PublicKeyType.EDDSA,
};
var operation2: AddAuthOperation = {
  type: "addAuth",
  publicKeyX: pubkey3.X,
  publicKeyY: pubkey3.Y,
  publicKeyType: PublicKeyType.ECDSA,
};
var operation3: RevokeAuthOperation = {
  type: "revokeAuth",
  publicKeyX: pubkey3.X,
};
var operation4: IssueClaimOperation = { type: "issueClaim", claim };
var operation5: RevokeClaimOperation = {
  type: "revokeClaim",
  claimHash: await claim.claimHash(),
};

var inputs = await stateTransitionByEDDSASignature(privateKey1, issuer, [
  operation1,
  operation2,
  operation3,
  operation4,
  operation5,
]);

const witness =
  new stateTransitionWitnessBuilder.StateTransitionByEDDSASignatureWitnessBuilder(
    3
  )
    .withStateTransitionByEDDSASignatureWitness(inputs)
    .build();

const verified = await generateProofAndVerify(witness, CircuitName.STATE);

assert(verified == true);

Claim presentation

import {
  Claim,
  ClaimBuilder,
  EDDSAPublicKey,
  ECDSAPublicKey,
  Issuer,
  Holder,
  ClaimExistenceProofWitness,
  ClaimNonRevocationProofWitness,
  ECDSAPublicKey,
  EDDSAPublicKey,
  IdOwnershipByECDSASignatureWitness,
  MembershipSetProofWitness,
  NonMembershipSetProofWitness,
  generateProofAndVerify,
  CircuitName,
  ECDSAClaimQueryWitnessBuilder,
} from "@zidendev/noir-ziden";

let claim: Claim;

let schemaHash: BigInt;
let expirationTime: BigInt;
let sequel: BigInt;
let slotValues: BigInt[];
let subject: BigInt;

let privateKey1: BigInt;
let privateKey2: BigInt;
let privateKey3: BigInt;
let pubkey1: EDDSAPublicKey;
let pubkey2: ECDSAPublicKey;
let pubkey3: ECDSAPublicKey;
let issuer: Issuer;
let holder: Holder;
let challenge: BigInt;

let iopWitness: IdOwnershipByECDSASignatureWitness;
let cepWitness: ClaimExistenceProofWitness;
let cnpWitness: ClaimNonRevocationProofWitness;
let mpWitness: MembershipSetProofWitness;
let nmpWitness: NonMembershipSetProofWitness;

privateKey1 = BigInt("123");
privateKey2 = BigInt("12");
privateKey3 = BigInt("12");

pubkey1 = await getEDDSAPublicKeyFromPrivateKey(privateKey1);
pubkey2 = getECDSAPublicKeyFromPrivateKey(privateKey2);
pubkey3 = getECDSAPublicKeyFromPrivateKey(privateKey3);

holder = new Holder(8, poseidon);
holder.addAuth(pubkey1.X, pubkey1.Y, PublicKeyType.EDDSA);
holder.addAuth(pubkey2.X, pubkey2.Y, PublicKeyType.ECDSA);

issuer = new Issuer(8, 10, poseidon);
issuer.addAuth(pubkey3.X as bigint, pubkey3.Y as bigint, PublicKeyType.ECDSA);

schemaHash = BigInt("93819749189437913473");
expirationTime = BigInt(Date.now() + 60 * 60 * 1000);
sequel = BigInt(1);
subject = BigInt("439798");
slotValues = [
  BigInt("43818579187414812304"),
  BigInt("43818579187414812305"),
  BigInt("43818579187414812306"),
  BigInt("43818579187414812307"),
  BigInt("43818579187414812308"),
  BigInt("43818579187414812309"),
];
claim = new ClaimBuilder()
  .withSchemaHash(schemaHash)
  .withExpirationTime(expirationTime)
  .withSequel(sequel)
  .withSubject(subject)
  .withSlotValue(2, slotValues[0])
  .withSlotValue(3, slotValues[1])
  .withSlotValue(4, slotValues[2])
  .withSlotValue(5, slotValues[3])
  .withSlotValue(6, slotValues[4])
  .withSlotValue(7, slotValues[5])
  .build();

issuer.addClaim(claim);
challenge = BigInt("123");

mpWitness = await MembershipSetProof(
  6,
  poseidon,
  [claim.getSlotValue(0).valueOf(), 12n],
  0
);
nmpWitness = await NonMembershipSetProof(
  6,
  poseidon,
  [1n, 123123123123123n],
  claim.getSlotValue(0).valueOf()
);

iopWitness = await idOwnershipByECDSASignature(privateKey2, holder, challenge);
cepWitness = await ClaimExistenceProof(issuer, 0);
cnpWitness = await ClaimNonRevocationProof(issuer, await claim.claimHash());

const validUntil = BigInt(Date.now() + 30 * 60 * 1000);

var witness = new ECDSAClaimQueryWitnessBuilder(8, 10, 6)
  .withClaimSlots(claim.allSlots)
  .withECDSAIopWitness(iopWitness)
  .withCepWitness(cepWitness)
  .withCnpWitness(cnpWitness)
  .withAttestingValue(claim.getSlotValue(0).valueOf() + BigInt(1))
  .withOperator(1)
  .withQueryType(0)
  .withSlotIndex0(0)
  .withSchemaHash(schemaHash)
  .withSequel(sequel)
  .withSubject(subject)
  .withValidUntil(validUntil)
  .build();

const verified = await generateProofAndVerify(
  witness,
  CircuitName.ECDSA_CLAIM_PRESENTATION
);

assert(verified == true);

Future work

  • Solidity smart contracts for proof verification and identity state management

  • User interface for holders

  • Server for issuers

  • Server and smart contracts for verfiers