Security reviews

Starknet Wallet follows a defined security review process built around local-first key control, transparent transaction review, responsible disclosure, and verification-first installation.

Security review process

• Code review. Application architecture, dependencies, signing flows, and account-permission surfaces are reviewed as part of the maintained security process.
• Build verification. Official public builds are paired with checksum and signature guidance before installation.
• Transaction clarity. Signing screens are designed to show network, calldata, fee, and permission context before approval.
• Responsible disclosure. Security reports should be handled privately so issues can be reviewed and resolved safely.
• Review history. Findings and remediation records are documented through the maintained release and disclosure process.

How to verify official builds

• Download only from the official project source.
• Compare the published SHA256 checksum before installation.
• Verify the PGP signature supplied with the official build.
• If building from source, compare your local hash with the official verification material.

See Security for the security and verification model, or Desktop platforms for platform and release details.