5678628b95
Feat/witness calculation removed
Former-commit-id: 4a162a833104922e38d3c5889b36bcd64f8b9eed [formerly 151571ab315831b6491df1cef8a8cee48608ce9f] [formerly f50400e7ad2ace7cb3f53ee9dc83999d9f171b3a [formerly 85c6ab88d17184621826e5bef223e5623e63268e]] [formerly 752eecf147646806a439f7f5d70c7ac2c823f0ea [formerly 4d065fda418640e82359dd213a1990292b805e29] [formerly 143b132d50ed7f1b55f510b3ec5474b0eee4c8df [formerly 01348d3483]]]
Former-commit-id: bbf5ec309b48e1272d2351f5dd8354aba77d4d77 [formerly 1bd5f2884e3101b2333a657f6bc73cbe39b86498] [formerly 690c73977f41e3ae9e6da2aefaad32ffbff156ca [formerly 80020325258c75eca0c9685ea1586a2c3da684c4]]
Former-commit-id: 028468897bce08a20c607fd27d9c170bd0fdc0be [formerly 6bda1aa342dc8ce0b361325ddfee9021a3f7ab34]
Former-commit-id: 2ba3bd73856961c4c0977eca8d24ba294c7f95f3
🧰 ZK-kit
A monorepo of reusable JS libraries for zero-knowledge technologies.
| ZK-kit is a set of NPM modules (algorithms or utility functions) that can be reused in different projects and zero-knowledge protocols, making it easier for developers to access ready-to-use and tested libraries for common tasks. |
|---|
♚ Simplified package management with Lerna (yarn, yarn build, yarn publish:fp)
♛ Conventional Commits for adding human and machine readable meaning to commit messages (yarn commit)
♜ Jest tests & common test coverage for all packages (yarn test)
♞ ESLint & Prettier to keep the code neat and well organized (yarn prettier & yarn lint)
♝ Automatic deployment of documentation generated with typedocs
♟ Simple benchmarking framework for JavaScript/TypeScript libraries with Benny (yarn benchmarks)
📦 Packages
🛠 Install
Clone this repository and install the dependencies:
$ git clone https://github.com/appliedzkp/zk-kit.git
$ cd zk-kit && yarn
📜 Usage
$ yarn lint # Syntax check with ESLint (yarn lint:fix to fix errors).
$ yarn prettier # Syntax check with Prettier (yarn prettier:fix to fix errors).
$ yarn commit # Interactive Commitizen commit.
$ yarn test # Test all packages (with common coverage).
$ yarn build # Create a JS build for each package.
$ yarn publish:fp # Publish packages on npm.
❓ FAQ
I have a library that could be reused in other projects. How can I integrate it on ZK-kit?
ZK-kit provides a set of pre-configured development tools. All you have to deal with is your own code, testing and documentation. To create a package follow these steps:
- Fork this repository and clone it (or simply clone it directly if you are a collaborator),
- Copy one of our current libraries and update the
README.mdandpackage.jsonfiles with your package name:
cd zk-kit
cp -r packages/sparse-merkle-tree packages/my-package
cd packages/my-package && rm -fr node_modules dist
grep -r -l "sparse-merkle-tree" . | xargs sed -i 's/sparse-merkle-tree/my-package/'
# Update the remaining description/usage sections, and write your code in the src & tests folders!
How can I test and publish my library?
ZK-kit provides two commands: yarn test and yarn publish:fp. Both must be run from the root folder. yarn test will test all packages in the monorepo, including yours using the files inside your packages/my-package/tests folder. yarn publish:fp can only be run by those who own the NPM token of the ZK-kit organization. They will then have to publish your package. This task could be automated in the future.
How can I create benchmarks for my library?
You can see some examples in the benchmarks folder. All you have to do is create a file that exports a function to run your benchmark in that folder, and add that function to the index.ts file. The yarn benchmarks command can be run with no parameters (it will run all the benchmarks), or you can specify the name of your benchmark file to run just that. When you run the command it will creates a benchmarks/results folder with your results.
How can I publish the documentation of my library with typedocs?
You just need to insert the NPM docs command in your package.json file, as in the other packages. This command will be executed by Lerna and the output of typedocs will be placed in the docs folder of the root directory, which will be used to deploy the documentation websites by the Github docs workflow whenever the main branch is updated.