@kumbaya_xyz/v3-core
v1.0.2
Published
Core smart contracts of Uniswap V3
Readme

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
feeProtocolis a denominator value that determines the protocol's share of fees- Protocol receives
1/feeProtocolof 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 | 0x48 → 0x28 (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:
0x851d77a45b8b9a205fb9f44cb829cceba85282714d2603d601840640628a3da7This 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.
