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

@realitio/realitio-cli

v1.0.3

Published

Command-line tools for interacting with the Realitio fact verification platform. Mainly intended for doing arbitration from an offline computer.

Downloads

7

Readme

CLI Scripts

These scripts are intended for arbitrators doing offline operations.

They should be run by the owner of the Arbitrator contract. This should have been set after deployment by the deployer, eg with:

truffle console

Arbitrator.deployed().then(function(a){ arb=a;} ) arb.transferOwnership("0x8f6981b7d32eacf7d2169ca29cb8a8864131403d")

The Network ID on which they will be used and other parameters can be set in the config.json file.

Since they are intended to be offline, the scripts require you to manually pass in the nonce and gas price, rather than getting these automatically from the network. The nonce and gas price passed as parameters are sanity-checked based on settings in config.json. These settings may need to be adjusted.

The arbitrator's private key should be stored in the secrets directory, in the file specified in config.json.

The scripts are:

  • set_reality_check.js: Sets the default Reality Check contract
  • set_dispute_fee.js: Sets the default dispute fee
  • set_question_fee.js: Sets the question fee (we will probably initially leave this at 0, but it may become necessary if network fees drop and the list of open questions gets spammed.)
  • call_withdraw.js: Withdraws any accumulated question fees from the arbitrator's balance in the Reality Check contract to the Arbitrator contract
  • withdraw.js: Withdraws any balance held by the arbitrator contract to the designated address
  • arbitrate.js: Signs an arbitration transaction. Expects that the data it should sign will be in a file under requests/arbitration.json, so you only need to pass in its ID.

For usage information, run the script without parameters, eg node set_dispute_fee.js

If you're online and have a local node running, you can pipe the output direct to ./broadcast.sh to send it to your node. Otherwise you'd normally scan the qrcode and broadcast the tx via a block explorer etc