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

@mach-34/aztec-statechannel-tictactoe

v1.0.2

Published

## Installation ### 1. Ensure correct versioning of aztec-nargo CLI: ```console aztec-nargo -V // nargo version = 0.23.0 // noirc version = 0.23.0+602f23f4fb698cf6e37071936a2a46593a998d08 // (git version hash: ea6aebcc4e190d9dbadaf1dd0f70950651eed615,, is

Downloads

4

Readme

Aztec State Channels

Installation

1. Ensure correct versioning of aztec-nargo CLI:

aztec-nargo -V
// nargo version = 0.23.0
// noirc version = 0.23.0+602f23f4fb698cf6e37071936a2a46593a998d08
// (git version hash: ea6aebcc4e190d9dbadaf1dd0f70950651eed615,, is dirty: false)

You can run VERSION=0.21.0 aztec-up to ensure you have a valid aztec-nargo compiler cli

2. Set up the proper folder structure for the imports as they currently exist

// Once everything is installed, you should have:
PARENT_DIR/
  | - aztec-packages
  | - aztec-state-channels
// such that npm imports in statechannel can access the local aztec-packages build with `file:../aztec-packages/yarn-project/*`

3. Install the fork of aztec-packages that has compatible @aztec/* for statechannel repo and runs a modified PXE through the sandbox that supports the state channel construction

a. clone the repo in your parent dir: git clone https://github.com/mach-34/aztec-packages && cd aztec-packages

b. ensure you are on the right branch: git checkout app_circuit_pxe

c. build the entire aztec-packages stack locally: ./bootstrap.sh

  • This can take over an hour. If you have a compatible version of aztec-packages already built locally, you can skip 99% of build time by only building yarn_project: cd yarn_project && bootstrap.sh
  • You may experience issues building barretenberg. Visit the official aztec-packages/barretenberg README.md for some help with this

4. Install the Aztec State Channels repository in a new terminal window

a. in PARENT_DIR, run git clone https://github.com/mach-34/aztec-state-channels && cd statechannel

b. ensuring file:../aztec-packages/yarn-project/* will work for package.json, run npm i (yarn will not work)

Running Tests

1. Start Services

a. In a new terminal in the aztec-state-channels folder, run a local Ethereum dev node with npm run anvil

b. In a new terminal in the aztec-state-channels folder, run the sandbox (and first PXE) with npm run sandbox

c. In a new terminal in the aztec-state-channels folder, run a second PXE with npm run pxe:secondary

2. Run the aztec-state-channel unit tests

  • To run only the state channel tests, run npm run test:statechannel

  • To run only the contract logic unit tests, run npm run test:logic

  • To run all test suites, run the normal npm run test

Modifications / Methodology

PXE ACIR Simulator Iterations On Folding/ HONK