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

@crate-crypto/crypto-4844

v0.2.0

Published

Cryptography needed for EIP4844

Downloads

5

Readme

JS Proto Danksharding

This is a pure* typescript version of EIP4844. It is ESM compatible and the speed is acceptable for web usage.

*pure it uses WASM for one function.

Exceptions

Currently the code does not throw unless it would indicate a bug. The effect of this is that many of the functions return T | Error. This means that the caller needs to explicitly check for errors and decide if they want to throw or not.

This decision was intentional, however if it is more conventional to throw, we can do this at the API level.

API

The API is still in flux, currently it takes in types like Bytes48 which can be created from a Uint8Array. It may be easier for the caller, if we have an API which is pure Uint8Array and we either throw and exception or return an error when we convert it to fixed size types.

Installation

npm install @crate-crypto/crate-4844

Example usage

// Taken from tests/index.test.ts
import { Context } from "../src/index.js"

let context = new Context()
let blob = ...
let { proof, commitment } = assertNoErrorThrow(context.computeBlobKZGProf(blob))
let result = context.verifyBlobKZGProof(blob, commitment, proof)
expect(result).to.not.be.instanceOf(Error)