m3taversal
018ee566e2
- What: Rewrote all 10 ownership coin entity files (mtnCapital, OmniPair, Umbra, Avici, Loyal, ZKFG, Paystream/PAYS, Solomon/SOLO, Ranger, P2P.me) with standardized frontmatter schema for dashboard consumption. Deduplicated 9 redundant files (Ranger had 4, P2P had 4, Umbra had 2, OmniPair had 2). Updated all wiki links across decisions/, sectors/, and entities/ to point to canonical files. - Why: m3ta requested portfolio dashboard. Entity stubs had near-zero structured data. Dashboard rendering requires standardized schema with raise amounts, token addresses, traction metrics, and chain data. - Gaps flagged: Token addresses for 5 coins, treasury multisig addresses for all 10, LP pool addresses, mtnCapital raise details. Phase 2 cron script will auto-fill on-chain numerics. Pentagon-Agent: Rio <244BA05F-3AA3-4079-8C59-6D68A77C76FE>
50 lines
3.2 KiB
Markdown
50 lines
3.2 KiB
Markdown
---
|
|
type: entity
|
|
entity_type: company
|
|
name: "Jupiter"
|
|
domain: internet-finance
|
|
handles: ["@JupiterExchange"]
|
|
website: https://jup.ag
|
|
status: active
|
|
tracked_by: rio
|
|
created: 2026-03-11
|
|
last_updated: 2026-03-11
|
|
category: "DEX aggregator / DeFi hub (Solana)"
|
|
stage: mature
|
|
key_metrics:
|
|
role_in_ecosystem: "Primary aggregator for MetaDAO ecosystem token routing"
|
|
omnipair_catalyst: "Jupiter SDK integration expected to ~3x OmniPair volume"
|
|
built_on: ["Solana"]
|
|
tags: ["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
|
|
- [[permissionless leverage on metaDAO ecosystem tokens catalyzes trading volume and price discovery that strengthens governance by making futarchy markets more liquid]] — Jupiter routing is the primary channel through which broader Solana liquidity reaches MetaDAO ecosystem tokens
|
|
- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]] — Jupiter integration is infrastructure-level validation for the MetaDAO ecosystem
|
|
|
|
---
|
|
|
|
Relevant Entities:
|
|
- [[omnipair]] — SDK integration (highest-impact catalyst)
|
|
- [[meteora]] — routed AMM
|
|
- [[raydium]] — routed AMM
|
|
- [[ranger-protocol]] — former aggregation client (liquidated)
|
|
|
|
Topics:
|
|
- [[internet finance and decision markets]]
|