From 220efb89e59c781e84b0e5eec30ca642f4531619 Mon Sep 17 00:00:00 2001
From: Sara Reynolds <snreynolds2506@gmail.com>
Date: Thu, 20 Jun 2024 14:46:07 -0400
Subject: [PATCH] remove rand comments

---
 contracts/interfaces/INonfungiblePositionManager.sol | 3 ---
 contracts/types/LiquidityRange.sol                   | 7 +------
 2 files changed, 1 insertion(+), 9 deletions(-)

diff --git a/contracts/interfaces/INonfungiblePositionManager.sol b/contracts/interfaces/INonfungiblePositionManager.sol
index ee8b0c667..46bbfbd60 100644
--- a/contracts/interfaces/INonfungiblePositionManager.sol
+++ b/contracts/interfaces/INonfungiblePositionManager.sol
@@ -10,9 +10,6 @@ interface INonfungiblePositionManager {
         LiquidityRange range; // 576
     }
 
-    // using 736 - 3 SLOTS
-    // total 768 - 32 bits free space
-
     // NOTE: more gas efficient as LiquidityAmounts is used offchain
     function mint(
         LiquidityRange calldata position,
diff --git a/contracts/types/LiquidityRange.sol b/contracts/types/LiquidityRange.sol
index 363575d2b..4f6640279 100644
--- a/contracts/types/LiquidityRange.sol
+++ b/contracts/types/LiquidityRange.sol
@@ -4,16 +4,11 @@ pragma solidity ^0.8.24;
 import {PoolKey} from "@uniswap/v4-core/src/types/PoolKey.sol";
 
 struct LiquidityRange {
-    PoolKey poolKey; // 528
+    PoolKey poolKey;
     int24 tickLower;
     int24 tickUpper;
 }
 
-// can we force integrators to instead pass in the liquidity range? and we only store a hash?
-
-// 2 256 = 512
-// 576
-
 type LiquidityRangeId is bytes32;
 
 /// @notice Library for computing the ID of a liquidity range