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

@nori-zk/ethereum-token-bridge

v0.0.9

Published

NoriTokenBridge contract

Readme

Nori Token Bridge - Source Contract

Exports

import { noriTokenBridgeJson } from '@nori-zk/ethereum-token-bridge';

Installation

npm install

Configuration

Env vars (create a .env file):

ETH_PRIVATE_KEY=
ETH_RPC_URL=
ETH_NETWORK=
  • ETH_PRIVATE_KEY: Ethereum contract deployer private key
  • ETH_RPC_URL: Ethereum RPC endpoint
  • ETH_NETWORK: Ethereum network label e.g. 'holesky'

Testing

npm run test

Build

npm run build

Deploy

Make sure your .env is set to deploy to the correct network.

npm run deploy

You will see output something like:

Running on network "holesky"
Using RPC URL: https://ethereum-holesky.core.chainstack.com/<api-key>
One private key loaded for deployment.
Deploying with account: 0xC7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Deployer balance: 100.0 ETH
Network: holesky (chainId: 17000)
NoriTokenBridge deployed to: 0xfCxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Deployed in block: 3840406
Gas used for deployment: 296589

A file .env.nori-token-bridge will have been created with NORI_TOKEN_BRIDGE_ADDRESS set within it.

Lock (for testing purposes)

Make sure your .env is set to deploy to the correct testing network. Copy NORI_TOKEN_BRIDGE_ADDRESS from the deploy stage. Also you must add NORI_TOKEN_BRIDGE_TEST_MODE=true to run this test facility.

npm run test:lock <attestationHashHex> <optionalAmountToLock (defaults to 0.000001)>

npx hardhat --network $ETH_NETWORK lockTokens <attestationHashHex> <optionalAmountToLock (defaults to 0.000001)>

One can (again for testing purposes) lock periodically in a loop, every 383 seconds (approximately once every consensus period):

npm run test:lock-loop <attestationHashHex>

Caution this is just a test facility, don't lock real ETH using this process.

Get total deposited

Ensure NORI_TOKEN_BRIDGE_ADDRESS is within your .env file.

npm run get-deposited <depositorAddressHex> <attestationHashHex>

e.g. npm run get-deposited 0xc7e910807dd2e3f49b34efe7133cfb684520da69 0x13cceb5b591e742c13fd7f3894f97139c964606f2928eefdc234e8a3a55c10b1

Withdraw

Ensure NORI_TOKEN_BRIDGE_ADDRESS and ETH_PRIVATE_KEY are within your .env file.

npm run withdraw

Package details

This package exports a single variable, noriTokenBridgeJson, which is a Hardhat artifact JSON object representing the compiled contract metadata (ABI, bytecode, etc.).

It is provided as an ES module export, allowing you to import it using ES module syntax.