> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ordr.trade/llms.txt
> Use this file to discover all available pages before exploring further.

# Why ordr.trade

> The problem with trading on Solana today, and why ordr.trade exists

## Market making is a race against time

A market maker's job is to keep their buy and sell prices close to the real market
price at all times. When the real price moves, the market maker has to update their
price fast. If they are too slow, someone else can trade against their old price and
make an easy profit at the market maker's expense. This is sometimes called getting
picked off.

On most exchanges this race is fair, because everyone pays for the same kind of fast
connection and everyone competes on roughly equal terms. On Solana, the race is tilted
against the market maker.

## Why Solana makes this harder

Most on-chain orderbooks still use one shared account to hold the whole order book.
Every market maker who wants to change a price has to update that same account.

When the market moves fast, that becomes a problem. If a hundred market makers all
try to update their prices in the same moment, only one of them can go first.
Everyone else has to wait, pay higher fees to try to go first, or get stuck with an
old price. This is often called "write-lock contention":
everyone is fighting to write to the same account, and only one write per account
can happen per slot. A bot watching the market can trade against that old price
before the market maker has a chance to fix it.

## How the market reacted: propAMMs

To avoid this problem, several teams built a different kind of program, often called
a propAMM. Instead of posting many individual orders, a propAMM uses a single pricing
formula and updates just a few numbers whenever the market moves. This made price
updates fast and cheap, and today the majority of all spot trading on Solana flows
through this kind of program.

This approach solves the speed problem, but it creates new ones.

* **Each one is a black box.** A propAMM is a single closed program run by one team.
  Nobody outside that team can see what is actually happening inside
  it or why it quotes the price it does. That one team controls everything about how
  the pool behaves, and when you trade through an app like Jupiter, you are not
  trading against one shared, visible market. You are being routed across many of
  these separate black boxes, stitched together behind the scenes.
* **The price you see is not always the price you get.** An aggregator quotes a
  propAMM by simulating a trade against its state at that moment, but the pool's
  price is set entirely by its own closed logic, with nothing stopping it from
  changing before your trade actually settles. Studies of propAMM pricing have found
  cases where a pool quotes an attractive price in the window aggregators sample
  from, then settles trades at a worse one once they land, a pattern distinct from
  the market simply moving. Because the logic is closed, neither a trader nor an
  aggregator can tell the two apart from the outside.
* **The pricing logic is hidden.** The same closed code that quotes your price also
  decides how much of your order gets filled. There is no way for you or an aggregator
  to check the math.
* **Only a few teams can run one.** Building a propAMM means writing a custom Solana
  program, hiring engineers who know how to make it fast, and solving hard problems
  around getting transactions to land on time. This is expensive, so only a small
  number of well funded teams can do it. Everyone else is locked out.
* **Only that one team ever gets to benefit.** Because a propAMM is one closed
  program run by one operator, no other market maker can plug into it and quote
  alongside it. The speed and tight pricing it achieves stay locked inside that one
  team, instead of being something any market maker who wants to compete can use.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.