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

@kumbaya_xyz/v3-core

v1.0.2

Published

Core smart contracts of Uniswap V3

Readme

Kumbaya Logo

Uniswap V3 - Kumbaya Edition

This repository contains the core smart contracts for the Uniswap V3 Protocol with a hint of Kumbaya.

Audit Status

This fork is based on the audited Uniswap V3 codebase. All core protocol logic remains unchanged and matches the original audited implementation. The only modification is the extended feeProtocol range described below.

Changes to Core Protocol

Protocol Fee Configuration

The protocol fee mechanism allows the factory owner to collect a portion of swap and flash loan fees from each pool.

How it works

  • feeProtocol is a denominator value that determines the protocol's share of fees
  • Protocol receives 1/feeProtocol of the total fees (e.g., feeProtocol=2 means 50%, feeProtocol=4 means 25%)
  • The remainder goes to liquidity providers

Valid values

| feeProtocol | Protocol Share | |-------------|----------------| | 0 | Disabled (0%) | | 2 | 50% | | 3 | 33.33% | | 4 | 25% | | 5 | 20% | | 6 | 16.67% | | 7 | 14.29% | | 8 | 12.5% | | 9 | 11.11% | | 10 | 10% |

Modification

The original Uniswap V3 implementation restricted feeProtocol to values 4-10 (max 25% protocol fee). This fork extends the range to 2-10, allowing up to 50% protocol fee collection.

File changed: contracts/UniswapV3Pool.sol (line 839)

- (feeProtocol0 == 0 || (feeProtocol0 >= 4 && feeProtocol0 <= 10))
+ (feeProtocol0 == 0 || (feeProtocol0 >= 2 && feeProtocol0 <= 10))

This is a single-line validation change. The underlying fee calculation math remains identical to the audited implementation.

Bytecode impact:

| Metric | Value | |--------|-------| | Deployed bytecode size | 22,142 bytes (unchanged) | | Bytes modified | 2 | | Byte positions | 8462, 8504 | | Change | 0x480x28 (PUSH1 4 → PUSH1 2) |

Pool Init Code Hash

The POOL_INIT_CODE_HASH is a keccak256 hash of the UniswapV3Pool contract's creation bytecode. It is used to deterministically compute pool addresses via CREATE2.

Kumbaya POOL_INIT_CODE_HASH:

0x851d77a45b8b9a205fb9f44cb829cceba85282714d2603d601840640628a3da7

This hash differs from the original Uniswap V3 hash (0xe34f199b19b2b4f47f68442619d555527d244f78a3297ea89325f843f87b8b54) due to the modified feeProtocol validation range.

Any contract that computes pool addresses (periphery contracts, indexers, frontends) must use this updated hash.