Invo vs Phantom

Phantom leads on the only live benchmark. Phantom wins on Hyperliquid frontends builder revenue leaderboard ($54.2K vs $36.6K).

Read methodology Last measured Window: rolling 24h1 shared benchmark
Invo logo
Invo

Invo is a Hyperliquid-powered social trading mobile app supporting 170+ perp pairs with copy-trading and a registered builder code (HL referral code INVO, 25k+ referrals).

Phantom logo
Phantom

Phantom is the leading multi-chain crypto wallet on Solana, Ethereum, and Bitcoin; its Hyperliquid perps tab routes orders with a registered builder code so users trade HL directly from the wallet UI.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading
ProviderBuilder fees collectedVolume routedUsers 24hEffective fee bpsTime since last fill
Invo$36.6K$104.53M9,2480.035%22.7 min
Phantom$54.2K$108.32M5,8640.050%22.7 min

Ranking is by raw builder fee revenue in USD, not by value for users. Bigger number means more fees collected via the on-chain builder code field. For the trader cost perspective, switch to the Effective fee bps companion tab. Native Hyperliquid UI orders carry no builder code and are excluded. Data from a local hl node tailing every fill on mainnet.

Rolling 24h · Builder fees collectedRaw JSON

Frequently asked questions

Invo vs Phantom: which one is better?

Invo and Phantom are compared on 1 shared OpenChainBench benchmarks. Phantom leads on Hyperliquid frontends builder revenue leaderboard. See the live table on this page for every metric.

Which is cheaper, Invo or Phantom?

On the Hyperliquid frontends builder revenue leaderboard benchmark, Phantom leads at $54.2K versus Invo at $36.6K. Live measurement is updated continuously by the OpenChainBench harness.

How is the Invo vs Phantom comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

Related comparisons

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.