Invo vs MetaMask

Name: Invo vs MetaMask OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

MetaMask leads on the only live benchmark. MetaMask wins on Hyperliquid frontends builder revenue leaderboard ($64.1K vs $37.5K).

Read methodology Last measured Tue, 25 Aug 2026 14:30:05 UTCWindow: rolling 24h1 shared benchmark

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).

MetaMask

MetaMask is the largest self-custody EVM wallet; its Hyperliquid integration routes perps orders through a registered builder code so users can trade HL from within the wallet.

Side by side measurements

Hyperliquid frontends builder revenue leaderboard

Trading

Provider	Builder fees collected	Volume routed	Users 24h	Effective fee bps	Time since last fill
Invo	$37.5K	$107.01M	9,270	0.035%	20.0 min
MetaMask	$64.1K	$67.46M	1,717	0.095%	20.0 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.

Frequently asked questions

Invo vs MetaMask: which one is better?

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

Which is cheaper, Invo or MetaMask?

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

How is the Invo vs MetaMask 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.