5d4faaf8ea
fix(incremental-merkle-tree): merkle tree supports zero leaves. Merkle proof fails for zero value
Former-commit-id: a961f107c8492c42eda3490e5f7aa46b4b0740c2 [formerly 9a10c338213a5c9825a49828a6a245386644aa8b] [formerly 60f9f95acc12b3d68e99c79f2860399c36e6a9ad [formerly 20bb55989daea35b64f06e95849118f12eca2320]] [formerly 7d21551201bfefa64ba3f53210c92fb7554ee0b4 [formerly 2df22ec07e8794443367938b5ef0f5984d9cd18c] [formerly 7d009ae578934827c5fef0ed8389961570f21bf8 [formerly 82ee0269a8]]]
Former-commit-id: 019791c05ecb53501b3784ff83ba2a710de90abc [formerly f0f7180505cea32fdb5b6f6420351570ce6e1561] [formerly 753d122f771435017881938840cd7d12b156470c [formerly 6723a76e5c9adedf9a007635cdebade8818b38c3]]
Former-commit-id: 457be8dbcd29c48ec70dfd0eb7565fe94a4f748a [formerly a35642b4ee9fb9915cd3fd8312072c337613ca2f]
Former-commit-id: a4fffb7a5501b879068886926f91741c6f368f72
🧰 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.