fix: Hardcoded TWAP/cooldown values not documented (#825)
Document MIN_RECENTER_INTERVAL (60 s, LiquidityManager.sol:61) and PRICE_STABILITY_INTERVAL (300 s, PriceOracle.sol:14) in docs/ARCHITECTURE.md and docs/PRODUCT-TRUTH.md so that agent-facing and product-facing copy stays traceable to source constants. Add an inline HTML comment in red-team-program.md next to the hardcoded 60s/300s sentence pointing to the two source constants, making drift detectable during code review. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
baaca1c9b4
commit
0d09f598d9
3 changed files with 7 additions and 0 deletions
|
|
@ -84,6 +84,8 @@ The three-position structure creates **asymmetric slippage** — buys push the p
|
|||
- The optimizer adjusts position parameters based on sentiment
|
||||
- "Recenter" = atomic repositioning of all liquidity in one transaction
|
||||
- Anyone can trigger a recenter; the protocol bot does it automatically
|
||||
- Recenter has a **60-second cooldown** (`MIN_RECENTER_INTERVAL = 60` in `LiquidityManager.sol`) — successive recenters are rate-limited on-chain
|
||||
- Recenter requires **300 seconds of TWAP oracle history** (`PRICE_STABILITY_INTERVAL = 300` in `PriceOracle.sol`) and validates the current tick is within ±50 ticks of the 5-minute average before proceeding
|
||||
- The three positions together create asymmetric slippage — buys have more price impact upward than sells have downward
|
||||
- With normal trading activity, this structural asymmetry accumulates ETH, raising the floor over time
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue