temporal-parameter-staleness

To detect stale parameters in multi-step Sui operations, identify functions that cache parameters at initiation and assess whether admin changes between steps invalidate those cached values before execution completes.

Clock timestamps (clock::timestamp_ms) and epoch counters (tx_context::epoch) influence cached parameter validity by tracking time progression across Sui transaction steps, which helps determine if cached values have expired or become stale.

Parameter staleness in Sui multi-step transactions occurs when an operation caches a parameter at Step 1, but an admin change alters that parameter before Step N executes, causing the operation to use outdated values.

Analyzing PTB bypass risks involves examining whether Sui Programmable Transaction Blocks can circumvent multi-step parameter caching safeguards, allowing operations to execute with stale or manipulated parameter values across steps.

Mitigating retroactive effects requires documenting staleness scenarios where admin changes impact in-flight operations and implementing safeguards that validate cached parameters against current values before each subsequent step executes.