ScoutraBeta

AgentsPreview

Limit changesPlanned contract design
How limit changes would apply in the planned mandate contract
ActionAppliesWhy
Raise a limitWaits 1 hourGives you time to react if someone else gets your key.
Lower a limitAt onceMaking limits stricter should never wait.
Freeze the agentAt onceOnly the owner can do it. Trading would stop in that block.
Send funds outNeverFunds could only go back to the owner's account.

A per-trade cap in actiondemo

no contract deployed
cap 0.2
0.1
0.3
  • Example bond (not real)1 USDG
  • Trade of 0.1 USDG, inside the cappasses
  • Trade of 0.3 USDG, over the capblocked · Size
  • 10% of the example bond would go to the owner0.9 USDG left

Amounts are USDG per trade. The verdicts come from the rule engine behind Break it. No transaction was sent and no mandate contract exists yet.

Limit change timeline1 hour delay · planned

60 min left · 0 min

Cap the agent could use

1,000 USDG

The old cap still applies

Change type

Raise

Waits 1 hour

The 1 hour delay is part of the planned design. No contract enforces it yet.

Risks on this page

What this tool can miss, and what it can't protect you from.

  1. 01Nothing here is enforced on chain yet. The rules run in our code, and no mandate contract or bond exists.
  2. 02Any trading strategy can lose everything it is given. Limits make losses smaller, not impossible.
  3. 03The decision log on these pages is example data. A real log would show what happened, not whether it was a good call.