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 🙏

© 2026 – Pkg Stats / Ryan Hefner

libra-offlinesign-provider

v0.0.2

Published

libra offline sign provider

Readme

OfflineSignProvider

This is a customized Ethereum web3-provider to facilitate separation of business layer and wallet layer

Install

$ npm install libra-offlinesign-provider

General Usage

You can use this provider wherever a Web3 provider is needed.

const config = require('../config');
var Web3 = require('web3');
var nodeUrl = 'http://127.0.0.1:8545';

var web3 = new Web3(new Web3.providers.HttpProvider(nodeUrl));

var abi = require("./contract.json");
var TruffleContract = require("truffle-contract");

var signServiceUrl = 'http://127.0.0.1:8080/api/pearl/v1/eth/sign_transaction';

var providerNew = new OfflineSignProvider(nodeUrl, signServiceUrl, [account1,account2,...], config.aesKey, false);

var contractAddress = "0xafc60ddf39e7a953c4d341f2f4a80accf3432b76";
var myContract = TruffleContract({ abi: abi });
myContract.setProvider(providerNew);
myContract.defaults({ from: "0xd7358e66c2ec3e398b39567b0c9f53a8e8c6000f" });
var web3 = new Web3(providerNew);

myContract.at(contractAddress).then(function (instance) {
                console.log(instance)
            }).catch(e => {
                reject(e);
            });
            

Parameters:

var providerNew = new OfflineSignProvider(nodeUrl, signServiceUrl, [account1,account2,...], config.aesKey);

param1: The eth network node url.

param2: The signature service url.

param3: Array format account address, that sign service will use one of them to signature the transaction data .

param4: AES key defined with the signature service.

param5: Use 0Ex or not.