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

@pooltogether/merkle-distributor

v1.0.2

Published

📦 A smart contract that distributes a balance of tokens according to a merkle root

Downloads

11

Readme

@pooltogether/merkle-distributor

Tests Lint

This project contains the distribution, code, and deployment scripts for the PoolTogether retroactive token claims. The BigQuery output was generated by the Retroactive Query

Setup

Install Dependencies

$ yarn

Compile Contracts

$ yarn compile

Run Tests

$ yarn test

Verify the output from the Retroactive Query

The file bq-results-20210202-094742-fvr9ifm390n3.json contains the full set of rows (ordered by address ascending) of the Retroactive Query. You can follow the steps in that project to generate this file.

In this repo the file merkle_tree.json is generated from the BigQuery output and fed into the contract deployment script. You can generate the merkle proof file yourself using the steps below.

Generate Merkle Proof

First pre-process the BigQuery results (the file is missing commas):

$ ts-node ./scripts/pre-process-json.ts -i bq-results-20210202-094742-fvr9ifm390n3.json > bq-results.processed.json

Now generate a merkle proof blob:

$ ts-node ./scripts/generate-merkle-root -i bq-results.processed.json > merkle-proof.generated.json

You can compare your proof to the committed proof:

$ diff merkle-proof.generated.json merkle_tree.json

You will not see any differences!

Deploy the Contract

The contract deployment script consumes the merkle_tree.json file as the distribution. Make sure this file exists before running the deploy script.

You can deploy to rinkeby:

$ yarn deploy rinkeby

Or you can deploy to mainnet:

$ yarn deploy mainnet