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

@nilfoundation/evm-placeholder-verification

v1.1.2

Published

=nil; Foundation's Placeholder Proof System In-EVM Verifier

Downloads

15

Readme

EVM Placeholder proof system verifier

Discord Telegram Twitter

An application for in-EVM validation of zero-knowledge proofs generated with the Placeholder proof system.

Dependencies

  • Hardhat
  • Node.js - Hardhat requires an LTS version of Node.js; as of September 2023 it's v18

Contract Addresses

| Network | Address | | ----------- | ----------- | | Sepolia | 0x489dbc0762b3d9bd9843db11eecd2a177d84ba2b |

Installing with npm

You can install the package via npm from the command line:

npm install @nilfoundation/[email protected]

or add it to the package.json file manually:

"@nilfoundation/evm-placeholder-verification": "1.1.1"

Contributing

Clone the project from GitHub:

git clone [email protected]:NilFoundation/evm-placeholder-verification.git

After that, navigate to the evm-placeholder-verification directory:

cd evm-placeholder-verification

Install dependency packages

npm i

Compile contracts

npx hardhat compile

Deploy

Launch a local network using the following command:

npx hardhat node

Don't close the terminal and don't finish this process, the Hardhat node should be running for the next steps.

To deploy to a test environment (Ganache, for example), run the following from another terminal:

npx hardhat deploy --network localhost

Hardhat reuses old deployments by default; to force re-deploy, add the --reset flag to the command.

Testing

Tests are located in the test directory. To run tests:

npx hardhat test # Execute tests
REPORT_GAS=true npx hardhat test # Test with gas reporting

Local verification of zkLLVM circuit compiler output

zkLLVM compiler prepares circuits as instantiated contracts that can be deployed to a blockchain.

Once you get zkLLVM output, create a circuit directory under contracts/zkllvm for your output. That directory should contain the following files:

* proof.bin — Placeholder proof file
* circuit_params.json — parameters file
* public_input.json — file with public input
* linked_libs_list.json — list of external libraries that have to be deployed for gate argument computation
* gate_argument.sol, gate0.sol, ... gateN.sol — Solidity files with gate argument computation

If all these files are in place, you can deploy the verifier app and verify the proofs. You only need to deploy the verifier once, and then you can verify as many proofs as you want.

Deploying the contracts:

npx hardhat deploy

If you've put the files under, let's say, contracts/zkllvm/circuit-name directory, you can verify the proofs with the following:

npx hardhat verify-circuit-proof --test circuit-name

To verify all circuits from contracts/zkllvm directory, run:

npx hardhat verify-circuit-proof-all

Community

Submit your issue reports to the project's Github Issues.

Join us on our Discord server or in our Telegram chat and ask your questions about the verifier's usage and development.