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

@wetrustplatform/charity-challenge-contracts

v0.4.2

Published

charity challenge contracts

Downloads

9

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

sihoangsihoang

Keywords

Readme

charity-challenge-contract

  • Smart contract is associated with
    • one challenge,
    • one NPO address,
    • 1 owner for safety hatch 2

--

  • Users send ETH to our smart contract. No ERC20.
  • Smart contract records who sends how much.

--

  • After period P1, contract stops accepting money. One person (anyone who wants to pay for gas) can trigger the "finalize" method which determine where the fund would be sent to.
    The method "finalize" will check for the result of our Augur bet and then determine whether to 1) Refund. 2) Forwarder to a predefined NPO's address.

  • Scenario 1: Each contributor will need to trigger the "claim" method to get ETH back.

  • Scenario 2: ETH is sent to NPO. This can be coupled with the "finalize" call or a separate call depending on the gas limit.

--

  • Safety hatch 1: In case Augur's contract messed up. After period P2 (>P1), if money hasn't moved to the NPO's address (due to unexpected issues from the oracles), each contributor can claim ETH back like Scenario 1 (or TBD?).

--

  • Safety hatch 2: Something really really wrong that prevent users from claiming ETH or forwarding to NPO. After period P3 (a lot greater than P2), the contract's owner or Vitalik (we know his public address) can claim it and it's up to the taker to decide what to do with the money. Implement designated contract's owner!