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

@totemsdk/lookup-protocol

v0.1.3

Published

Wire protocol definitions for Totem lookup node ↔ client communication

Readme

@totemsdk/lookup-protocol

The wire protocol spec for the P2P lookup network.

Defines the complete binary message grammar for communication between @totemsdk/lookup-node servers and @totemsdk/lookup-client consumers. Import this in both server and client code to share typed message definitions, binary framing, and WOTS-signed message authentication.

Install

npm install @totemsdk/lookup-protocol

What's inside

Message families

| Family | Messages | |--------|----------| | Auth | HelloMessage, AuthChallengeMessage, AuthResponseMessage | | Chain queries | GetCoinsMessage, GetCoinMessage, GetProofMessage, GetTipMessage, GetTokenMessage | | Real-time | CoinUpdateMessage, WatchRegisterMessage, WatchRemoveMessage | | Relay | BroadcastTxPoWMessage | | Lease coordination | LeaseReserveMessage, LeaseCommitMessage, LeaseBurnMessage, LeaseWatermarkMessage | | App/Agent discovery | AppAnnounceMessage, AppQueryMessage, AgentAnnounceMessage, AgentQueryMessage | | Trust | TrustRecordMessage, TrustQueryMessage |

Binary framing

import { encodeMessage, decodeMessage, peekFrameLength } from '@totemsdk/lookup-protocol';

// Encode any typed message to a binary frame
const frame = encodeMessage({ type: 'GET_COINS', address: 'Mx...' });

// Peek length before reading full frame (for streaming parsers)
const len = peekFrameLength(buffer);

// Decode binary frame back to a typed message object
const msg = decodeMessage(frame);

WOTS-signed message authentication

import { messageDigest, signMessage, verifyMessageAuth } from '@totemsdk/lookup-protocol';

// Sign a message with a WOTS key
const digest = messageDigest(msg);
const signed = signMessage(msg, wotsPrivateKey, wotsIndex);

// Verify on the receiving end
const ok = verifyMessageAuth(signed);

See also