Question 1

What does Singularity Shield audit?

Accepted Answer

Singularity Shield audits smart contract code for canisters on the Internet Computer (ICP), written in Motoko or Rust. It looks for rug-pull patterns, upgrade and controller risks, reentrancy across inter-canister calls, state inconsistencies, crypto misuse and quantum-vulnerable cryptography (ECDSA, ECDH, RSA) with NIST post-quantum migration paths.

Question 2

How is it different from a normal LLM code review?

Accepted Answer

Fifteen deterministic detectors parse the code and give the same answer for the same input every time. Four language-model reviewers, a consensus layer and a meta-review run on top, and a finding that the three disagree on is dropped rather than reported.

Question 3

Where does Singularity Shield run?

Accepted Answer

The frontend, the report store, the badge registry and governance are canisters on ICP mainnet. The analysis itself runs off chain in one orchestrator, because a language model answers every replica differently and an HTTPS outcall needs identical responses to pass consensus. Every secret stays there rather than in replicated canister state.