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

@dcspark/catalyst-registration-js

v1.0.2

Published

A Javascript library reference implementation for CIP-15

Downloads

7

Readme

Catalyst Registration

This is a JS implementation of the Catalyst registration logic as defined in CIP15.

This package requires you to inject cardano-serialization-lib for the cryptography.

Install

npm i @dcSpark/catalyst-registration-js --save

Usage

Create encrypted key

import * as cip15 from "@dcSpark/catalyst-registration-js";
import CSL from "@emurgo/cardano-serialization-lib-nodejs";

// either get a user-selected PIN code or random one
const pin = cip15.generatePin(); // ex: [1,1,1,1]

// encryption key from the pin
const passBuff = Buffer.from(pin);

// generate a key for Catalyst
const catalystKey = cip15.generatePrivateKeyForCatalyst(CSL);

// encrypt the key with the pin
const encryptedKey = await cip15.encryptWithPassword(passBuff, catalystKey.as_bytes());

Create registration metadata (software wallet)

import * as cip15 from "@dcSpark/catalyst-registration-js";
import CSL from "@emurgo/cardano-serialization-lib-nodejs";

const catalystKey = ... // CSL.PrivateKey
const stakePrivateKey = ... // CSL.PrivateKey
const rewardAddresss = ... // CSL.RewardAddress
const slotNumber = ... // number

const metadata = cip15.generateRegistrationMetadata(
    CSL,
    Buffer.from(catalystKey.to_public().as_bytes()).toString(
      "hex"
    ),
    Buffer.from(stakePrivateKey.to_public().as_bytes()).toString("hex"),
    Buffer.from(rewardAddresss.to_address().to_bytes()),
    slotNumber,
    (hashedMetadata) => stakePrivateKey.sign(hashedMetadata).to_hex()
  );

Create registration metadata (hardware wallet)

import * as cip15 from "@dcSpark/catalyst-registration-js";
import CSL from "@emurgo/cardano-serialization-lib-nodejs";

const catalystKey = ... // CSL.PrivateKey
const stakePrivateKey = ... // CSL.PrivateKey
const rewardAddresss = ... // CSL.RewardAddress
const slotNumber = ... // number

const metadata = cip15.generateRegistrationMetadata(
    CSL,
    Buffer.from(catalystKey.to_public().as_bytes()).toString(
      "hex"
    ),
    Buffer.from(stakePrivateKey.to_public().as_bytes()).toString("hex"),
    Buffer.from(rewardAddresss.to_address().to_bytes()),
    slotNumber,
    (_hashedMetadata) => {
      // for hardware wallets, we have to include dummy data
      // since the signature will be replaced later by the hardware wallet itself
      return '0'.repeat(64 * 2);
    }
  );
 
// you will have to call the above-function twice. Once with mock data (as shown) and once with data you get from the hw wallet