Onchain Privacy for Hedge Funds: Separating Trades from the Fund Wallet

Can a hedge fund trade onchain without exposing its book

Not completely. Onchain venues are designed to make transactions and account activity observable. A hedge fund cannot place a visible order, hold a public position and simultaneously make that market activity disappear.

It can, however, reduce how easily individual trades and positions are connected to its recognised treasury, fund or strategy wallet. That distinction matters. The market can still see execution, while learning less about the institution behind it and the broader portfolio that the activity belongs to.

For hedge funds considering Hyperliquid, the practical objective is therefore not invisibility. It is controlled public attribution: keeping a complete internal view of risk while limiting the external trail that connects funding, execution, PnL and liquidation information to one persistent address.

What exposing the book means onchain

A hedge fund's book is more than a list of open positions. It includes directional exposure, hedges, concentration, leverage, margin usage, entry levels, trading cadence and the relationship between positions across markets.

On a public venue, an observer who knows a fund's address may be able to monitor:

• Open perpetual positions and their direction
• Position size and average entry price
• Leverage, margin mode and liquidation levels
• Unrealised PnL and changes in account equity
• Open orders, fills and order history
• Funding payments and holding periods
• Deposits, withdrawals and collateral movements
• Repeated activity across the same markets

No single field reveals a complete investment thesis. The risk grows when these signals are combined over time. A persistent wallet can become a public record of how the fund deploys capital and responds to changing market conditions.

What observers may infer from a persistent fund wallet

Directional conviction

Position size, duration and repeated additions can indicate which trades carry the most conviction. Even when the underlying research remains private, the resulting exposure can reveal where the fund is willing to concentrate risk.

Entry and exit discipline

A visible history of fills and position changes may show whether the fund scales into trades, takes profit in stages, cuts exposure at defined thresholds or holds through volatility. These patterns can become useful context for copy traders and competing desks.

Hedging relationships

Positions across related markets may reveal an intended hedge, relative-value trade or basis strategy. An observer may not know the exact mandate, but correlated changes can expose how the fund offsets risk.

Stress and liquidation boundaries

Leverage, margin usage and liquidation levels can show when a position is moving closer to a risk boundary. This information does not guarantee that another participant can force an outcome, but it can make the fund's constraints easier to estimate.

Capital allocation

A long-running wallet can show which markets receive the most capital and how exposure changes across a cycle. Over time, the wallet becomes a public portfolio history rather than a record of isolated trades.

Transparency and attribution are different

Onchain trading requires transparency at the market level. Orders, fills and positions must remain verifiable. The more avoidable exposure comes from attribution: the ability to connect that public activity to a known fund and then combine it with the fund's earlier trading history.

This creates two separate questions:

1. Can the fund remove its activity from the public market?
2. Can the fund reduce the direct public link between that activity and its recognised wallet?

The answer to the first question is no. The second is possible when execution is separated from the persistent wallet that supplies capital and carries the fund's public identity.

Why common operating structures may not be enough

One wallet is operationally simple but information rich

Funding and trading from one address simplifies monitoring and reconciliation. It also concentrates positions, PnL, margin and history into a single public profile.

Subaccounts separate mandates, not necessarily attribution

Subaccounts can help a fund organise strategies and permissions. They remain addressable accounts, and their public activity may still be studied when the relevant address or relationship becomes known.

Manual wallet rotation can create a new fingerprint

Moving between wallets reduces the history held by one address, but timing, funding paths, position sizes and repeated behaviour may reconnect the activity. Rotation also increases key management and reconciliation work.

Centralised venues change the trade-off

A centralised venue may reduce public position visibility, but it introduces custody, counterparty and withdrawal considerations. It also moves execution away from the onchain venue and liquidity the fund may specifically want to access.

What shielded execution changes

A shielded execution layer separates the wallet providing funds from the wallet that executes and holds a position. With ShieldTX, the general flow is:

1. The fund deposits USDC into its ShieldTX balance.
2. The fund submits a Hyperliquid perpetual order through ShieldTX.
3. A fresh execution wallet is funded for the position.
4. The order reaches Hyperliquid's native order book.
5. The position and its public account data sit on the execution wallet.
6. When the position is closed through ShieldTX, proceeds return to the shielded balance.

The trade is still onchain. Its size, direction, fills and market impact do not disappear. What changes is the direct public relationship between the execution wallet and the fund's recognised funding wallet.

For a hedge fund, this can reduce the amount of portfolio context available to an observer. A visible position on a fresh wallet provides less history than the same position added to an address already associated with the fund's treasury and earlier strategies.

What shielded execution does not hide

ShieldTX should not be interpreted as an invisible order book or a guarantee that no one can infer anything about a trade. Public observers may still see:

• The temporary wallet that executes the position
• Orders and fills on Hyperliquid
• Position size, direction and entry information
• PnL, leverage, margin and liquidation information on that wallet
• Market impact created by the order
• Deposits into and withdrawals from the ShieldTX system
• Solver and settlement activity

Sophisticated observers may also use timing, size and repeated behaviour to form hypotheses. Shielded execution reduces direct persistent attribution. It does not eliminate all statistical inference, execution risk or market signalling.

Execution structures at a glance

Where this can fit in a hedge fund workflow

A fund does not need to apply the same execution structure to every trade. The value of attribution separation is usually highest where public portfolio information is most sensitive.

Potential use cases may include:

• Directional positions that would reveal a high-conviction view
• Hedges that expose the risk profile of another position
• Larger positions accumulated over time
• Trades where copy activity can affect execution or exit conditions
• Selected strategies routed through a controlled API workflow

Latency-sensitive and high-frequency strategies require separate evaluation. ShieldTX states that shielded routing currently introduces a delay of a few seconds. A fund should confirm that supported order types, cancellation behaviour, throughput and failure handling fit the intended strategy before production use.

What an institutional team should evaluate

Internal risk visibility

The portfolio manager and risk team still need a complete view across all execution wallets. Public separation should never create fragmented internal monitoring.

Execution and latency

Measure the time from instruction to placement on Hyperliquid and test performance under realistic market conditions. Confirm how limit orders, partial fills, cancellations and emergency closes behave.

Reconciliation and reporting

Define how orders, fills, fees, funding, realised PnL and settlements feed into the fund's books and records. The external trail may be separated, but the internal audit trail must remain complete.

Permissions and key management

Review who can place orders, close positions and withdraw funds. API credentials, approval policies and incident procedures should fit the fund's existing control environment.

Compliance and counterparties

A hedge fund should assess the legal, regulatory, sanctions-screening, custody and reporting implications for its jurisdiction and mandate. Shielded execution changes public attribution, not the fund's compliance obligations.

Economics

Compare the value of limiting information leakage with routing fees, gas costs, latency and operational effort. The appropriate structure may differ by strategy and position size.

Review what the market can already see

Before changing execution, review the public footprint of the fund's current Hyperliquid address. The ShieldTX scanner can help identify visible activity and follower patterns using recent public data. Scan your public Hyperliquid wallet.

The scanner is a diagnostic tool. Similar activity between wallets is not proof of copying or common control, but it can identify repeated patterns that deserve closer review.

How to access ShieldTX

ShieldTX is a non-custodial shielded execution layer for Hyperliquid perpetuals. Hedge funds and professional trading teams can request private beta access and evaluate whether the available workflow fits selected strategies.

Request access to ShieldTX