[study] (2h) shouldRebalance semantics — tick-drift, time threshold, 24h fallback

[ozpool]

Goal

Understand when PRISM rebalances and who triggers it.

Time estimate

2h (single focused session)

Prerequisites

• [study] (2h) IStrategy purity contract — no state reads, weight-sum exactness #107 (P8) — IStrategy purity contract — no state reads, weight-sum exactness

Study plan (in order)

1. [25 min] PRISM_PRD_v1.0.html §Day 3 BellStrategy.shouldRebalance
2. [25 min] Triggers: tick drift > X ticks OR time elapsed > Y AND real work to do
3. [25 min] 24h fallback: block.timestamp - lastTs > 24h short-circuit → anyone can rebalance
4. [25 min] Keeper economics: bonus covers gas; competition for bonus = gas war risk
5. [20 min] On-chain signals of keeper misbehavior: long time since rebalance, tick drift beyond threshold, vault share-price stagnation

Total: 120 min

After studying, you can

• Describe tick-drift + time threshold triggers
• Explain the 24h liveness fallback
• Articulate what prevents keeper gas wars
• Sketch detection of keeper misbehavior on-chain

Tradeoff prompt for the architectural review

How would you detect keeper misbehavior from on-chain signals?

References

• PRISM_PRD_v1.0.html §Day 3, §13 Keeper liveness