TEMPER

GenLayer · Onchain Justice

The breach is settled.
The bill isn't.

TEMPER is a post-liability remedy protocol for bonded onchain service agreements. After a service failure, the provider claims when the agreed fallback became usable, the claimant responds, GenLayer adjudicates the mitigation dispute, and TEMPER settles what remains recoverable.

Create Agreement Explore Cases

Powered by GenLayer · Post-liability remedy adjudication

Three moves after liability

Three moves after liability.

01 · READ

Read the agreement + liability record

02 · PROVE

Prove when the fallback became usable

03 · SETTLE

GenLayer judgment → TEMPER remedy

Explore a live case

Core idea

A remedy after responsibility.

The original breach can be settled while the remedy is still disputed. A provider may be responsible for the original failure without being responsible for every loss that follows.

Upstream record
Liability statusEstablishedConfirmed loss8 GEN
✓Responsibility bound

01 · The record

Responsibility already established

Upstream liability and confirmed loss enter TEMPER.

Breach
4 GEN lost
Backup claimed available
8 GEN final loss

02 · The claim

The intervention point

The provider claims the agreed fallback became reasonably available after 4 GEN had already been lost. TEMPER asks whether the remaining loss could have been avoided.

Provider evidence
Claimant evidence
GenLayer
Verdict

03 · The evidence

What was actually possible?

Provider and claimant submit public evidence about whether the fallback could practically be used.

8 GEN confirmed lossBOND
4
4
RecoverableAvoidable
4 GEN4 GEN

04 · The remedy

What should still be paid?

GenLayer adjudicates the mitigation question; TEMPER converts the judgment into recoverable loss.

Mechanism · Onchain Justice

Onchain Justice should not stop at breach.

The remedy moves one state at a time. Smart contracts enforce objective rules, GenLayer adjudicates disputed facts from evidence, and TEMPER carries that process into the remedy.

01 · LIABILITY

Responsibility + confirmed loss arrive upstream.

02 · CLAIM

The provider identifies the intervention point.

03 · EVIDENCE

Both sides show what was practically possible.

04 · JUDGMENT

GenLayer adjudicates the mitigation dispute.

05 · SETTLEMENT

TEMPER applies the judgment to secured loss.

Technical positioning

Post-liabilityavoidable-lossadjudication

Responsibility is already established upstream. “Who is responsible?”

TEMPER handles the next question: “How much of the continuing loss should still remain recoverable?”

Upstream liability

Who is responsible?

→

Contract fact

Liability established

→

TEMPER

How much loss should remain recoverable?

Machine-native duty to mitigate

Smart contracts

Objective execution

GenLayer

Contextual adjudication

TEMPER

Remedy application

Current application

Primary service

Binance BTC/USD

Agreed fallback

Pyth BTC/USD

Coverage

10 GEN

Rule

Switch to Pyth if it is working and accessible to the other party.

Remedy, not just liability

Turn disputed mitigation into an enforceable remedy.

Create a bonded agreement, define the fallback obligation, and let GenLayer adjudicate the mitigation dispute when a failure occurs. TEMPER turns that judgment into an enforceable remedy.

Create Agreement Explore Cases

Evidence in · GenLayer verdict · Onchain settlement

Remedy path

Evidence

Two-sided inputs

GenLayer judgment

Mitigation question

↓

TEMPER remedy

Secured loss applied onchain