What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The negative-only behavior comes from an extra adjustment in the tick-compression helper shown in Uniswap’s v4 SDK guide. JavaScript’s Math.floor already rounds a negative quotient down; subtracting one more shifts the compressed tick again. The documented behavior concerns indexing helper and periphery code. The reviewed evidence does not establish a core-swap exploit or whether a later release changed the affected code.
Why negative ticks expose the issue
Uniswap ticks mark boundaries in price space. Each tick represents a 0.01% price change, and crossing an active tick can change which liquidity is active. A pool’s tick spacing restricts which ticks can be initialized: for spacing 3, the eligible sequence includes … -6, -3, 0, 3, 6 …. The SDK maps ticks into a bitmap by compressing them according to spacing and then locating the compressed index’s word and bit. Uniswap’s tick overview and v4 SDK quoting guide describe these concepts.
As an Amazon Associate I earn from qualifying purchases.
The guide’s displayed helper computes a compressed value with Math.floor(tick / tickSpacing), then subtracts one when the tick is negative and not evenly divisible by spacing:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →function tickToWord(tick: number): number {
let compressed = Math.floor(tick / tickSpacing)
if (tick < 0 && tick % tickSpacing !== 0) {
compressed -= 1
}
return compressed >> 8
}For tick -1 and spacing 10, the quotient is -0.1. JavaScript’s Math.floor(-0.1) is -1, so the additional decrement produces -2. The extra adjustment is redundant if the intention is simply to round down: floor already rounds toward negative infinity. The comparable positive quotient, such as 0.1, floors to 0 without needing a correction.
#1 Best Overall
This distinction matters because integer division in different languages or expressions may truncate toward zero instead of rounding down. Negative non-multiples are where those behaviors diverge. But in the displayed JavaScript expression, applying floor and then decrementing again moves the index one position farther than floor alone.
What tick compression and bitmap lookup do
Compression translates a tick into an index relative to the pool’s spacing. That index is then used to identify a bitmap word and a bit within it. Uniswap’s SDK documentation describes each bitmap word as covering 256 initializable tick positions; the v4 core source provides the spacing-based tick sequence and traversal context. See the v4 core TickBitmap library.
Rank #2
The distinction between a compressed tick and its bitmap coordinates is important: the helper shown in the guide returns a word derived from the compressed value, while a position calculation also needs the appropriate bit offset. The audit excerpt’s replacement snippet should not be copied as a verified fix: it displays a return based on tick >> 8, which does not use the compressed value and does not match the surrounding description. The sound principle is to avoid applying a second floor adjustment after Math.floor; that observation alone is not a complete, verified replacement implementation.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What the draft periphery review establishes
A draft Spearbit review of periphery code discusses a related negative-tick issue. In its PoolTicksCounter change, calculations for tickBefore and tickAfter move from direct signed division and modulo operations to compress(key.tickSpacing).position(). The excerpt also says a related issue is present in v3-periphery and points to the SDK documentation. The draft review records Uniswap’s response that the Quoter-related issue would not be fixed in that revision because, as the response put it, “For various reasons we are now going to be re-architecting our Quoter contract.”
That response is historical and appears in a draft review. It does not establish whether a later Quoter release corrected the behavior. Nor does the helper and periphery discussion, by itself, show that core pool swaps are affected. The current v4 core source routes swap traversal through nextInitializedTickWithinOneWord using the current tick and tick spacing; this implementation context is not proof that the reported helper issue changes core swap execution. The v4 core source and TickMath state supported tick bounds of -887272 to 887272 and a minimum spacing of 1.
Quick Recap
How to read the issue accurately
- It is not every negative tick. The extra decrement in the displayed helper is conditional on a negative tick that is not divisible by spacing.
- It is an indexing concern. The relevant mechanism is converting ticks to compressed indices and bitmap positions, not a demonstrated loss-of-funds scenario.
- The evidence is about documentation and periphery. The cited review and SDK guide do not establish a current core protocol vulnerability or current remediation status.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
