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

@vegaprotocol/crypto

v0.12.0

Published

Crypto operations for Vega supporting Node.js and Browsers

Downloads

36

Readme

@vegaprotocol/crypto

⚠️ Under active development ⚠️

Crypto operations for Vega supporting Node.js and Browsers

Usage

This module supports both CommonJS and ES Modules:

const { VegaWallet, HARDENED } = require('@vegaprotocol/crypto')

VegaWallet.fromMnemonic('...').then(async wallet => {
  const keys = await wallet.keyPair(HARDENED + 0)

  const msg = Buffer.from('Hello world!')
  const signature = await keys.sign(msg)
})
import { VegaWallet, HARDENED } from '@vegaprotocol/crypto'

const wallet = await VegaWallet.fromMnemonic('...')
const keys = await wallet.keyPair(HARDENED + 0)

const msg = Buffer.from('Hello world!')
const signature = await keys.sign(msg)

API

Note: All APIs are async. In some cases they will run sync, eg in Node.js where loading WASM is sync, or where crypto routines are sync, but everything is kept async as a lowest common denominator between browser APIs and future hardware wallet support.

const wallet = await VegaWallet.fromMnemonic(mnemonic)

Derive a new SLIP-10 VegaWallet from a BIP-0039 mnemonic. Note that the mnemonic is not validated before key derivation.

const seed = await VegaWallet.deriveSeed(mnemonic)

Derive a seed from a BIP-0039 mnemonic. In combination with VegaWallet.fromSeed this is equivalent to VegaWallet.fromMnemonic. Note that the mnemonic is not validated before key derivation.

const wallet = await VegaWallet.fromSeed(seed)

Derive a new SLIP-10 VegaWallet from a seed.

const kp = await wallet.keyPair(index)

Generate a new key pair at index, under the Vega specific subtree.

const { name, version } = kp.algorithm

This contains name and version detailing the version used by the instantiated keyPair. Note if this changes in the future other "builder" methods will be exposed to derive newer versions.

const sig = await kp.sign(msg, [chainId])

Sign msg with key pair kp for optional chainId.

const isValid = await kp.verify(sig, msg, [chainId])

Verify sig is valid for msg under key pair kp for optional chainId.

Spec

See algorithm.md and test-vectors.

License

MIT