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

l1beat-l1-registry

v1.2.4

Published

Community-maintained registry of Avalanche L1 chains

Readme

Avalanche L1 Chains Registry

A comprehensive, community-maintained registry of Avalanche L1 chains with detailed metadata, social links, and technical specifications.

Validate Chain Data License: MIT

Stats

  • Total L1 Chains: 116
  • Networks: Mainnet, Fuji
  • Last Updated: 2025-11-06

Structure

Each L1 chain has its own folder containing:

  • chain.json - Structured chain data
  • README.md - Human-readable documentation
l1-registry/
├── README.md (this file)
├── CONTRIBUTING.md (contribution guide)
├── LICENSE
├── .github/ (GitHub workflows & PR templates)
├── scripts/ (validation scripts)
└── data/ (all chain data)
    ├── _TEMPLATE/ (format reference)
    │   ├── chain.json
    │   └── README.md
    ├── dexalot/
    │   ├── chain.json
    │   └── README.md
    ├── beam/
    │   ├── chain.json
    │   └── README.md
    └── ... (116 L1 chains)

Data Format

chain.json

{
  "subnetId": "subnet-id-here",
  "network": "mainnet",
  "categories": ["DeFi", "Gaming"],
  "name": "Chain Name",
  "description": "Description of the chain",
  "logo": "https://cdn.example.com/logo.png",
  "website": "https://example.com",
  "socials": [
    { "name": "twitter", "url": "https://twitter.com/example" },
    { "name": "discord", "url": "https://discord.gg/example" }
  ],
  "chains": [
    {
      "blockchainId": "blockchain-id-here",
      "name": "Blockchain Name",
      "description": "Blockchain description",
      "evmChainId": 12345,
      "vmName": "EVM",
      "vmId": "vm-id-here",
      "sybilResistanceType": "Proof of Stake",
      "explorerUrl": "https://explorer.example.com",
      "rpcUrls": ["https://rpc.example.com"],
      "nativeToken": {
        "symbol": "TOKEN",
        "name": "Token Name",
        "decimals": 18,
        "logoUri": "https://example.com/token-logo.png"
      }
    }
  ]
}

Quick Start

Browse Chains

Simply browse the folders to explore different L1 chains. Each folder contains:

  • chain.json - Machine-readable data
  • README.md - Human-friendly documentation

Use the Data

# Clone the repository
git clone https://github.com/L1Beat/l1-registry.git

# Access any chain's data
cat l1-registry/data/dexalot/chain.json

# Use in your application
import chainData from './l1-registry/data/dexalot/chain.json';

Contributing

We welcome contributions! See CONTRIBUTING.md for detailed instructions.

Quick Contribution Guide

  1. Fork this repository
  2. Create a branch: git checkout -b add-your-chain
  3. Add/Update chain data in a folder (lowercase, hyphenated name)
  4. Validate your changes: ./scripts/validate-single.sh your-chain
  5. Commit: git commit -m "Add Your Chain to registry"
  6. Push: git push origin add-your-chain
  7. Create a Pull Request

Validation

Before submitting a PR, validate your chain data:

# Validate a single chain
./scripts/validate-single.sh data/your-chain-name

# Or validate everything (if you have Node.js)
npm run validate

Folder Naming Convention

Folder names must be:

  • Lowercase
  • Hyphenated (no spaces or special characters)
  • Descriptive

Examples:

  • defi-kingdoms
  • beam-subnet
  • dexalot
  • DeFi Kingdoms
  • Beam_Subnet
  • DEXALOT

Search & Filter

You can search for chains by:

  • Name: Check folder names or name field in chain.json
  • Category: Filter by categories like "DeFi", "Gaming", "NFT"
  • Network: Mainnet or Fuji
  • Subnet ID: Unique Avalanche subnet identifier

Categories

Available categories:

  • DeFi
  • Gaming
  • NFT
  • Metaverse
  • Infrastructure
  • Finance
  • Social
  • Identity
  • And many more...

Data Source

Initial data generated from SnowPeer AMDB API. Community contributions keep it up-to-date.

Data Quality

  • ✅ Automated validation via GitHub Actions
  • ✅ JSON schema validation
  • ✅ Required fields enforcement
  • ✅ Folder naming convention checks
  • ✅ Community review process

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

  • Data sourced from SnowPeer
  • Built for the Avalanche L1 ecosystem
  • Maintained by L1Beat

Contact


Made with ❤️ for the Avalanche community