Check a strategy
fixture-tampered-rules
Sample data. Not a real strategy, and nothing here is read from a chain.
Result
Not matching
The strategy's status
MatchingThe strategy is closed and settled.
Rules match the commitment
Not matchingThe revealed rules do not match the commitment.
Action 1: Open, ok
UnverifiableCan't check: the rules were not revealed.
Action 2: ClosePosition, ok
UnverifiableCan't check: the rules were not revealed.
No close missed at the sampled blocks
UnverifiableCan't check: the rules were not revealed, or do not match the commitment.
No change to the account's keys or code at the sampled blocks
MatchingNo change to the account's keys or code at the sampled blocks.
The code hash equals the pinned hash
MatchingThe deployed code hash equals the pinned hash.
The strategy uses the pinned counterparties
MatchingThe DCL contract, quote token and pool equal the pinned constants.
Not checked in this version
- Valuation: stop loss and take profit use the pool's spot point at each sampled block (Q15). The page cannot check that this price was fair; a price moved across the whole confirmation span would pass.
- That the deployed code is a reproducible build of the audited commit (only a pinned hash is compared, when one is published).
- That the account was created in the single creating transaction, and that principal equals the sum of the funding events.
- That the split of fees followed the stated percentage.
- Refusals by public limits are shown as context. They are not yet recomputed from the record, so they are never counted as an excuse.
- Only the sampled blocks are compared: a key added and removed between two samples, or a close condition that comes and goes between them, is not seen.
- The decision log chain, unless the agent records chain heads (a run without them has no chain to check).
- That the creation block and the agent's history are as recorded; the recorded runs supply a stand-in creation block.