LimitOrderHookV1

A liquidity manager hook. It manages its own liquidity.

• Manages its own liquidity

  It adds and removes liquidity itself, so it can own part or all of the pool.

  The code that does this (handlePlaceCallback):

  function _handlePlaceCallback(PlaceCallbackData memory placeData) internal virtual {
      OrderInfo storage orderInfo = _orderInfos[placeData.orderId];
      UserInfo storage userInfo = orderInfo.userInfo[placeData.owner];
      uint128 newUserLiquidity = userInfo.liquidity + placeData.liquidity;
  
      // add the out of range liquidity to the pool
      (BalanceDelta callerDelta, BalanceDelta feesAccrued) = poolManager.modifyLiquidity(
          placeData.key,
          ModifyLiquidityParams({
              tickLower: placeData.tickLower,
              tickUpper: placeData.tickLower + placeData.key.tickSpacing,
              liquidityDelta: int256(uint256(placeData.liquidity)),
              salt: _getPositionSalt(placeData.zeroForOne)
          }),
          ZERO_BYTES
      );
  
      // collect the fees the position accrued into the order, over the liquidity that earned them
      _collectFees(orderInfo, uint256(uint128(feesAccrued.amount0())), uint256(uint128(feesAccrued.amount1())));
  
      // checkpoint the placer against the order's accumulators, over the liquidity they end up holding
      (uint256 owed0, uint256 owed1) = _feesOwed(orderInfo, userInfo);
      userInfo.feeCheckpoint0X128 = _feeCheckpoint(orderInfo.accFee0PerLiqX128, owed0, newUserLiquidity);
      userInfo.feeCheckpoint1X128 = _feeCheckpoint(orderInfo.accFee1PerLiqX128, owed1, newUserLiquidity);
  
      // update the order liquidity accounting
      unchecked {
          orderInfo.liquidityTotal += placeData.liquidity;
          userInfo.liquidity = newUserLiquidity;
      }
      // …

Who controls it: It has an admin address, but no admin-only settings in its own code. The code cannot be changed.

Based on the hook’s published code.