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

parsec-node

v2.2.2

Published

https://parseclabs.readthedocs.io/en/latest/

Downloads

64

Readme

PARSEC Labs validation node

https://parseclabs.readthedocs.io/en/latest/

Prerequisite

  • Node.js 8+
  • build-essential
  • Python 2.X (required by node-gyp, only for building)

Install

npm install parsec-node -g or yarn global add parsec-node

Run locally

parsec [ARGS] --config=path-to-config.json

Debug

To enable logs use DEBUG env variable (see: https://www.npmjs.com/package/debug). Debug namepaces:

  • tendermint
  • parsec
  • parsec:period
  • parsec:tx
  • abci (built-in from js-abci)

Example: DEBUG=tendermint,parsec:tx parsec

Available cli arguments

  • no-validators-updates — disabling validators set updates (default: false)
  • port — tx endpoint port (default: 3000)
  • rpcaddr — host for http RPC server (default: localhost)
  • rpcport — port for http RPC server (default: 8645)
  • wsaddr — host for websocket RPC server (default: localhost)
  • wsport — port for websocket RPC server (default: 8646)
  • p2pPort — port for p2p connection (default: random)
  • config — path to config file
  • version — print version of the node

Config file options

  • bridgeAddr — parsec bridge contract address
  • rootNetwork — ethereum provider url
  • genesis — genesis string
  • network — network id
  • peers — array of peers

Config presets

Dev config file: parsec-testnet-beta.json

Testnet config file: N/A

Mainnet config file: N/A

Run in the cloud

You can use Terraform to spin up an Amazon EC2 instance with the node. You will need an SSH keypair to access the EC2 instance. Generate a new keypair or use an existing one.

terraform init setup/cloud
terraform apply -var ssh_public_file="~/.ssh/parsec-testnet.pub" -var ssh_private_file="~/.ssh/parsec-testnet" -var network="testnet-beta" setup/cloud

Some useful commands once it is up and running:

  • check the logs: ssh ubuntu@<ec2 host> journalctl -u parsec
  • start/stop/restart/status: ssh ubuntu@<ec2 host> sudo service parsec start/stop/restart/status

Dive in development

https://github.com/parsec-labs/parsec-contracts/wiki/Setting-up-local-development-environment

Staking UI

Dev: http://stake-dev.parseclabs.org/

Testnet: N/A

Mainnet: N/A