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

da-commitment-node

v0.0.2

Published

- cargo install wasm-pack - chmod +x ./build_package.sh - ./build_package.sh <x.x.x> (eg. `./build_package.sh 0.1.0`) - If there is an issue: https://github.com/wasm-bindgen/wasm-bindgen/issues/4228#issuecomment-2693647441

Downloads

104

Readme

Generate da-commitment package and publish

  • cargo install wasm-pack
  • chmod +x ./build_package.sh
  • ./build_package.sh <x.x.x> (eg. ./build_package.sh 0.1.0)
  • If there is an issue: https://github.com/wasm-bindgen/wasm-bindgen/issues/4228#issuecomment-2693647441

Usage

build_commitments_js(data, params_version, babe_randomness, blob_hash) returns:

  • commitment
  • eval_point_seed
  • eval_claim

Simple Node usage:

import { build_commitments_js } from "da-commitment-node";
import { keccakAsU8a } from "@polkadot/util-crypto";

const text = "Hello World!";
const encoder = new TextEncoder();
const data = encoder.encode(text);
const paramsVersion = 0;
const babeRandomness = new Uint8Array(32); // replace with real BABE randomness from chain
const blobHash = keccakAsU8a(data);

const metadata = build_commitments_js(data, paramsVersion, babeRandomness, blobHash);

console.log(Buffer.from(metadata.commitment).toString("hex"));

Standalone build

If you just want to build locally by hand:

cd utils/da-commitment-js
cargo install wasm-pack
wasm-pack build --target nodejs --features wasm
mv pkg pkg_node

After that, the local Node package is in pkg_node.

JS example

There is a small JS example in examples/submit_blob_metadata.cjs.

It shows how to:

  • compute the FRI metadata with build_commitments_js
  • build dataAvailability.submitBlobMetadata
  • sign it
  • submit it with blob_submitBlob

You can tweak the constants at the top of the file if needed, for example:

  • WS_URL
  • TEXT
  • APP_ID
  • ERA_PERIOD

Install and run:

cd utils/da-commitment-js/examples
npm install @polkadot/api @polkadot/keyring @polkadot/util @polkadot/util-crypto
node submit_blob_metadata.cjs