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

@big-whale-labs/ketl-allow-map-contract

v0.0.3

Published

Allow map contract for Ketl

Downloads

4

Readme

Allow Map ZKP for Ketl

Usage

  1. Clone the repository with git clone [email protected]:BigWhaleLabs/ketl-allow-map-contract.git
  2. Install the dependencies with yarn
  3. Add environment variables to your .env file
  4. Check out yarn generate-inputs script and modify it so that you get the correct inputs are generated for your circuits, then run yarn generate-inputs
  5. Run yarn compile to compile the circom circuits, create proof, verify proof, export verifier as a solidity Verifier.sol
  6. Run yarn test to run the test suits and make sure your circuits are robust
  7. Use the artifacts from the public folder in snarkjs
  8. Run yarn deploy to deploy the verifier smart contracts to blockchain
  9. Run yarn release to publish an NPM package with typings that can later be used in any of your JS/TS projects

Bonus

  • Check out scripts/compile-circuit.sh for complete understanding of what's going on when compiling the circuits
  • Feel free to increase/decrease tau factors in the pot folder as you number of constraints grows or shrinks

Environment variables

| Name | Description | | ---------------------------- | --------------------------------- | | ETHERSCAN_API_KEY | Etherscan API key | | ETH_RPC | Ethereum RPC URL | | CONTRACT_OWNER_PRIVATE_KEY | Private key of the contract owner |

Also check out the .env.example file for more information.

Available scripts

  • yarn build — compiles the contracts' ts interfaces to the typechain directory
  • yarn compile - compiles the circom circuit, creates proof, verifies proof, exports verifier as a solidity file, exports artifacts to the public directory
  • yarn test — runs the test suite
  • yarn deploy — deploys the contract to the network
  • yarn eth-lint — runs the linter for the solidity contracts
  • yarn lint — runs all the linters
  • yarn prettify — prettifies the code in th project
  • yarn release — relases the typechain directory to NPM