Security tooling has to earn trust before it earns a workflow, so the platform is built around isolation, explicit access, and evidence that can be re-run.
Four commitments that hold today. Everything else on this page is marked as work still to be documented.
Your contracts, sessions, forks, and findings are visible only to your workspace. Access is explicit and controlled, never implicit.
Analysis and proof-of-concept testing run only against isolated forks of chain state. Nothing the platform runs touches a live network or real funds.
A finding reaches your report only if it reproduces deterministically on the pinned fork. Evidence is tied to execution rather than to an assertion.
We publish a security contact and a disclosure process, and we support coordinated disclosure of issues found in our own site and tooling.
Send reports to security@trilocore.com. The machine-readable contact record and policy live at /.well-known/security.txt.
The headings below are what this page will document as the work is completed and verifiable. None of them is published yet, and no certification or control is claimed here before it is finished.
Open a fork, reproduce a finding, and read the trace that produced it.