# met.guide: Meteora agent skill

Use this skill to set up a Solana test wallet and inspect Meteora Dynamic Liquidity Market Maker (DLMM) pools. Use it to plan liquidity provider (LP) actions. Read the companion guides at [met.guide](https://met.guide).

## Quick Start (macOS, Linux, or WSL)

1. `sh -c "$(curl -sSfL https://release.anza.xyz/stable/install)"`
2. `export PATH="$HOME/.local/share/solana/install/active_release/bin:$PATH"; solana --version`
3. `mkdir -p .solana-test && HOME="$PWD/.solana-test" solana config set --url https://api.devnet.solana.com`
4. `HOME="$PWD/.solana-test" solana-keygen new --no-bip39-passphrase --silent --outfile .solana-test/devnet-test.json`
5. `HOME="$PWD/.solana-test" solana config set --keypair "$PWD/.solana-test/devnet-test.json"`
6. `HOME="$PWD/.solana-test" solana balance`

Choose the [TypeScript software development kit (SDK)](#official-typescript-dlmm-sdk) for a bot or [Gateway](#hummingbot-gateway) for Hummingbot. Read the [live Meteora docs](https://docs.meteora.ag/) before write transactions. See [wallet safety](#1-wallet-and-network-safety) and the [official command-line interface (CLI) install guide](https://solana.com/docs/intro/installation/dependencies#install-solana-cli).

## 1. Wallet and network safety

**Use a throwaway keypair on devnet by default. Never paste a seed phrase, private key, passphrase, or keypair JSON into an AI chat or shell history.** Keep `.solana-test/` out of Git. Delete test keys when done. Devnet SOL has no mainnet value.

**Devnet airdrops are rate limited.** Try `HOME="$PWD/.solana-test" solana airdrop 1`. Then check `HOME="$PWD/.solana-test" solana balance`. A failed airdrop does not mean the key or CLI is broken.

The Quick Start's `--no-bip39-passphrase` supports unattended creation of a disposable key. For funded wallets, generate offline in a private interactive terminal with `solana-keygen new --outfile <secure-new-path>` and a strong, unique BIP39 passphrase. Back up the recovery phrase offline. The JSON keypair file remains plaintext; protect it with strict file permissions or use a hardware wallet. Passphrase key generation needs an interactive terminal. It failed in the noninteractive test; piped input did not work.

The Quick Start gives each CLI command an isolated `HOME`. If you cannot override `HOME`, pass `-C "$PWD/.solana-test/config.yml"` to each `solana` command. Confirm the cluster with `solana genesis-hash` (verified devnet hash in [section 5](#5-test-record-and-source-limits)). Set the remote procedure call (RPC) endpoint explicitly each session. Public RPC endpoints: `https://api.devnet.solana.com` and `https://api.mainnet-beta.solana.com`. Do not infer a cluster from a wallet address. Mainnet needs funded assets and a SOL fee reserve.

Before signing, ask the operator to confirm the cluster, wallet, pool, range, amounts, and expected fees. A timeout or 504 response does not prove a write failed. The transaction can still land, and a resend can create a second one. Check any returned signature with `getSignatureStatuses` before a retry. Recheck wallet balances and positions if the transaction status is unclear.

## 2. Choose a Meteora tool

### Official TypeScript DLMM SDK

For a custom bot, use Meteora's [official DLMM SDK](https://github.com/MeteoraAg/dlmm-sdk/tree/main/ts-client). In a separate SDK project:

```sh
npm i @meteora-ag/dlmm @coral-xyz/anchor @solana/web3.js
```

This read-only example needs a real devnet DLMM pool address. Check its pair and token mints. Do not use a mainnet pool address on devnet.

```ts
import DLMM from "@meteora-ag/dlmm";
import { Connection, PublicKey } from "@solana/web3.js";

const poolAddress = process.env.METEORA_DEVNET_POOL_ADDRESS;
if (!poolAddress) throw new Error("Set METEORA_DEVNET_POOL_ADDRESS");
const connection = new Connection("https://api.devnet.solana.com");
const pool = await DLMM.create(connection, new PublicKey(poolAddress));
const activeBin = await pool.getActiveBin();
// activeBin.price is per lamport; convert it to a token price.
console.log(activeBin.binId, pool.fromPricePerLamport(Number(activeBin.price)));
```

Read the [SDK README](https://github.com/MeteoraAg/dlmm-sdk/tree/main/ts-client) before building writes. This example came from it and was not run against a pool in this test.

### Hummingbot Gateway

Gateway **2.17.0** was tested on mainnet-beta on **2026-10-09** with direct HTTP calls and a small funded wallet. The Hummingbot client path was not tested. Use the [Meteora connector guide](https://hummingbot.org/exchanges/gateway/meteora/) and [Gateway installation guide](https://hummingbot.org/gateway/installation/) for current setup details.

#### Run Gateway

The 2026-10-09 test used Docker Hub's `hummingbot/gateway:latest` at version 2.17.0; a `ghcr.io` pull was denied. Use the 2.17.0 image for these routes. It sets `DEV=true` and serves plain HTTP. Enter the passphrase in a private terminal. Bind the port to loopback. Mount `conf`, `certs`, and `logs` to retain wallets and settings. Gateway fills missing config files from templates.

```sh
mkdir -p gateway/conf gateway/certs gateway/logs
read -rs GATEWAY_PASSPHRASE && export GATEWAY_PASSPHRASE
docker run -d --name hb-gateway -p 127.0.0.1:15888:15888 \
  -e GATEWAY_PASSPHRASE \
  -v "$PWD/gateway/conf:/home/gateway/conf" \
  -v "$PWD/gateway/certs:/home/gateway/certs" \
  -v "$PWD/gateway/logs:/home/gateway/logs" \
  hummingbot/gateway:version-2.17.0
curl -s http://127.0.0.1:15888/
```

The health response is `{"status":"ok"}`. **Set `GATEWAY_PASSPHRASE`; Gateway uses it to encrypt stored wallets. Gateway 2.17.0 never reads `GATEWAY_PASSCODE`.** Keep the passphrase stable and out of prompts and history. Do not use the sample value `admin`.

In Docker, `/docs` returns 404 because Gateway hides Swagger when bound to a non-loopback host. Read its bundled schema with `docker exec hb-gateway cat openapi.json`. Enable `GATEWAY_ENABLE_DOCS=true` only with the port bound to loopback.

Read `gateway/conf/connectors/meteora.yml` after startup. The official defaults are `slippagePct: 1` (1% swap tolerance, not a profit target) and `strategyType: 0`; the tested container had `slippagePct: 2`. The six shape presets are `SpotImBalanced=0`, `CurveImBalanced=1`, `BidAskImBalanced=2`, `SpotBalanced=3`, `CurveBalanced=4`, and `BidAskBalanced=5`. `open` and `add` accept per-request `strategyType`. A shape does not set rebalance rules. Restart Gateway after config changes.

The separate Hummingbot client uses its `docker-compose.yml`, `gateway connect solana`, and `gateway-files/conf/connectors/meteora.yml`. That path was not tested; see the [Hummingbot installation guide](https://hummingbot.org/installation/).

#### Import and check a wallet

Use a separate wallet with only test funds. Send `POST /wallet/add` with `{"chain":"solana","privateKey":"<BASE58_OF_64_BYTE_SECRET_KEY>"}`. A Solana CLI JSON keypair holds the 64 bytes as an array; convert them to base58 offline on the same host. Put the request body in a mode-600 file. Send it with `curl --data @<file>`. Delete the file after the request. Check the imported address with `GET /wallet` before any write.

**A `0x` hex string of the raw key bytes is rejected with `Unable to retrieve wallet address`.** If the passphrase is absent in the container, wallet import fails with a passphrase error.

For balances, send `POST /chains/solana/balances` with `{"network":"mainnet-beta","address":"<WALLET_ADDRESS>"}`. The optional `tokens` field is an array of symbols; `tokenSymbols` is rejected. This route uses `network`, not `chainNetwork`, and returns a `balances` map. The funded test read both SOL and USDC.

#### Unified concentrated liquidity market maker (CLMM) routes

Gateway 2.17.0 puts Meteora DLMM under `/trading/clmm/*`. DAMM v2 uses `/trading/amm/*`; old `/connectors/meteora/clmm/*` paths were removed. See the [2.17.0 release notes](https://hummingbot.org/release-notes/2.17.0/). DAMM v2 positions do not qualify for the DLMM referral terms below.

Set `connector` to `meteora`. Set `chainNetwork` to `solana-devnet` or `solana-mainnet-beta` (dash format; `solana/mainnet-beta` is rejected). **If omitted, `chainNetwork` defaults to `solana-mainnet-beta` even on write routes. Send it every time.** Schemas reject unknown fields.

`POST` bodies need `connector`, `chainNetwork`, and `walletAddress`, plus:

| `/trading/clmm/` route | Additional fields |
| --- | --- |
| `open` | `poolAddress`, `lowerPrice`, `upperPrice`, `baseTokenAmount` and/or `quoteTokenAmount`; optional `slippagePct`, `strategyType` |
| `add` | `positionAddress`, `baseTokenAmount` and/or `quoteTokenAmount`; optional `slippagePct`, `strategyType` |
| `remove` | `positionAddress`, `percentageToRemove` (0–100); optional `slippagePct` |
| `collect-fees` | `positionAddress` only |
| `close` | `positionAddress`; `slippagePct` is accepted but ignored |

`GET` query strings need `connector` and `chainNetwork`, plus:

| `/trading/clmm/` route | Additional fields |
| --- | --- |
| `fetch-pools` | Optional `query=SOL-USDC`, `limit` (default 50), `sortBy`, `page`, `includeUnverified` |
| `pool-info` | `poolAddress`; optional `binCount` |
| `position-info` | `positionAddress` only |
| `positions-owned` | `walletAddress` |
| `quote-liquidity` | `poolAddress`, `lowerPrice`, `upperPrice`, `baseTokenAmount` and/or `quoteTokenAmount`; optional `slippagePct` |

`fetch-pools` has no `tokens` field; each result has a `price`. **`open` takes decimal prices, not bin IDs. For a one-sided open, exactly one of `baseTokenAmount` and `quoteTokenAmount` must be greater than zero.** Read a fresh `pool-info` before choosing the range. `position-info`, `collect-fees`, and `close` use `positionAddress`; do not send `poolAddress` or `positionRef` to them.

Example read, then an operator-approved one-sided open and close. Replace placeholders and prices with fresh data:

```sh
GW=http://127.0.0.1:15888
curl -s "$GW/trading/clmm/fetch-pools?connector=meteora&chainNetwork=solana-mainnet-beta&query=SOL-USDC"
curl -s -X POST "$GW/trading/clmm/open" -H 'content-type: application/json' -d '{
  "connector":"meteora","chainNetwork":"solana-mainnet-beta","walletAddress":"<WALLET_ADDRESS>",
  "poolAddress":"5rCf1DM8LjKTw4YqhnoLcngyZYeNnQqztScTogYHAS6",
  "lowerPrice":109.2,"upperPrice":109.5,"baseTokenAmount":0.25}'
curl -s "$GW/trading/clmm/position-info?connector=meteora&chainNetwork=solana-mainnet-beta&positionAddress=<POSITION_ADDRESS>"
curl -s -X POST "$GW/trading/clmm/close" -H 'content-type: application/json' -d '{
  "connector":"meteora","chainNetwork":"solana-mainnet-beta","walletAddress":"<WALLET_ADDRESS>",
  "positionAddress":"<POSITION_ADDRESS>"}'
```

`close` removes all liquidity, claims pending fees, and refunds position rent in one transaction. A separate `collect-fees` is optional. **Meteora `close` has no minimum-amount check; Gateway ignores `slippagePct` there.** Read the position before closing. After a successful close, `position-info` returns 404 (`Position closed: <address>`) and `positions-owned` returns `[]`. Check the chain after each write, not just Gateway's response. In a 2026-10-15 funded test, an immediate token balance read returned zero after a successful close. Later reads showed the tokens; the cause is unverified. Retry a zero balance read. Make any pending swap recoverable on a later check.

#### Router swaps

Gateway routes swaps through external aggregators. `GET /trading/router/quote-swap` returns a quote; `POST /trading/router/execute-swap` executes a swap. The quote route accepts `GET` only; a `POST` there returns 404. Send `baseToken`, `quoteToken`, `amount`, and `side` (`BUY` or `SELL`). The token fields accept a symbol or mint address. Send a decimal base-token `amount` in user interface (UI) units. Gateway converts it to raw units. In a funded 2026-10-15 test, a raw integer amount requested 10^decimals times too much and failed simulation (Jupiter error 0x1788). The UI amount worked for a live swap.

#### Jupiter API key

The `jupiter` connector is the default swap router on `solana-mainnet-beta`. The tested Gateway 2.17.0 image sends keyless requests to `lite-api.jup.ag`. Jupiter announced that this host would shut down on 2026-10-30. The keyless container logged `No Jupiter API key configured. Using lite-api.jup.ag` on 2026-10-16.

Get a free application programming interface (API) key at the [Jupiter portal](https://developers.jup.ag/portal). Gateway 2.17.0 selects `api.jup.ag` and sends an `x-api-key` header when `apiKey` is nonempty. A placeholder such as `***` can select that path without a valid key. A keyed Gateway quote succeeded on 2026-10-29 after key installation and restart. That test set both Jupiter config fields, so it did not isolate the effective field. Inspect that image's config loader to find the effective `apiKey` field. Set the key only in that field. Restart Gateway. Run a read-only Jupiter quote to initialize the connector. Check a log entry from the current start for `Using Jupiter API with key`. Confirm that the quote succeeds. A log line alone does not confirm that the key works. For keyless use, use a build that sends requests to `api.jup.ag`.

#### Real pool and measured costs

The funded test used the Meteora DLMM **SOL/USDC bin-step-4 flagship pool** `5rCf1DM8LjKTw4YqhnoLcngyZYeNnQqztScTogYHAS6`. At open, the active bin was `-5531` near 109.49 USDC/SOL. `fetch-pools` also listed SOL/USDC steps 1, 10, and 20. Re-read pool state before each use.

The one-sided open placed **0.25 SOL** across 109.2–109.5 USDC/SOL, bins `-5538` to `-5530` (nine bins). Only bins at or above the active bin held SOL. **Price rose through the SOL-side bins**, crossing the full occupied range once. The deposit became 27.382474 USDC.

| Item | Observed |
| --- | --- |
| Position size and time | about $27.4; about 18 minutes |
| Fees earned | 0.009895 USDC (about 0.036%) plus 0.000000109 SOL |
| Network fees, three transactions | 0.000043988 SOL (about $0.005) |
| Net after network fees | about $0.005 |
| Position rent | 0.04189984 SOL, fully refunded at close |
| New USDC token-account rent | 0.00148844 SOL, kept in the account; recoverable only by closing that token account |

An apparent open amount of 0.25148844 SOL included the new token-account rent; the pool received exactly 0.25 SOL. Reconcile on-chain balances. This is one short crossing, not an annual percentage rate (APR) forecast. The token-account rent is a separate setup cost from the stated net fee result.

## 3. DLMM field guide

- **Bins and ranges:** A bin is one price level. `binStep` is the gap in basis points; 25 bps is 0.25%. Capital earns fees when swaps reach occupied bins. Tight ranges concentrate capital and exit sooner. Choose an exit rule for both edges.
- **Fees:** Bin step, base factor, and sometimes a base-fee power factor set the base fee. Volatility can add a variable fee. Read live rates and sustained volume; `getFeeInfo()` exposes base, protocol, and maximum fee rates. Gross fees are not net profit.
- **DLMM vs CLMM:** DLMM uses fixed-price bins and a shape per position. CLMM pools on Raydium and Orca use ticks and one even liquidity amount per position. Gateway's `/trading/clmm/*` routes serve Meteora DLMM; the route name does not mean a tick pool. See the [comparison](https://met.guide/guides/dlmm-vs-clmm.md). Meteora DAMM v2 also offers a pool-wide range. The pool creator sets it; LPs cannot set their own range. See the [DAMM v2 guide](https://met.guide/guides/meteora-damm-v2.md).
- **Shapes:** Spot spreads liquidity evenly across selected bins. Curve weights bins near the range middle. Bid-Ask weights bins near the edges. Stable pairs often use a narrow Spot range. Shape does not choose an exit or rebalance rule.
- **One-sided placement:** Put one token in bins on one side of the active price. Inventory converts when trades reach those bins. Turn off auto-fill for a strict one-sided position. Accept the asset you may hold after a range break. A base deposit fills bins at or above the active bin. Set the range bottom at the active bin to build an upward ladder. A quote deposit fills bins at or below the active bin. Set the range top at the active bin to build a downward ladder. In a 2026-10-15 test, a base range ending at the active bin filled only one bin. A bin price is a shared boundary. An exact boundary can make the position one bin wider than requested. Check the actual bin IDs after you open. Fees accrue in the token that swappers pay.
- **Token checks:** Compare Meteora's live fees with real volume; third-party totals can disagree. Check holder clusters, common funding sources, recent wallet creation, developer-wallet trades, and unlocks. Unusual volume candles add a warning. Tokleo screens pools; GMGN and Bubblemaps show holders; Streamflow shows unlocks. No tool proves safety. Check each pool mint for Token-2022 `TransferFeeConfig` before you deposit. Check whether a nonzero fee applies in the current epoch. Meteora's Dynamic Bonding Curve (DBC) 0.2.2 supports transfer fees on base and quote mints (2026-10-16 update). The fee reduces the tokens received on a transfer. Reject the pool or include the fee in output limits and profit and loss (PnL) calculations. A router may account for the fee; check your own limits against the amount received.
- **Range and timing:** Match width to volume and hold time; wide, low-fee positions can lose. The Friday/Saturday slow-cook loss finding is one trader's six-month sample; test it on your own net PnL.
- **Size and compound:** Start small. Raise size at a preset realized-net milestone; estimate exit slippage. Reinvest net gains after costs. A 20% loss needs a 25% gain to recover.
- **Same-range redeploy:** After a meaningful move, put all withdrawn SOL and half the token in bid-ask. Put the other half of the token in spot. Track both balances; wallet dashboards can misread this loop. One trader's method.
- **Position loop:** Inspect pool liquidity, bin step, fees, volume, and distribution. Pick range, shape, size, and exit rule. Open small. Monitor range, inventory, fees, and net PnL. Claim fees only when their value covers costs. Rebalance only when expected benefit exceeds network fees, swap fees, and slippage.
- **Risk:** Keep SOL for fees. Size positions so you can exit. A depeg, rug, wash volume, or crowded liquidity can erase fees. Compare realized PnL with holding the assets. No fees can mean low volume or out-of-range bins.
- **Stops:** DLMM positions have no native stop-loss or take-profit. A stop is a decision rule that a script executes. The script checks the price at fixed intervals. When the rule fires, close the position. Swap the received tokens if your exit rule requires it. Choose the check interval before you open. In one 2026-10-15 test, a five-minute check detected a fast price drop on its next run.
- **Cross-pool price gaps:** One recorded trade bought the SEALS token on PumpSwap and sold it into a Meteora DLMM pool in one transaction. Check other active pool prices before you open a tight new-token range. A price gap can draw a large swap through your bins.

Read the [beginner guide](https://met.guide/guides/meteora-dlmm-beginners-guide.md), [bin range guide](https://met.guide/guides/dlmm-bin-ranges-explained.md), and [fee guide](https://met.guide/guides/dlmm-fee-tiers-explained.md). See the [risk guide](https://met.guide/guides/lp-risk-il-rug-traps.md), [sizing guide](https://met.guide/guides/position-sizing-discipline.md), and [Hummingbot guide](https://met.guide/hummingbot).


## 4. Verified referral terms

Referral code: **UTT9PXJFGW** (`UTT9PXJFGW`). Referral URL: **https://app.meteora.ag/ref/UTT9PXJFGW** (`https://app.meteora.ag/ref/UTT9PXJFGW`). Open the URL, connect your wallet, and link the code on [Meteora's referral page](https://www.meteora.ag/referral) before opening eligible positions. This site may earn a referral commission.

The referred user gets a **2% kickback of protocol fees** taken from their own eligible LP positions. It is not 2% of deposits, trading volume, or gross LP fees. Rewards settle in USDC in monthly cycles and are claimed at `meteora.ag/referral`. Referred users share a pool capped at **20% of their referrer's earnings cap**. That cap scales with the referrer's staked MET. If the referrer unstakes mid-cycle, referred users forfeit pending rewards for that cycle.

At launch, eligible positions were **DLMM pools with SOL or USDC quote tokens**. Limit orders, DAMM v2 positions, and blacklisted wash-trading pools did not qualify. Meteora may change terms. Check the live referral page before relying on rewards. See [met.guide referral details](https://met.guide/referral).

## 5. Test record and source limits

**Local CLI test, 2026-10-09:** `solana-cli 4.2.2` wrote and read the isolated devnet config at `.solana-test/.config/solana/cli/config.yml`. Throwaway key creation, key selection, pubkey lookup, `cluster-version`, and `genesis-hash` worked. The cluster version was `4.4.0-beta.0`. `solana airdrop 1` hit the rate limit; balance was `0 SOL`. Passphrase-protected key generation failed without a TTY (`Unable to acquire passphrase: No such device or address`), including with piped input. The test key and config were deleted.

**Independent CLI re-test, 2026-10-09:** A fresh key with `solana -C <config.yml>` returned the same cluster version and `0 SOL`. It returned devnet genesis hash `EtWTRABZaYq6iMfeYKouRu166VU2xqa1wcaWoxPkrZBG` and a rate-limited airdrop. That key was deleted.

**Funded mainnet test, 2026-10-09:** Gateway 2.17.0 ran in Docker. The test imported a funded wallet, opened one position in the SOL/USDC bin-step-4 pool, collected fees, and closed it. All three transactions finalized without error. The position account no longer exists on-chain. An independent RPC review confirmed signatures, balances, costs, and closure; Gateway source checks confirmed the route schemas. Price **rose** through the SOL-side range. The measured amounts are in section 2.

**Documented, not run here:** the Hummingbot client, `gateway connect solana`, Gateway `add`, `remove`, `pool-info`, and `quote-liquidity`, devnet Gateway calls, and the SDK read example. The SDK repo and README were inspected; its dependency install was checked in a separate temporary directory.

**Operator tests, 2026-10-15 (funded, mainnet-beta):** a one-sided quote ladder filled bins at or below the active bin, with the range top at the active bin. A router swap with a raw integer amount failed simulation (Jupiter error 0x1788); the UI-amount form worked. A close succeeded, and an immediate balance read returned zero; later reads showed the tokens.

**2026-10-16:** a keyless Gateway 2.17.0 container logged `No Jupiter API key configured. Using lite-api.jup.ag`. A relayed Jupiter notice gave 2026-10-30 as the shutdown date (see the Jupiter API key section). Gateway source checks confirmed the keyed path; no keyed request ran.

## Guide index

All 19 guides, one line each:

Fetch `https://met.guide/guides/<slug>.md` for each full guide body. Use one file per guide. Do not scrape the HTML pages. Each file has a one- or two-sentence **Short answer** before the body. The file gives the publication and last review dates. A review without a text change does not change the guide's sitemap date. For a short map of the whole site, read https://met.guide/llms.txt.

- [Meteora DLMM Guide for Beginners](https://met.guide/guides/meteora-dlmm-beginners-guide.md)
- [Meteora Referral Kickback: The 2% Fee Program](https://met.guide/guides/referral-kickback.md)
- [Meteora Memecoin Pools: The Degen Fee/TVL Basket](https://met.guide/guides/memecoin-pools-degen-baskets.md)
- [The Heart Attack Strat: Tight Sub-10-Bin Scalps](https://met.guide/guides/heart-attack-strat.md)
- [Slow Cook: Multi-Day Positions on Older Tokens](https://met.guide/guides/slow-cook-positions.md)
- [Meteora Copy LP: How to Mirror a DLMM Wallet](https://met.guide/guides/copy-lp-meteora.md)
- [DLMM Rebalancing: What to Do When Out of Range](https://met.guide/guides/rebalancing-in-range.md)
- [Meteora LP PnL: Real Profit vs Dashboard Fees](https://met.guide/guides/lp-pnl-vs-dashboard.md)
- [Meteora LP Tools: Screeners, Alerts, Trackers](https://met.guide/guides/lp-toolstack-edge.md)
- [LP Risk: IL, Rug Risk, and Liquidity Traps](https://met.guide/guides/lp-risk-il-rug-traps.md)
- [LP Position Sizing: Unit Size and Scaling Rules](https://met.guide/guides/position-sizing-discipline.md)
- [DLMM Bin Ranges Explained](https://met.guide/guides/dlmm-bin-ranges-explained.md)
- [DLMM Fee Tiers Explained](https://met.guide/guides/dlmm-fee-tiers-explained.md)
- [DLMM vs CLMM: Which Solana Pool Type Fits You?](https://met.guide/guides/dlmm-vs-clmm.md)
- [Meteora DAMM v2: How It Differs from DLMM](https://met.guide/guides/meteora-damm-v2.md)
- [Meteora DBC Explained: Bonding Curve to DAMM v2](https://met.guide/guides/meteora-dbc-explained.md)
- [Stable Pair Strategies on Meteora](https://met.guide/guides/stable-pairs-meteora.md)
- [Why Is My Meteora Position Not Earning Fees?](https://met.guide/guides/position-not-earning-fees.md)
- [Meteora Volume Bots: What LPs Should Know](https://met.guide/guides/meteora-volume-bots.md)

[FAQ: short answers to common Meteora LP questions](https://met.guide/faq)

Glossary pages with worked definitions (`.md` bodies available): [Bin](https://met.guide/glossary/bin.md), [Impermanent loss](https://met.guide/glossary/impermanent-loss.md), [APR vs APY](https://met.guide/glossary/apr-vs-apy.md). The full reference desk is https://met.guide/glossary.

## Sources

[Solana CLI](https://solana.com/docs/intro/installation/dependencies#install-solana-cli), [Meteora docs](https://docs.meteora.ag/), [DLMM SDK](https://github.com/MeteoraAg/dlmm-sdk/tree/main/ts-client), [Hummingbot](https://hummingbot.org/exchanges/gateway/meteora/), [Gateway setup](https://hummingbot.org/gateway/installation/), [Gateway 2.17.0](https://hummingbot.org/release-notes/2.17.0/), [Jupiter API portal](https://developers.jup.ag/portal), [Jupiter rate limits and setup](https://developers.jup.ag/docs/portal/setup), [Solana Token-2022 transfer fees](https://www.solana-program.com/docs/token-2022/extensions#transfer-fees), [Raydium CLMM](https://docs.raydium.io/products/clmm/ticks-and-positions), [@0xMrBeefman — LP wallet analysis series](https://x.com/0xMrBeefman/status/2104183167754063916), [@Tuuxxdotsol — same-range redeploy strategy](https://x.com/Tuuxxdotsol/status/1991158752452489477), [SEALS cross-pool swap, 2026-10-13](https://solscan.io/tx/3aNkXnPAwGdJe6kzmwg3Cbv68vMV1ccsg6J2w9Ki7AaeSo1m81ZY615RvGHLLJSPwSovLX2gfL1896kUWMWbL39t).
