Skip to content

Module Compositions

Chronomancy modules are designed to be independent but composable. Certain combinations produce emergent behaviors — financial structures or user experiences that neither module achieves alone.


Modules: SLOW (deadline extension) + REWIND (position insurance)

Emergent behavior: A user activates SLOW to extend a market, then uses the extension window to assess whether to activate REWIND on their position before resolution.

sequenceDiagram
participant User
participant Market
participant RewindPool
User->>Market: Burns $TM to extend resolution +24h
User->>RewindPool: Buys Rewind policy during extension
Market->>Market: Resolves (against user)
User->>RewindPool: Claims 70% payout within 24h window

Use case: A market is about to resolve on news that just broke. The user is uncertain — SLOW buys time to evaluate. If their position looks weak, they activate REWIND before deadline passes. The two-step creates a structured negotiation with uncertainty.


Freeze + Fork: Contested Resolution Branch

Section titled “Freeze + Fork: Contested Resolution Branch”

Modules: FREEZE (trading halt) + FORK (conditional market split)

Emergent behavior: When a market’s integrity is in question, FREEZE pauses it. During the halt, a FORK creates two competing resolution branches — allowing the community to price in both “legitimate resolution” and “disputed resolution” outcomes simultaneously.

sequenceDiagram
participant Community
participant Market
participant ForkBranch
Community->>Market: Stakes $TM → FREEZE triggered (30 min halt)
Community->>ForkBranch: Burns $TM → Creates "disputed" + "undisputed" branches
Market->>ForkBranch: Resolves based on which branch community selects

Use case: A prediction market on a political outcome faces a disputed result. FREEZE prevents panic trading. FORK creates a market on the dispute itself — the community prices the probability of contested vs. accepted resolution.


Modules: FAST-FORWARD (early exit) + LOOP (seasonal epoch)

Emergent behavior: Users who want to lock in profits before season end use FF to cash out early. They redeploy capital into fresh Season markets — capturing high early-season liquidity while locking in their CS outcome before Glicko-2 seasonal reset.

sequenceDiagram
participant User
participant FFVault
participant NewSeason
User->>FFVault: Fast-Forwards winning position
FFVault->>User: USDC payout (above market price)
Note over User: Season ends, Glicko-2 RD resets
User->>NewSeason: Re-enters with capital + persistent CS

Use case: End of Q4 season. A user with a high-CS position at 75c (market says 65c) exits via FF. They receive 72c immediately, lock in their CS improvement from the winning trade, and enter the new season with USDC ready to deploy.


Precognition → Rewind: The Full Safety Net

Section titled “Precognition → Rewind: The Full Safety Net”

Modules: PRECOGNITION (paper trading onboarding) + REWIND (position insurance)

Emergent behavior: A new forecaster completes Precognition to qualify for CS access. Their first real-money trades are protected by Rewind. If they lose, they recover 70%. The combination turns the intimidating first real-money step into a capped-loss trial run.

sequenceDiagram
participant NewUser
participant Precognition
participant RealMarket
participant RewindPool
NewUser->>Precognition: 30 paper predictions (qualification grind)
Precognition->>NewUser: CS Basic tier unlocked
NewUser->>RealMarket: First real-money prediction
NewUser->>RewindPool: Buys Rewind on first position
RealMarket->>RealMarket: Market resolves (loss)
NewUser->>RewindPool: Claims 70% — re-enters market

Use case: The entire onboarding funnel. Precognition lowers the barrier to entry; Rewind lowers the cost of being wrong early. Together they convert new users into active participants before they’ve proven skill.


One composition that is intentionally blocked: activating both FAST-FORWARD and REWIND on the same position simultaneously.

  • FF transfers the economic risk to the vault — the user no longer holds the position
  • Rewind insures a position the user holds — once transferred, there’s nothing to insure

The protocol enforces this at the contract level: FF transfer voids any existing Rewind policy on the same position (premium is refunded pro-rata for unused coverage time).

Related: