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

@enclave-e3/contracts

v0.1.15

Published

Enclave is an open-source protocol for Encrypted Execution Environments (E3).

Readme

Enclave Smart Contracts

Importing the contracts, interfaces or types

To install, run

pnpm add @enclave-e3/contracts

If writing a new E3 program, you can import the necessary interfaces by writing something similar to:

import {
    IE3Program,
} from "@enclave-e3/contracts/contracts/interfaces/IE3Program.sol";

contract MockE3Program is IE3Program {...}

Check out the E3 mock for an example

To deploy

pnpm deploy --network [network]

This will add the deployment information to the ./ignition/deployments directory, as well as to the deployed_contracts.json file.

Be sure to configure your desired network in hardhat.config.ts before deploying.

Localhost deployment

If you are running Enclave locally, you can first start a local hardhat (or Anvil) node, then deploy the contracts using the following commands:

pnpm hardhat node
pnpm clean:deployments
pnpm deploy:mocks --network localhost

This will ensure that you are a local node running, as well as that there are no conflicting deployments stored in localhost.

Configuration

Using Environment Variables (Development)

For development, you can set your private key in a .env file:

# .env
PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80

Using Hardhat Configuration Variables (Production)

For production, it's recommended to use Hardhat's configuration variables system:

# Set your configuration variable (securely stored)
npx hardhat vars set PRIVATE_KEY

Then update hardhat.config.ts to use configuration variables:

import { vars } from "hardhat/config";

const privateKey = vars.get("PRIVATE_KEY", "");

Registering a Ciphernode

The tasks use the first signer configured in your Hardhat network configuration.

To add a ciphernode to the registry:

pnpm ciphernode:add --network [network]

Options:

  • --license-bond-amount: Amount of ENCL to bond (default: 1000 ENCL)
  • --ticket-amount: Amount of USDC for tickets (default: 1000 USDC)

For testing/development, you can also use the admin task to register any ciphernode address:

pnpm ciphernode:admin-add --network localhost --ciphernode-address [address]

To request a new committee, run

pnpm run hardhat committee:new --network [network]

To publish the public key of a committee, run

pnpm run hardhat --network [network] committee:publish --e3-id [e3-id] --nodes [node address],
[node address] --public-key [publickey]

To activate an E3, run

pnpm run hardhat --network [network] e3:activate --e3-id [e3-id]

To publish an input for an active E3, run

pnpm run hardhat --network [network] e3:publishInput --e3-id [e3-id] --data [input data]