teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 43 Projects Releases Packages Wiki Activity Actions 422
teleo-codex/entities/internet-finance/jupiter.md
m3taversal 1fef01b163 fix: prefix 543 broken wiki-links with maps/ directory 
13 map file targets were linked as bare names ([[livingip overview]])
but files live at maps/. Script walks all claim files outside maps/
and prefixes with maps/ path. 351 files modified, zero remaining
bare instances, zero double-prefixes.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-21 14:54:41 +01:00

3.2 KiB
Raw Blame History

type entity_type name domain handles website status tracked_by created last_updated category stage key_metrics built_on tags
entity company Jupiter internet-finance
@JupiterExchange
https://jup.ag active rio 2026-03-11 2026-03-11 DEX aggregator / DeFi hub (Solana) mature
role_in_ecosystem omnipair_catalyst
Primary aggregator for MetaDAO ecosystem token routing Jupiter SDK integration expected to ~3x OmniPair volume
Solana
DEX-aggregator
solana
infrastructure
metadao-adjacent

Jupiter

Overview

The dominant DEX aggregator on Solana — routes trades across all Solana AMMs to find optimal execution. Critical infrastructure for the MetaDAO ecosystem: Jupiter integration determines whether ecosystem tokens are tradeable by the broader Solana market. The Jupiter team forked OmniPair's SDK (as of ~March 2026) to enable direct routing through OmniPair pools, making this integration the single highest-impact catalyst for OmniPair's volume growth.

Current State

  • Aggregator role: Routes trades across Raydium, Meteora, OmniPair, and other Solana AMMs. Being listed on Jupiter is effectively a prerequisite for meaningful trading volume on Solana.
  • OmniPair integration: Jupiter team forked OmniPair's SDK (~March 2026). Integration expected to roughly triple OmniPair volume and close most of the APY gap with Raydium. This is the single highest-impact near-term catalyst for the MetaDAO ecosystem's DeFi infrastructure.
  • Ranger Finance: Ranger's perps aggregation product aggregated Jupiter (among others) before its liquidation.
  • Ecosystem significance: Jupiter is not a MetaDAO ecosystem project — it's Solana-wide infrastructure. But its routing decisions determine liquidity accessibility for every MetaDAO token.

Competitive Position

  • Dominant position: The default swap interface for Solana users. Near-monopoly on DEX aggregation.
  • Infrastructure dependency: MetaDAO ecosystem tokens that aren't routed through Jupiter have severely limited discoverability and volume. OmniPair's DexScreener visibility issue (~10% of liquidity displayed) compounds this — Jupiter routing partially compensates.
  • Not a direct competitor: Jupiter aggregates, not competes with, MetaDAO ecosystem AMMs. The relationship is symbiotic — more AMMs with unique pools give Jupiter more routing options.

Relationship to KB

Relevant Entities:

Topics: