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

ethproof

v0.0.4

Published

A node module for server-side proof of existence (with timestamping) on the Ethereum blockchain.

Readme

ethproof

NPM version NPM downloads CircleCI codecov

This module helps you publish Proof Of Existence transactions on the Ethereum blockchain. These create a permanent record of a document hash at a specific date and time, allowing you to prove when it was originally written.

For example, you may use this technique to document an invention or intellectual property to verify in the future the date at which you first created it. The only information about your data which is stored on the chain is the documents SHA256 hash.

Install

npm install --save ethproof

Usage

ES6

import {hashDocument, publishProof} from 'ethproof'

const privateKeyHex = '774a1dee2b3a3d6c64c0e47124d3ac7522ae5c57e1fef1c4abb1b3dd63bffee6';
const destinationAddress = '44241d4e6a0fd2acff819478a87b7cdfe7963468';
const document = Buffer.from('Hello Crypto! ' + Math.random().toString());

const documentHash = hashDocument(document);
const txHash = publishProof(privateKeyHex, destinationAddress, documentHash);

ES5

var ethproof = require('ethproof');

var privateKeyHex = '774a1dee2b3a3d6c64c0e47124d3ac7522ae5c57e1fef1c4abb1b3dd63bffee6';
var destinationAddress = '44241d4e6a0fd2acff819478a87b7cdfe7963468';
var document = Buffer.from('Hello Crypto! ' + Math.random().toString());

var documentHash = ethproof.hashDocument(document);
var txHash = ethproof.publishProof(privateKeyHex, destinationAddress, documentHash);

The above examples provide no JSON RPC URI to the publishProof(...) call. As such they default to localhost and default port. If you would like to use Infura or any other custom URI pass it as the final parameter. For example:

var txHash = publishProof(privateKeyHex, destinationAddress, documentHash, 'https://rinkeby.infura.io/');

If the transaction can not be sent, an error will be thrown and can be handled with try {...} catch (err) {...}

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Use npm test to run linting and tests.

Author

ethproof © Stefan Gordon, Released under the MIT License. Authored and maintained by Stefan Gordon with help from contributors (list).

github.com/stefangordon · GitHub @Stefan Gordon · Twitter @stefangordon