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

fullnode

v0.14.2

Published

Javascript implementation of Bitcoin.

Downloads

97

Readme

Fullnode

Fullnode is a javascript implementation of bitcoin intended to satisfy certain goals:

  1. Bring the blockchain to web browsers and node.js in a decentralized, trust-minimized manner, without the required use of a third-party API.

  2. Support ease-of-use by being internally consistent. It should not be necessary to read the source code of a class or function to know how to use it. Once you know how to use part of the library, the other parts should feel natural.

  3. Have 100% test coverage, or nearly so, so that the library is known to be reliable. This should include running standard test vectors from the reference implementation.

  4. Library objects have an interface suitable for use with a command-line interface or other libraries and tools, in particular having toString, fromString, toJSON, fromJSON, toBuffer, fromBuffer, toHex, fromHex methods.

  5. All standard features of the blockchain are implemented (or will be) and saved in lib/. All BIPs are correctly implemented and, where appropriate, saved as bipxx.js in lib/ (since that is their standard name). In order to allow rapid development, Fullnode includes non-standard and experimental features. Any non-standard features (such as colored coins or stealth addresses) are labeled as such in index.js as well as in comments.

  6. Expose everything, including dependencies. This makes it possible to develop apps that require fine-grained control over the basics, such as big numbers and points. However, it also means that you can hurt yourself if you misuse these primitives.

  7. Use standard javascript conventions wherever possible so that other developers find the code easy to understand.

  8. Minimize the use of dependencies so that all code can be easily audited.

  9. All instance methods modify the state of the object and return the object, unless there is a good reason to do something different. To access the result of an instance method, you must access the object property(s) that it modifies.

Fullnode is still being developed and does not yet support downloading the blockchain.

Environment Variables

  • FULLNODE_JS_BASE_URL - Default "/".
  • FULLNODE_JS_BUNDLE_FILE - Default "fullnode.js"
  • FULLNODE_JS_WORKER_FILE - Default "fullnode-worker.js"
  • FULLNODE_JS_BUNDLE_MIN_FILE - Default "fullnode-min.js"
  • FULLNODE_JS_WORKER_MIN_FILE - Default "fullnode-worker-min.js"
  • FULLNODE_NETWORK - Default "mainnet"

You can change the network to run the CLI in testnet mode:

FULLNODE_NETWORK=testnet ./bin/fullnode.js

Documentation

While Fullnode is under heavy development, the API changes frequently, and the documentation is not kept up-to-date. However there is some documentation, and it can be built with groc:

npm install -g groc
groc