Connected venues

Read to
the summit.

Every venue is read the way the venue means it: settlement, margin, and every position you have open. Hyperliquid runs deepest.

Hyperliquid

native dex + builder dexes
reading · live
  • native dexDirect
  • builder dexes (HIP-3)Resolved
  • per-dex marginIndependent
  • balancesLive
  • settlementVerbatim

Most trackers read only the native dex. Tarn reads the builder dexes too: every position, every dex, its own margin.

CryptoStocksCommoditiesIndicesFX

Bybit

spot + perpetuals
reading · live
  • spot holdingsDirect
  • open perpetualsLive
  • account balancesLive
  • settlementVerbatim

A tracker reads your spot balance and your stablecoins and calls that your portfolio. It never sees the perpetuals you have open, which is exactly where the risk sits. Tarn reads the open positions too, each against its entry, its leverage, and its liquidation.

Binance

spot + futures
reading · live
  • spot holdingsDirect
  • open futuresLive
  • account balancesLive
  • settlementVerbatim

Most trackers stop at the Binance spot wallet. The open futures positions, the leverage on them, the liquidation price, none of it shows. Tarn reads the positions the way Binance itself accounts for them, not just the coins sitting still.

Builder DEXs (HIP-3) are a Hyperliquid feature, and Bybit and Binance do not have them. Every connection is read-only. Wallets are watched read only by address across Bitcoin, Ethereum, Solana and Tron, and anything else is added by manual entry.

Tarn connects read only to Bybit, Binance and Hyperliquid, including Hyperliquid’s builder dexes (HIP-3), with each dex’s margin kept independent. It is a native macOS app, and your data stays on the machine.

The whole account

One account is
never one number

Where the money actually sits, read without flattening.

A serious account does not live in one place. Perps run on one venue, spot sits on another, a core position waits in cold storage, and on Hyperliquid the account divides again: the native dex and the builder dexes, each market carrying its own independent margin. Any single number that claims to summarize all of this is hiding most of it.

Most trackers flatten anyway. They net every venue, every margin, every settlement convention into one figure, and call the flattening a feature. The figure moves, and you cannot say why, because the structure that produced it has been erased.

Tarn refuses the flattening. Each venue is read in its own register: settlement taken verbatim, margin kept where the venue keeps it, builder dexes resolved separately from the native dex. Wallets are watched read only by address across Bitcoin, Ethereum, Solana and Tron, and anything else is added by manual entry, so what you hold off venue stands beside the live positions without pretending to be one of them. The whole account is visible at once, and no part of it is blurred to get there.

The read

How the
read works

Read-only keys, your machine, the venue. Nothing in between.

Every connection is a read-only key, held in the macOS Keychain and nowhere else. Calls run straight from your machine to the venue: no Tarn backend, no account, no relay that could log, hold, or lose what passes through it.

Positions stream from each venue’s own socket, so a fill shows the moment it lands. If the socket drops, REST takes over within seconds. And when a price can no longer be trusted, Tarn marks the figure stale, never guessed. Read everything, touch nothing: the keys cannot place an order or move a coin, so neither can Tarn, and neither can anyone who compromises it.

The next line

Tell us what Tarn
should climb next

A venue you trade on, a capability you want. One trader reads every message, and you will hear back when it ships.

Used only to reply to you and tell you when it ships. Nothing else.

A darkened massif under heavy cloud
Get Tarn

Begin the climb.

Install the instrument · the permit brings it live