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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@terminallyonline/plug-core

v0.5.4

Published

> [!NOTE] > This repository is a submodule of the larger [Plug monorepo](https://github.com/terminally-online/plug) that contains all the required pieces to run the entire Plug stack yourself.

Readme

[!NOTE] This repository is a submodule of the larger Plug monorepo that contains all the required pieces to run the entire Plug stack yourself.

The core package of Plug powers the building and verification of declarative messages in both a server-context and interactive-wallet environment using the connected wallet when possible.

Dependencies

In order to run @terminallyonline/plug-core it is necessary to install all of the following dependencies first:

├─ foundry - "Foundry is a blazing fast, portable and modular toolkit for Ethereum application."
└─ pnpm — "Efficient package manager for Node modules."

Deployment

The deployment pipeline of Plug is setup to be as simple as possible and multichain by default. There is a single script to run (for the current version) that will deploy all the instances of the implementation based contracts. Because we are using CREATE2 for deployments it does not matter who sends the transaction.

forge script \
    --chain <chain_name> \
    --rpc-url <rpc_url> \
    --broadcast \
    -vvvv \
    src/contracts/script/Plug.s.sol

If you don't care about verifying the contract right now you can skip this step. Please don't skip it unless you're doing something for development. When you want to verify the contract so you will need to add an ETHERSCAN_API_KEY to your .env and include the --verify tag when running the deployment script.

When you are setting everything up you will want to remove the --broadcast so that it just simulates everything and you can confirm you have everything setup right before running a transaction.

Built into the scripts are redeploy protection so if you are running a batch deploy and one succeeds, but one fails, you can just rerun the same script.

Addresses

All contracts that should be deterministic are. That means Plug.sol, Plug.Factory.sol and the base Plug.Socket.sol are all found at constant addresses across chains. The only time the address will change when a new version is deployed. This will happen most common for the Socket, but we will always keep the list updated.

[v0.5.4]:
├─ Mining Configuration:
│  ├─ Leading Zeros: 4
│  ├─ Total Zeros: 8
│  ├─ Factory: 0x0000000000ffe8b47b3e2130213b802212439497
│  └─ Quick Mode: Yes
│
└─ Contracts:
   ├─ Plug.Assert.sol [256] — "0x00000000E830C2dFfa9B69cF0a5eD7323ee5221C"
   ├─ Plug.Boolean.sol [256] — "0x0000000062b4cde8cf8AAB13CADC85bbfD5FeeE9"
   ├─ Plug.Coercion.sol [256] — "0x0000000021113D96a58E15F40b50af1149b34EA8"
   ├─ Plug.Database.sol [256] — "0x00000000507376e5E3106CAb060E8369e9ffb6e0"
   ├─ Plug.EVM.sol [256] — "0x000000005f138dC65676f1a4e6C523483B629F2A"
   ├─ Plug.Factory.sol [256] — "0x00000000D29C274c206F51528868E84651798292"
   ├─ Plug.Math.sol [256] — "0x00000000377FF51f3d4F23F0c963eD9d0CD6Bb34"
   ├─ Plug.Socket.sol [256] — "0x00000000E0397b53F8845cD642Fd1e09be1F59FF"
   ├─ Plug.Ticket.sol [4217] — "0x0000000048ff6276eF007caA363f659298F9753f"
   ├─ Plug.Time.sol [256] — "0x00000000c31784854546e6b1ffCa11917d2DfDD7"
   └─ Plug.sol [256] — "0x00000000F10e32471c86cE1d110D27f5D03e1A72"