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

@cryptech.services/bitcoin-rpc

v1.1.0

Published

A simple, efficient, zero-dep Bitcoin RPC interface.

Downloads

6

Readme

GitHub license npm version GitHub last commit (branch) Node.js CI

bitcoin-rpc

A simple, efficient, zero-dep Bitcoin RPC interface.

Why?

Most other Bitcoin RPC libraries either:

  • Have unnecessary dependencies.
  • Don't follow proper standards (silent RPC errors, strange Promise handling, etc).
  • Have hardcoded RPC commands, meaning the lib must be upgraded every time the RPC daemon changes, seriously?

But why fork it?

TypeScript compilation allows the types to be easily exported, meaning that when the library updates, users of it won't have to update their types definitions manually in a separate file.

How?

import RPC from '@cryptech.services/bitcoin-rpc';

// Create a new RPC class for a Bitcoind RPC daemon
//                      user    pass      host      port
const btcRPC = new RPC('user', 'pass', '127.0.0.1', 8332);

// EXAMPLE: Fetch the latest block count
btcRPC.call('getblockcount').then((nBlocks) => {
  console.log("There's " + nBlocks + ' blocks in the blockchain, nice!');
});

// EXAMPLE: Fetch a raw block based on it's block hash
btcRPC
  .call(
    'getblock',
    '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f'
  )
  .then((cBlock) => {
    console.log(cBlock);
  });

// EXAMPLE: Asynchronously fetch the latest block count
async function getBlockCount() {
  const nBlocks = await btcRPC.call('getblockcount');
  console.log("There's " + nBlocks + ' blocks in the blockchain, nice!');
}