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

zokrates-tools

v0.0.0

Published

ZoKrates convenience CL tools and scripts.

Downloads

89

Readme

ZoKrates dev tools

A command line toolkit for easier dev flow with ZoKrates, so you do not have to copy files, execute each command step by step, deploy the contract, and verify manually. It is a TS wrapper around a set of bash scripts which I wrote while playing around with ZoKrates. I like to automate stuff.

Since this is a first dirty version, bugs can be expected. Feel free to open issues or contribute.

Maintainers

Primary: Adam Nagy (@ngyam)

Quickstart

npm install -g zokrates-tools

! Make sure that a ZoKrates container is running, either named as zokrates or zokrates/zokrates. The scripts are looking for it, and automatically fetch the container ID.

Then just use the --help flag for further description of the commands.

zoktools --help
> zoktools <command>

Commands:
  zoktools compile <name> [options]         Compiles the .code file in the
                                            running ZoKrates container.
  zoktools copyfrom <name> [outputdir]      Retrieves the project folder & files
  [options]                                 from the running ZoKrates container.
  zoktools copyto <filepath> [options]      Copies a .code file into its created
                                            project folder in the running
                                            ZoKrates container.
  zoktools deploy <name> [dir] [options]    Deploys verifier from the local
                                            project folder. No truffle, just
                                            web3.
  zoktools easycopyproof <name> [dir]       Parses the proof in the local
  [options]                                 project folder so that it is easier
                                            to copy-paste manually.
  zoktools full <filepath> [outputdir]      Performs a full cycle: copy to
  [options]                                 container -> generate (compile,
                                            setup, witness, proof, verifier) ->
                                            copy from container.
  zoktools generate <name> [options]        Performs a full generation of a
                                            project inside the ZoKrates
                                            container: compile, setup, witness,
                                            proof and generate verifier
                                            contract. All the generated files
                                            are located inside the project
                                            folder.
  zoktools proof <name> [options]           Generates the proof for the project
                                            in the running ZoKrates container.
  zoktools setup <name> [options]           Performs the trusted setup for the
                                            project in the running ZoKrates
                                            container.
  zoktools trufflecompile <name> [dir]      Compiles the verifier in the local
  [options]                                 project folder. The output is placed
                                            in the local project's
                                            'contractbuild/' folder.
  zoktools verifier <name> [options]        Generates the verifier contract for
                                            the project in the running ZoKrates
                                            container.
  zoktools verify <address> [options]       Verifies a proof with the deployed
                                            verifier contract, using a local
                                            proof.json file.
  zoktools version                          Prints version number.
  zoktools witness <name> [options]         Generates the witness for the
                                            project in the running ZoKrates
                                            container.

Options:
  --version  Show version number                                       [boolean]
  --help     Show help                                                 [boolean]

You can invoke --help for each command separately.

zoktools full --help
> zoktools full <filepath> [outputdir] [options]

Performs a full cycle: copy to container -> generate (compile, setup, witness,
proof, verifier) -> copy from container.

Positionals:
  filepath, f   The local path to the .code source file.     [string] [required]
  outputdir, o  The output dir (local), where the project folder will be copied
                from the container.                           [string] [default:
              "/home/aznagy/.npm-global/lib/node_modules/zokrates-tools/build/"]

Options:
  --version      Show version number                                   [boolean]
  --help         Show help                                             [boolean]
  --name, -n     Name of the project folder and .code file to be created in the
                 container. By default it is taken from the input .code
                 filename. You can rename it though.                    [string]
  --witness, -w  List of witness params. Positional arguments to the
                 corresponsing ZoKrates command.[array] [required] [default: []]

An example

Using the supplied dummy.code circuit for testing:

zoktools full ./circuits/dummy.code -w 5 6 -o ~/build/zokbuilds
  1. This command copies the circuit file into the running ZoKrates container, into a created project folder ~/dummy, under the name dummy.code. This can be changed with the --name flag, otherwise it is taken from the circuit filename.
  2. The command invokes the compile, setup, witness, proof and verifier scripts. For the witness generation, the positional input params need to be passed. In this case it is 5 and 6. The files generated in each step stay in the project folder inside the container.
    dummy
    ├── dummy.code
    ├── out
    ├── out.code
    ├── proof.json
    ├── proving.key
    ├── variables.inf
    ├── verification.key
    ├── verifier.sol
    └── witness
  3. Copies the whole project folder from the container to a specified location, given by the -o flag.
zoktools trufflecompile dummy --dir ~/build/zokbuilds
  • This command compiles the verifier.sol file in the project folder which was copied from the container in the previous step. The JSON-ABIs are placed in the dummy/contractbuild/ folder. This step uses truffle for now but I will update it to a truffle free version later so it is not an annoying dependency.
zoktools deploy dummy --dir ~/build/zokbuilds

> Looking for verifier..
Verifier found!
Deploying from 0x0052569B2d787bB89d711e4aFB56F9C1E420a2a6..
Verifier deployed at:
0x49dce4FCADde346D7ff727b8a929F4e06f367631
  • The compiled verifier contract is deployed. Access to an ethereum node is needed. You are free to specify --from, --rpc or --gas.
zoktools verify 0x49dce4FCADde346D7ff727b8a929F4e06f367631 --dir ~/build/zokbuilds --name dummy
  • In this step we are verifying the proof.json with our deployed verifier contract.

Prerequisites

Contributing

Please read contributing and our code of conduct for details.

Getting started (as a dev)

Cloning the repo

git clone https://github.com/ngyam/zokrates-tools.git
cd zokrates-tools
npm install -D
npm run postinstall # patch for web3 js beta.37 
npm install -g [email protected] # if needed

Testing

Manually so far.

Make sure to start your container by either fetching it from dockerhub:

docker run -ti zokrates/zokrates:latest
# or: npm run start
# from the project folder

or building yourself from the checked out offical repo:

docker build -t zokrates .
docker run -ti zokrates /bin/bash

It is essential to tag it as zokrates in this case, cause the scripts are looking for it.

Versioning

SemVer.

License

This project is licensed under MIT - see the LICENSE file for details.