Non-Custodial Security Model
BlockRotate is built around a non-custodial design. You control your keys. The platform coordinates execution without holding your funds.
Security is a model, not a badge
The real questions: where do funds sit. What permissions exist. How is execution routed. What controls activate when conditions degrade.
Non-custodial by design
BlockRotate does not hold user funds. The platform controls detection, routing, and execution logic. It does not control your wallet. That boundary is the foundation of our copy trading bot system. In practice, this model powers Polymarket copy trading where every mirrored trade is signed with scoped L2 credentials that can trade but cannot withdraw.
Execution controls and private handling
Private transaction mempools and front-running protection. Route privacy keeps execution out of public visibility. Trade propagation is a security concern, not just a latency concern. See the copy trading infrastructure architecture for how routing and security intersect. For how L2 credentials enable this separation between trading and custody, read our guide to Polymarket L2 credentials.
Auditing and operational review
Smart contracts and core modules undergo third-party review. The audit scope and cadence are public. No trust through slogans — trust through verification.
What users should evaluate
Check every provider against the same list: custody model, permission scope, route exposure, audit coverage, failure handling, operator transparency.
Understanding Trust
Start with the custody model. Then the execution path. Review how BlockRotate handles permissions, routing, and safeguards — before comparing marketing claims.
Secure Your SetupFrequently Asked Questions
Is BlockRotate custodial?
No. BlockRotate is built around a non-custodial model and does not hold user funds.
What does non-custodial mean in this context?
It means the platform coordinates detection, routing, and execution logic without taking ownership or control of user assets. Users maintain full control of their private keys and funds at all times, drastically reducing counterparty and platform hack risks.
Why is execution handling part of security?
Route exposure, transaction handling, and execution flow can affect front-running risk, slippage exposure, and operational control.
What should users verify before trusting a copy trading platform?
They should verify custody boundaries, required permissions, audit coverage, route handling, and how the system behaves when execution conditions degrade.