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

snap-checker

v1.5.2

Published

Synchronized Network Accounting Protocol

Downloads

3

Readme

Synchronized Network Accounting Protocol (SNAP)

Deploy Tests

NPM package: snap-checker

An implementation of the Synchronized Network Accounting Protocol (SNAP).

Usage: see example

The most basic unit is the Transaction:

type Transaction = {
  amount: number;
  condition?: string; // 32-byte hex sha256
  expiresAt?: Date;
};

Transactions go through state transitions:

type StateTransition = {
  transId: number;
  newState: SnapTransactionState;
  amount?: number;
  condition?: string;
  preimage?: string;
  expiresAt?: Date;
};

Valid combinations:

  • Proposer -> Decider: transId, newState=Proposing, amount, unit.

  • Proposer -> Decider: transId, newState=Proposing, amount, unit, condition.

  • Proposer -> Decider: transId, newState=Proposing, amount, unit, expiresAt.

  • Proposer -> Decider: transId, newState=Proposing, amount, unit, condition, expiresAt.

  • Proposer <- Decider: transId, newState=Proposed.

  • Proposer <- Decider: transId, newState=Accepting (if the Propose did not have a condition).

  • Proposer <- Decider: transId, newState=Accepting, preimage (if the Propose did have a condition).

  • Proposer -> Decider: transId, newState=Accepted.

  • Proposer <- Decider: transId, newState=Rejecting.

  • Proposer -> Decider: transId, newState=Rejected.

A SimplexWatcher will watch the transactions from one specific proposer to one specific decider in one specific currency. It can report the sum of all transactions, including/excluding all committed, pending, and rejected transactions, respectively. It will throw an error if:

  • a transaction will make the sum of committed + pending transactions go over the max,
  • a transaction is accepted after it has expired, or
  • a transaction is accepted without satisfying its condition.

A ChannelWatcher combines two SimplexWatchers into a duplex channel. It takes two trust levels and adaptively sets the max of each SimplexWatcher as transactions go back and forth. It can report on current, payable, and receivable balance.

A SnapChecker combines an append-only message log with one ChannelWatcher per combination of (sender, receiver, unit). It has one public method, processMessage, which takes a log entry of the following type:

type SnapMessageLogEntry = {
  stateTransition: StateTransition;
  time: Date;
  from: string;
  to: string;
  unit: string;
};

You can replay a historical message log through a SnapChecker and it will arrive at the same combination of balances for each combination of (sender, receiver, unit).