ApexLiquid vs Gem Wallet

ApexLiquid leads on the only live benchmark. ApexLiquid wins on Hyperliquid frontends builder revenue leaderboard ($802.44 vs $0.8506).

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

ApexLiquid is a Telegram bot and smart wallet that auto copies on chain smart money traders on Hyperliquid in roughly one second, routing mirrored fills via a registered builder code.

Gem Wallet logo
Gem Wallet

Gem Wallet is a multichain self custody mobile wallet with a built in Trade Perpetuals section that routes orders directly into Hyperliquid via a registered builder code.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading
ProviderBuilder fees collectedVolume routedUsers 24hEffective fee bpsTime since last fill
ApexLiquid$802.44$1.68M1160.048%1.6 s
Gem Walletprovisional$0.8506$3,889.3520.022%3.2 h

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

ApexLiquid vs Gem Wallet: which one is better?

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

Which is cheaper, ApexLiquid or Gem Wallet?

On the Hyperliquid frontends builder revenue leaderboard benchmark, ApexLiquid leads at $802.44 versus Gem Wallet at $0.8506 (provisional). Live measurement is updated continuously by the OpenChainBench harness.

How is the ApexLiquid vs Gem Wallet 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.

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.