> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lunya.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Events & Indexing

> What is byte-identical to Uniswap V3, what is new, and the handlers to change

## The six that carry your V3 subgraph

Byte-identical to Uniswap V3, emitted by every pool type:

```solidity theme={null}
event Initialize(uint160 sqrtPriceX96, int24 tick);
event Mint(address sender, address indexed owner, int24 indexed tickLower, int24 indexed tickUpper,
           uint128 amount, uint256 amount0, uint256 amount1);
event Burn(address indexed owner, int24 indexed tickLower, int24 indexed tickUpper,
           uint128 amount, uint256 amount0, uint256 amount1);
event Collect(address indexed owner, address recipient, int24 indexed tickLower, int24 indexed tickUpper,
              uint128 amount0, uint128 amount1);
event Swap(address indexed sender, address indexed recipient, int256 amount0, int256 amount1,
           uint160 sqrtPriceX96, uint128 liquidity, int24 tick);
event Flash(address indexed sender, address indexed recipient, uint256 amount0, uint256 amount1,
            uint256 paid0, uint256 paid1);
```

STABLE pools emit the same shapes: ranges as `MIN_TICK/MAX_TICK`, and the `Swap` tick **derived from the price** — in tick space, zero means exactly 1:1, so emitting a literal zero would report a wrong price on every stable swap.

## The one changed handler

```solidity theme={null}
event SetFeeProtocol(uint16 feeProtocol0Old, uint16 feeProtocol1Old,
                     uint16 feeProtocol0New, uint16 feeProtocol1New);
```

V3's four fields are `uint8` (a four-bit denominator); these are shares out of ten thousand. **A subgraph indexing this event needs its handler changed.** Everything else on the pool that V3 has is untouched.

## New pool events (no V3 counterpart)

```solidity theme={null}
event FeeChanged(uint24 newFee);                        // governance or dynamic-fee plugin moved the fee
event TickSpacingChanged(int24 newTickSpacing);         // CL only
event PluginChanged(address newPlugin);
event PluginConfigChanged(uint16 newConfig);
event CollectProtocol(address indexed sender, address indexed recipient, uint128 amount0, uint128 amount1);
```

STABLE adds `AmplificationChanged(uint32 old, uint32 new)` and `AmplificationRampStarted(uint32 start, uint32 target, uint32 endTime)`.

There is **no `IncreaseObservationCardinalityNext` on the pool** — the TWAP is a plugin, and that event lives on the oracle module.

## Factory

```solidity theme={null}
event PoolCreated(
    address indexed token0,
    address indexed token1,
    PoolType indexed poolType,   // uint8 in topic3 — NOT V3's uint24 fee
    int24 tickSpacing,
    uint24 fee,
    address pool
);
event PoolDefaultsChanged(PoolType indexed poolType, int24 tickSpacing, uint24 fee);
event PoolCreationRestrictedChanged(PoolType indexed poolType, bool restricted);
```

`PoolCreated` is **not** V3's signature — pool discovery handlers need the new shape. This is the stream that catches launchpad graduations too: the launchpad's own `Graduated` event names the pool, but the pool's birth logs here.

## Position manager

The V3 trio is signature-identical, down to the indexing:

```solidity theme={null}
event IncreaseLiquidity(uint256 indexed tokenId, uint128 liquidity, uint256 amount0, uint256 amount1);
event DecreaseLiquidity(uint256 indexed tokenId, uint128 liquidity, uint256 amount0, uint256 amount1);
event Collect(uint256 indexed tokenId, address recipient, uint256 amount0, uint256 amount1);
```

One addition that **will silently corrupt a V3-shaped position tracker** if unhandled:

```solidity theme={null}
event Repositioned(
    uint256 indexed tokenId, int24 tickLower, int24 tickUpper, uint128 liquidity, uint256 amount0, uint256 amount1
);
```

A position can move to a new range **keeping its token id** — no `DecreaseLiquidity` + `Collect` + `IncreaseLiquidity` sequence describes it on the manager. Without a handler, a repositioned NFT appears to sit at its old ticks forever. (The pool underneath still emits its own `Burn`/`Collect`/`Mint`, and optionally a `Swap`, in the same transaction.)

## Plugin modules (index if you track these features)

* **Limit orders**: `OrderPlaced(owner, fillTick, sellingToken0, liquidity)`, `OrderCancelled(...)`, `OrdersFilled(fillTick, sellingToken0, epoch, amount0, amount1)`, `OrderClaimed(...)`, and `SettlementIncomplete(settledThrough, target)` — a swap can cross more ticks than one transaction settles; unsettled orders still rest and still fill later.
* **Oracle**: `IncreaseObservationCardinalityNext(old, new)` on the oracle module.
* **Dynamic fees**: `FeeCurveChanged(baseFee, maxFee, sensitivity, twapPeriod)`; the pool's own `FeeChanged` fires as the fee moves.
* **Security**: `StatusChanged(previous, current)`.
* **Farming**: `IncentiveCreated(virtualPool, pool, rewardTokens)`, `Entered/Exited(virtualPool, tokenId, ...)`, `RewardAdded`, `RateChanged`.
* **Vaults**: `VaultCreated(vault, pool, owner, tickLower, tickUpper)` on the vault factory; `Deposited/Withdrawn/Rebalanced`, `PositionOpened(tokenId)`, and the reward ledger events (`Harvested`, `RewardClaimed`) on each vault.

## Indexer rules of thumb

1. Start from the [deployment's start blocks](/developers/contracts); discover pools from `PoolCreated`, positions from the manager, launches from the [launchpad factory](/developers/launchpad/events).
2. `feeGrowthGlobal*X128` may overflow `uint256` **by design** — index it as a wrapping counter, not a monotone value.
3. The emitted position range is always the pool-resolved one, so CP/STABLE logs never carry a caller's fictional range.
4. Protocol-fee accounting: `SetFeeProtocol` (changed shape) + `CollectProtocol`.