Skip to main content
AlphaEngine privacy is strongest during submission and evaluation. It should be described as private decisioning and private evaluation for public markets, not as hidden public market execution.

​
Required statement

AlphaEngine keeps strategy inputs confidential during submission and evaluation, while scores, evidence artifacts, eligibility status, and final effects can become public.

​
Privacy map

Private strategy parameters, protected component choices, pre-selection strategy logic, and private allocation or policy inputs when supported by the confidential path.
Public observers, competing builders, unauthorized operators, and anyone outside the configured evaluation boundary.
Submission, decoding and validation, simulation, scoring, and selection or eligibility review.
Scores, benchmark diagnostics, eligibility status, report hashes, artifact references, final execution effects, and market-level behavior after deployment.
Timing, metadata, supported market family, wallet or submitter information if revealed, final settlement effects, and behavior inferred from repeated public execution.
Attested compute implementation, operator configuration, permission and key management, side-channel assumptions, artifact publication policy, and governance over upgrades and supported families.

Confidential compute

Architecture-level compute boundary.

Trust and confidential compute

Operational assumptions and limits.

Public settlement

What becomes observable when effects settle.