Skip to main content
This flow describes private strategy evaluation, not the public HTTP-only beta simulation path.
Private strategy evaluation protects strategy logic during submission and evaluation. It does not make final public execution effects invisible.

​
Sequence

​
What is hidden

The protected surface is strategy input data during submission and evaluation: private parameter choices, strategy component composition, pre-selection candidate logic, and internal evaluation inputs that would leak builder edge.
Scores, benchmark diagnostics, eligibility status, report hashes, artifact references, and final execution effects if a later guarded deployment occurs.
Timing metadata, submitter or wallet metadata when revealed, market family, public catalog shape, final settlement effects, and behavior inferred from repeated public execution.

​
Trust assumptions

Confidential evaluation still depends on:
  • attested compute configuration,
  • operator configuration,
  • enclave implementation,
  • key and permission management,
  • side-channel assumptions,
  • governance over which artifacts and scores are published.
See Privacy Model for the full trust boundary.