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

@sandbox-smart-contracts/giveaway

v1.0.0

Published

Contracts used for token claims

Downloads

98

Readme

Signed Giveaways

This is a hardhat project, see https://hardhat.org

The main contract gives rewards in any ERC20, ERC721 or ERC1155 when the backend authorize it via message signing.

The message is composed of:

  • A list of signatures. If the contract holt too much value more than one signature is needed. Ideally the systems that sign must be independent.
  • A list of claim ids used by the backend to avoid double spending.
  • Expiration the expiration time of the message in unix timestamp. After the expiration the message cannot be used anymore.
  • From: usually the rewards must be transferred to the contract and this value is address(this), if a strategy with approve and transfer is used this is the address of the source.
  • To: the destination address that will get the rewards.
  • Claims: A list of union structs (ClaimEntry) that include: token type (ERC20, ERC721, ERC1155, etc), token address and a data field that depending on the token type may have: amount, tokenId, etc.

Usage

yarn hardhat help
yarn hardhat test
yarn hardhat coverage
REPORT_GAS=true yarn hardhat test
yarn hardhat markup

Deployment

This package exports the contract source code, for deployments see: @sandbox-smart-contract/deploy package.