Rubik Capital
Blockchain intelligence, dual execution, and defense-in-depth risk control — built as a system of constraints rather than a single algorithm firing orders at the exchange.
A signal in Rubik is a proposal to act, not an order to execute.
Rubik reads on-chain and market-state data through several independent analytical layers. A trading initiative never reaches the exchange directly: it passes through capital allocation, portfolio-level limits, a separate microstructure control layer, and protective execution machinery.
A new position is evaluated against the existing portfolio, available capital and current exposure — never on its own merits alone.
Portfolio-level constraints take precedence. The system will decline new exposure even when an analytical layer finds the entry attractive.
Microstructure control can shrink or block an entry outright, and the main trading logic may not override it.
On-chain state and live market conditions enter the system.
Several independent contours form a trading initiative.
Can this exposure fit inside current capital and risk?
A final independent review of the initial entry.
System limits and execution-layer health are verified.
Only a permitted action reaches Hyperliquid.
Rubik runs as two independent execution instances on separate trading accounts, held together by a single portfolio-level control. The split distributes trading load, exposure and strategy capacity across two planes.
Under certain conditions the instances can hold opposite directions on the same instrument — long on one, short on the other — used as a controlled element of portfolio hedging.
Correctly read: controlled opposing exposure, not a mandatory symmetric hedge. Positions need not open together, match in size, or hold a fixed ratio. The conditions that trigger this configuration are part of internal logic and are not disclosed.
Above the core decision logic sits a separate layer reading market microstructure. It does not look for opportunity — it judges whether an initial entry is admissible in current conditions, and it holds an independent right of veto.
Permit the original size of the initial order.
Cut the size of the initial position.
Decline to open the position at all.
This layer governs the creation of a new position. Once open, add / hold / reduce / exit decisions belong to the main analytics and position management. The features, combinations and thresholds behind the verdict are closed.
Rubik is not built around a single stop mechanism. Between a trading idea and real risk stand several independent layers, each able to limit, shrink or halt the action.
A gross exposure ceiling per execution instance. Increase requests are cut or refused when they exceed the available risk budget.
Per-instrument limits that cap how much of the book any single market may occupy.
A preflight check before adding risk: the intended protective structure must remain valid against the venue's real liquidation boundary.
Open positions carry protective orders, and their presence is verified against actual exchange state — not against an internal note saying they should exist.
Stale upstream state, lost connectivity or unconfirmed venue state can close the path to new entries.
A critical-drawdown kill mechanism can stop trading and close positions. Its threshold is internal and not disclosed.
Reducing existing risk always outranks creating new risk. When state cannot be trusted, the system shuts the door on new entries while leaving the existing book free to exit safely.
Trading authority ≠ withdrawal authority.
Rubik separates the power to trade from the power to move money. The system manages positions within its permitted execution access and holds no ability to withdraw funds. Control of capital stays outside the trading agent.
Modelled monthly rates by account size. The rate peaks at Core — below it commissions weigh heavier on a smaller slot, above it the book's own market impact narrows the tradable universe. These are planning inputs, not results.
| Monthly rate | Entry | Core | Extended | Large |
|---|---|---|---|---|
| Stress edge degrades | 3.6% | 4.0% | 3.8% | 2.8% |
| Base realistic | 9.0% | 10.0% | 9.5% | 7.0% |
| Optimistic top of sample | 18% | 20% | 19% | 14% |
Participants pool capital into a single trading book. Each holds an economic share; performance is measured against a personal high-water mark.
A dedicated instance of Rubik on managed infrastructure, trading the client's own account. The client keeps custody; Rubik keeps the canonical trading state.
A non-custodial vault contract on HyperEVM. The contract owns its own trading account; funds are never handed to us.
Fee rates, legal structure and service terms are settled individually and are not published here.
No forms and no sign-up. Write to us directly and we will take it from there.