Trust Model
How Klovr is designed to remove discretionary trust from prop trading.
The core idea
Traditional prop firms ask traders to trust a private company. The company controls the rules, the capital, the scoreboard, and the payout process.
Klovr is built differently. Traders are evaluated through transparent risk systems, funding decisions move to the DAO, and funded-account settlement is designed to be enforced by protocol rules rather than company discretion.
Trust model at a glance
Current status
Klovr is currently in private alpha.
Alpha accounts are simulated: no deposits, no withdrawals, and no real funded execution. The alpha is used to prove the trading experience, risk rules, ledger, leaderboard, and Performance Passport before funded accounts go live.
Funded accounts are the roadmap. The core non-custodial execution architecture has been validated on Hyperliquid mainnet, but the public funded product still requires production hardening, legal review, and security review.
What you do not have to trust
The ledger
Klovr is ledger-first.
Every meaningful account event is recorded: orders, fills, fees, equity updates, liquidations, rule breaches, account passes, and admin actions. Events are append-only and hash-chained, meaning historical edits are detectable because changing one event breaks the chain after it.
Account state should be explainable from the ledger, not from a private dashboard number.
The risk engine
Klovr's risk engine evaluates accounts against explicit rules.
The engine tracks equity, PnL, drawdown, daily loss, trading days, closed trades, and breach status. It is designed so pass and breach decisions come from deterministic inputs rather than manual judgement.
For alpha, this powers simulated challenge evaluation. For the full Klovr Proptocol, the same philosophy extends into funded-account rules and settlement.
Execution model
Alpha evaluations are simulated. Orders are filled by Klovr's engine against live market data; there is no real capital, no counterparty, and no A-Book/B-Book dealer model.
Funded accounts are different. Funded execution is designed to be A-Book: orders execute on Hyperliquid's real order book, while settlement and withdrawal rights remain separated from trading activity.
Non-custodial funded accounts
The funded-account roadmap is built around a simple principle:
The trader should be able to trade within rules, but neither the trader nor Klovr Labs should be able to move funds outside the rules.
For funded accounts, capital movement, settlement, breaches, and eligible withdrawals are designed to be enforced by protocol logic. Once a trader satisfies the protocol rules, neither the DAO nor Klovr Labs should be able to manually block an eligible withdrawal.
DAO and Labs
The DAO should be able to replace Labs if it chooses another evaluator or risk-service provider.
What happens if something goes wrong?
What we do not publish
Klovr's public docs explain the trust guarantees, not the full implementation.
We do not publish low-level contract architecture, key-management mechanics, settlement internals, risk formulas, or security-sensitive infrastructure details before production hardening and audit.
Important status boundary
Private alpha proves the simulated evaluation layer. The full trustless funded protocol is the roadmap: mainnet-validated, technically central to Klovr, and not yet a public funded product.