Skip to content

Commit 8650da8

Browse files
codybornclaude
andcommitted
style: strip point-in-time ticket / rollout references from comments
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 28fae3f commit 8650da8

2 files changed

Lines changed: 8 additions & 12 deletions

File tree

lib/handlers/constants.ts

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,12 @@ export const DEFAULT_MAX_OPEN_ORDERS = 5
1515
export const DEFAULT_MAX_OPEN_LIMIT_ORDERS = 100
1616
export const HIGH_MAX_OPEN_ORDERS = 200
1717

18-
// V3-rollout chains (BNB/Monad/XLayer/Worldchain/Soneium/Celo/Avalanche/Blast/Zora)
19-
// register Dutch_V3 only — they have no priority/hybrid reactor in
20-
// @uniswap/uniswapx-sdk's REACTOR_ADDRESS_MAPPING, so
21-
// OffChainUniswapXOrderValidator.validateReactorAddress rejects priority/hybrid
22-
// orders for those chainIds before these buffers are consulted. The sentinel-0
23-
// entries exist only to satisfy Record<ChainId, number> typing and are
24-
// unreachable in practice. Tempo follows the same pattern (see ECO-365 phase 1b).
18+
// Chains that register Dutch_V3 only (no priority/hybrid reactor in
19+
// @uniswap/uniswapx-sdk's REACTOR_ADDRESS_MAPPING) get sentinel-0 entries
20+
// here to satisfy Record<ChainId, number> typing.
21+
// OffChainUniswapXOrderValidator.validateReactorAddress rejects
22+
// priority/hybrid orders for those chainIds before these buffers are
23+
// consulted, so the values are unreachable in practice.
2524
export const PRIORITY_ORDER_TARGET_BLOCK_BUFFER: Record<ChainId, number> = {
2625
[ChainId.MAINNET]: 3,
2726
[ChainId.UNICHAIN]: 4,

lib/util/constants.ts

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,8 @@ export const ONE_HOUR_IN_SECONDS = 60 * 60
1111
export const ONE_DAY_IN_SECONDS = 60 * 60 * 24
1212
export const ONE_YEAR_IN_SECONDS = 60 * 60 * 24 * 365
1313
// Per-chain "oldest block worth scanning" used by the GS reaper to floor its
14-
// 1-week lookback window. Pre-existing entries (Mainnet/Arbitrum/Base/Unichain/
15-
// Tempo) are unchanged. New entries for the V3 multi-chain rollout are seeded
16-
// just below each chain's V3DutchOrderReactor deploy block (see x-contracts
17-
// deployments.md / broadcast/DeployDutchV3.s.sol/<chainId>/run-latest.json),
18-
// which is the earliest block any V3 fill could possibly appear on.
14+
// 1-week lookback window. Values are seeded just below each chain's earliest
15+
// reactor deploy block — the earliest block any UniswapX fill could appear on.
1916
export const OLDEST_BLOCK_BY_CHAIN = {
2017
[ChainId.MAINNET]: 20120259,
2118
[ChainId.OPTIMISM]: 151283000,

0 commit comments

Comments
 (0)