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

bitcore-payid

v1.0.0

Published

Bitcore library for PayID

Downloads

6

Readme

Bitcore PayID

This is a library to assist PayId integration with Bitcore

Setup

npm install

Usage

Sign

  • Bitcore key
import Bitcore from 'bitcore-lib';
import PayId from 'bitcore-payid';

const privKey = new Bitcore.HDPrivateKey(); // or Bitcore.PrivateKey() for a non-hierarchically derived private key

const signed = PayId.sign('alex$example.com', 'bitcoinaddress123', 'BTC', privKey.toString());
  • Node crypto key
import crypto from 'crypto';
import PayId from 'bitcore-payid';

const keys = crypto.generateKeyPair('ec'); // could be 'rsa' too
const privKey = keys.privateKey.export({ format: 'pem', type: 'pkcs8' });

const signed = PayId.sign('alex$example.com', 'bitcoinaddress123', 'BTC', privKey);
  • From file
import fs from 'fs';
import PayId from 'bitcore-payid';

const privKey = fs.readFileSync('/path/to/private/key');

const signed = PayId.sign('alex$example.com', 'bitcoinaddress123', 'BTC', privKey);

It is recommended to store the signed.signatures' signatures and protected properties. protected can be thought of as the public key to verify the signature because it contains the ingredients to build the public key as a JWK, but you could also discard the protected property if you intend to rebuild it at verification time.

Verify

verifiableAddress can be manually constructed as a IVerifyPayId object or a JWK.GeneralJWS object from the jose library. Note that the bitcore-payid sign method above returns a JWK.GeneralJWS object.

import PayId from 'PayId';

// ...

const isValid = PayId.verify('alice$example.com', verifiableAddress);