Trust you can check.
We’d rather give you evidence than assurances. Here’s what has been independently reviewed and where that review stops, what we commit to by design, and how to tell us when something’s wrong.
Pick the proof you need.
Security reviewers, integrators and buyers ask different questions. Each route answers one.
Audit & scope
What Nethermind reviewed, where the review stops, and the report itself.
Read → Release integrityDeployment verification
How the official CreateX catalog was checked across 15 listed networks against the published release — and what that check does not cover.
Read → How checks workBefore settlement
What the account can require before an operation runs — roles, waits, and targets. Depth lives under Technology.
Technology →What we commit to.
Properties of how the technology is built — not certifications. Particle CS holds none. For the mechanisms behind these commitments, see Technology.
You hold your keys
Particle CS doesn’t custody assets or key material for your account.
Nothing until it’s granted
Roles, operations and targets that weren’t permitted are refused — an allowlist the contract enforces.
Rules outlive our software
Policy is enforced by the account, not our application. Another client can’t skip it.
Separation of duties
Sensitive operations can require more than one party — over time, or across roles.
Evidence stays with the operation
Who proposed, approved or cancelled, and what ran, is part of chain history — not a chat log.
Open to inspection
The Protocol’s contracts, tests and audit report are public.
Found a vulnerability? Tell us privately.
Please don’t open a public GitHub issue. Email us with a description, steps to reproduce and the potential impact — we’d rather hear about it before anyone else does.
Running a security review?
Architecture reviews and vendor questionnaires included — we’d rather answer before a contract than after.