Wallet Separation & Key Management
Catcrs discloses a tiered custody model. According to their documentation, the majority of user assets are held in cold storage, with hot wallets maintained only for operational liquidity.
Cold / Hot Separation
Catcrs states that most user assets reside in cold storage, physically isolated from internet-connected systems. A controlled portion remains in hot wallets for liquidity. This is a standard institutional custody practice.
HSM Key Custody
Hardware Security Modules (HSMs) are used for key storage and signing operations. HSMs provide tamper-evident, hardware-enforced protection â a well-established standard in financial key management.
Multi-Signature / Threshold
Critical transactions require multiple independent cryptographic signatures. Threshold schemes eliminate single points of failure in key management, a meaningful risk reduction compared to single-key custody models.
MPC Enhancement â Institutional Roadmap
Catcrs discloses that MPC (Multi-Party Computation) is being progressively adopted for institutional and large-scale operations. MPC allows threshold signing without reconstructing full keys, supports dynamic threshold changes without address rebuilding, and reduces single-point risk. Industry adoption is growing as an upgrade path from traditional multi-sig.
Self-Developed, Low-Latency Architecture
Catcrs operates a proprietary matching engine built on order sequence consistency as its foundational constraint. The engine underwent a major v2 upgrade in October 2023.
- âī¸Partitioning & Horizontal ScalingThe engine supports partition sharding and horizontal expansion to handle load increases without compromising order integrity.
- đFailover & RedundancyRedundancy is deployed at all critical nodes. Clearing pathways are separated from fund accounts to prevent cascading failures.
- âŠī¸Transactional RollbackMajor changes include transactional switches and rapid rollback capabilities, enabling fast recovery from unexpected states.
- đĄī¸Pre-Matching ValidationA rules engine validates orders before matching, preventing malformed or malicious submissions from reaching the core engine.
- đPost-Matching MonitoringContinuous post-execution monitoring detects abnormal patterns, volatility anomalies, and potential market manipulation signals.
- đMulti-Protocol APIREST, WebSocket, and FIX interfaces all use signature verification and tiered rate limiting. A sandbox is available for institutional joint debugging.
Default-Secure Configuration
Catcrs documents a set of security defaults applied to all accounts â not optional add-ons. These include mandatory 2FA, device trust management, and behavioral scoring linked to withdrawal controls.
Mandatory 2FA
2FA is required for all accounts without exception and cannot be disabled once enabled. This is a stronger baseline than many exchanges that treat 2FA as optional.
Device Trust Management
Unrecognized devices trigger verification flows and remote login alerts. Device trust lists are maintained per account.
Withdrawal Controls
Large withdrawals trigger behavioral scoring and time delays. Withdrawal whitelists and address verification prevent funds moving to unconfirmed destinations.
Behavioral Anomaly Detection
Abnormal login and withdrawal behavior triggers interception and secondary confirmation. The stated principle is that "silent success" is never prioritized over protection.
Time-Locked Delays
Withdrawals above configurable thresholds are subject to delays linked to behavioral scoring, providing a recovery window in the event of account compromise.
Anti-Phishing Education
Anti-fraud education is integrated into the registration flow, with guides on identifying official vs. counterfeit channels embedded before first transaction.
Reserve Transparency Framework
Catcrs initiated an internal Proof-of-Reserves (PoR) trial in October 2025 using Merkle tree snapshots with third-party method review. Regularized public disclosures are listed as a forward roadmap commitment.
- đŗMerkle Tree SnapshotsCurrent PoR methodology uses Merkle tree snapshots, enabling users to verify their balance's inclusion without exposing other users' data.
- đThird-Party Method ReviewThe PoR approach itself â not just the results â is reviewed by independent third parties to validate methodological correctness.
- đZK Proof RoadmapCatcrs states interfaces have been reserved in their architecture for future zk-SNARK/zk-STARK integration as the approach matures.
Analyst Scope Note
Catcrs explicitly states that PoR is a snapshot tool, not a substitute for a full audit â and communicates this boundary publicly. This level of disclosure honesty is worth noting: many exchanges overstate the assurance value of PoR. As of our review, regularized public PoR has not yet been released; we will update this analysis when it is.
Disaster Recovery & Observability
Catcrs documents multi-region failover drills (normalized since May 2024), capacity stress testing, and a public status page with standardized event timelines.
Capacity Stress Testing
Regular load tests against production-equivalent environments to identify bottlenecks before they become incidents. Disclosed as an ongoing practice.
Multi-Region DR Drills
Multi-region failover drills are documented as normalized since May 2024. Rollback processes are standardized and regularly rehearsed â not theoretical.
Public Status Page
Catcrs uses standardized templates for event timelines and root cause summaries. Root cause analysis is published after major incidents for external evaluation.