Event-triggered synths

A standard synthetic tracks a continuous series, a price, an index, a rate. An event-triggered synth is minted against a discrete event instead: a question with a date and a credible resolution source. When that event resolves, the synth's collateral mix shifts along a formula that was fixed when the synth was created.

Every event-triggered synth carries an event reference recorded at mint, which event, and which oracle feed resolves it. That reference can't be changed afterwards.

SymbolEventResolution sourceStatus
tFOMCFOMC target-rate decision, next meetingFederal Reserve (H.15)Spec
tOPECOPEC+ production quota change at next meetingOPEC Secretariat communiquéSpec
tCPIXU.S. CPI release surprise vs. consensusU.S. BLS & consensus printSpec
tDEBTU.S. debt ceiling raised before the Treasury X-dateU.S. TreasurySpec

These are specification examples, not live instruments. The rebalancing mechanic is scaffolded but not deployed. See Rebalance engine for the contract-level detail.

How a rebalance happens

  1. The referenced event resolves through the optimistic oracle.
  2. A keeper triggers the rebalance and posts a bond, the same way a liquidator does for an under-collateralised position.
  3. The engine reads the resolved outcome, looks up the pre-committed target mix for that outcome, and shifts the collateral basket toward it, within bounds set at creation.
  4. The keeper's bond is returned and a reward is paid from the synth's reward pool.

What's fixed upfront

Nothing about the rebalance is discretionary once the synth is live. Fixed at creation:

Bounded by design

A single rebalance can only move each collateral weight by a capped amount, and only toward a target committed before you took the position. Governance can't re-aim a rebalance after the fact.