Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Jupiter: a Solana route aggregator |
|---|---|
| What the text proposes | Jupiter publishes a router that searches Solana venues for a path and settles it in one transaction. The router is not a liquidity pool. |
| Who may write | Jupiter |
| What is settled | The metis or successor routing engine, as the docs name it, chooses a path. The path can include AMMs and order books. |
| Load-bearing assumption | No volume share is stated here. |
| What this library says afterwards | A reading of the project's public design document. Not a copy, not a benchmark, and not an offer. |
| Rights | Official external source only |