Uniswap V4 Hooks

LFG.RICH is built around a Uniswap V4 Hook architecture. The Hook is not just a helper contract. It is the protocol component that enforces the bonding curve, floor-price accounting, fee routing, referral-aware fee splits, and collateral borrowing rules for official LFG.RICH tokens. The user-facing swap flow is intentionally simple, but the on-chain route is precise:

Factory

Creates official LFG.RICH tokens and registers them with the Hook.

Uniswap V4 Hook

Enforces pricing, floors, reserves, fees, collateral, borrowing, and hook callbacks.

Swap Router

Gives users and integrations simple buy and sell entry points.

Pool Manager

Executes the Uniswap V4 unlock, swap, settlement, and callback flow used by the Hook and Router.

User wallet
  -> Swap Router
  -> Pool Manager unlock(...)
  -> Pool Manager swap(...)
  -> Uniswap V4 Hook beforeSwap(...)
  -> custom curve, floor, fee, and accounting logic
  -> Pool Manager settlement / take

Main contracts

Contract	Responsibility
Factory	Creates official LFG.RICH tokens and registers them with the hook.
Uniswap V4 Hook	Handles pricing, floors, reserves, fees, collateral, borrowing, and hook callbacks.
Swap Router	Provides simple buy and sell functions for users and integrations.
Token	ERC20-compatible token contract created by the Factory.
Pool Manager	Uniswap V4 Pool Manager used by the hook and router flow.

BSC V5 addresses

Contract	Address
Factory	`0x429a7ef0129649a97bb3f1e961dd56d9bd4ac01f`
Uniswap V4 Hook	`0xc18e6e1926113cdcf53f3ec1a89d3eb84cc6a888`
Swap Router	`0x4018abd5d24ee48c642e7e518a8aef03b59ec150`
Token	Created per launch by the Factory.
Pool Manager	`0x28e2Ea090877bF75740558f6BFB36A5ffeE9e9dF`

PoolKey and poolId

Each official token has its own Uniswap V4 PoolKey and its own poolId.

struct PoolKey {
    address currency0;   // native BNB represented as address(0)
    address currency1;   // token address
    uint24 fee;          // 3000
    int24 tickSpacing;   // 60
    address hooks;       // Uniswap V4 Hook
}

For integrations, the important rule is: do not guess the pool. Resolve the poolId and PoolKey for the token you are interacting with.

poolId = token.pool_id || token.poolId || hook.tokenToPoolId(tokenAddress)
key    = factory.getPoolKey(tokenAddress)

The site code always treats the token’s poolId as part of the interaction context. Estimates use poolId; swaps use PoolKey.

Why the Hook matters

The Hook prevents the token from behaving like a normal unmanaged LP token. Creators do not receive LP tokens to remove. Traders do not interact with arbitrary third-party pools. Official trades are routed through the protocol contracts, where the Hook enforces the same pricing, floor, fee, referral, and collateral rules for everyone. This gives the protocol a consistent execution path:

buys and sells use the official Swap Router;
pricing is calculated by the Hook;
token mints and burns are controlled by the Hook;
collateral lending uses the same poolId-based state;
floor updates are tied to the token’s own protocol state;
referral rewards are decided by on-chain invite bindings.

Important integration rule

Older V3 examples are not safe for V5 integrations. V5 estimates include the user address, token creation uses devBuyEth, and buys/sells must be routed with the token’s correct PoolKey.

Use this V5 pattern:

Load token data

Start from API token data or a known token address.

Resolve poolId

Use token.pool_id, token.poolId, or hook.tokenToPoolId(tokenAddress).

Resolve PoolKey

Use factory.getPoolKey(tokenAddress) or build from verified V5 constants.

Estimate with Hook + poolId + user address

V5 estimate functions include the wallet address because referral state can change fee recipients.

Execute buy/sell with Swap Router + PoolKey

Swap execution uses the token-specific PoolKey.

Execute lending with Hook + poolId

Borrow, borrowMore, repay, and state reads use the Hook and poolId.

Overview

Protocol

Getting Started

Developers

Resources

Factory

Uniswap V4 Hook

Swap Router

Pool Manager

Main contracts

BSC V5 addresses

PoolKey and poolId

Why the Hook matters

Important integration rule

Factory

Uniswap V4 Hook

Swap Router

Pool Manager

​Main contracts

​BSC V5 addresses

​PoolKey and poolId

​Why the Hook matters

​Important integration rule

Main contracts

BSC V5 addresses

PoolKey and poolId

Why the Hook matters

Important integration rule