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

biteasy-unofficial

v1.2.6

Published

A Biteasy adapter built to standardize requests to follow the common-blockchain convention

Downloads

11

Readme

biteasy-unofficial

Version

A Biteasy adapter built to standardize the output of requests to follow the common-blockchain convention. Aliases are introduced in the return of functions to account for differences in convention between the two standards. It is our hope that the Bitcoin community will come to an agreement on proper style and convention for requests on addresses, transactions, and blocks.

Information on common-blockchain for convention

Installation

Install as you normally install an npm module:

  npm install biteasy-unofficial

Usage

Run npm install to have all necessary node modules installed.

To use the Biteasy API, simply require the module.

  var biteasyAPI = require('biteasy-unofficial');
  var commonBlockchain = biteasyAPI({ network: 'mainnet' });

For Mainnet, use biteasyAPI({ network: 'mainnet' }) when calling a function. For Testnet, use biteasyAPI({ network: 'testnet' }) when calling a function. By default, if no parameter is provided, Mainnet will be used.

Known Issues

Biteasy currently only returns the confirmed balance of an address when requested. Therefore, our parameters for balance, confirmedBalance, and unconfirmedBalance are specified as such:

  {
    balance: null,
    confirmedBalance: 0.0,
    unconfirmedBalance: null
  }

Tests

Run npm test to have abstract-common-blockchain run a suite of tests on Addresses, Blocks, and Transactions. The tests are comprehensive with complete code coverage - see documentation in abstract-common-blockchain for further details.

API Examples

See abstract-common-blockchain for API

There are examples for using Addresses, Blocks, and Transactions, provided in the /examples folder. Each function includes a Mainnet and Testnet sample call and where possible, an invalid example is provided to show error handling. Expect all returns to be of the form (error, response).

Request Limits

Biteasy has a request limit of 4 requests per second and 345600 requests per day per IP. Therefore, large arrays of inputs to biteasy-unofficial may result in errors or long wait times for responses due to the constricted nature of Biteasy's request limit.

Information on Biteasy Request Limits

Convention

Standard convention is described fully by common-blockchain in the types.json file: https://github.com/blockai/common-blockchain/blob/master/types.json

Maintainers