Meteora exchange profile

DLMM’s Dynamic Terminal combines TradingView charts, pool analytics, risk information and position management. It saves chart settings and annotations automatically. The documented terminal supports DLMM; DAMM v2 support is described as forthcoming, so a shared website should not be read as identical tooling across both products. The interface exposes partial withdrawals, claims, rebalancing and closing, alongside batch actions.[8]

Native DLMM limit orders place buy-side or sell-side liquidity in up to 50 bins per order account. They are available only in limit-order-enabled pools; a pool cannot simultaneously use the liquidity-mining mode. An order remains open until filled or cancelled, can fill partially, and requires swap flow through its selected bins. The program allocates 50% of the limit-order portion of trading fees to order participants; that is a share of fees, not a rebate on the full trade.[9]

A displayed price touching a target is insufficient evidence of execution. Check the order account and transaction result before replacing an order. Closing a browser session does not remove liquidity from an on-chain account; cancellation and any remaining asset claims require their own confirmed actions.[9]

Meteora has pool-specific economics rather than a single retail maker/taker tariff. A trader pays the configured swap charge; an LP receives only the share allocated to the liquidity that actually participates. Network fees, account rent, token transfer fees and any conversion are separate. A quoted annual return does not freeze any of those variables.[10]

For illustration, a 1,000 USDC fee-inclusive DLMM swap at a hypothetical 0.30% total rate produces a 3 USDC trading fee before integer rounding. With a standard market-maker-only 90/10 split, 2.70 USDC belongs to LPs and 0.30 USDC to the protocol. An eligible host’s 20% slice of the latter is 0.06 USDC; it is not another 20% charge on 1,000 USDC. This illustration excludes token transfer costs, price movement and network fees.[11]

Opening a DLMM position currently requires approximately 0.059 SOL refundable position rent, with extra rent for extensions. Creating a new bin array costs about 0.075 SOL, non-refundable. Review the live account-cost breakdown.[17]

Deposits that alter an already populated active bin can also incur a composition fee. Adding liquidity is therefore not always economically neutral.[11]

Removing liquidity crystallises its current token composition. A position started with two assets can finish heavily concentrated in the weaker one; the withdrawal button does not restore the original quantities or purchase value. To move proceeds elsewhere, wait for the removal and any conversion to confirm, then send the resulting token on its correct network. A bridge or a cash-out provider adds another service relationship and another quoted cost.[3]

Self-custody describes who controls the wallet key; it does not mean assets supplied to liquidity remain outside contracts. DLMM positions and DAMM pools are program-controlled records and token vaults. Their ownership rules, locks, token authorities and external dependencies matter as much as the wallet connection.[4]

The audit directory separates DLMM, DAMM, DBC, vault, staking and helper programs. An audit of one product or version should not be stretched across a different program or a later upgrade. The inspected documents do not establish a general insured reimbursement limit for trading losses, compromised wallets or liquidity positions.[27]

The protocol directs vulnerability reports to its OOO Security bounty program. A bounty compensates qualifying security research under its own scope; it is not customer balance insurance or a promise to repay an affected LP.[28]

The terms require legal capacity and exclude restricted persons by residence, citizenship, incorporation or registered office. Listed exclusions include the US, BVI, China, Russia, Cuba, Iran, North Korea, Syria, Myanmar, Iraq, Libya, Mali, Nicaragua, Somalia, Sudan, Yemen, Zimbabwe, Côte d’Ivoire, DR Congo, Crimea and Sevastopol, plus applicable sanctioned territories. VPN circumvention is prohibited. An accessible contract does not establish lawful eligibility.[29]

For stale data or an unreliable connection, the getting-started guide describes switching RPC provider, checking a blockchain explorer and reviewing the transaction broadcast mode. Jito submission depends on Jito-supporting validators. Check whether a transaction already landed before repeating it; a website timeout alone does not establish a failed withdrawal. No staffed emergency dealing desk or substitute telephone execution authority was established.[17]

Section 14 selects BVI law and BVI IAC arbitration in Road Town, Tortola, before one arbitrator in English. The notice address is [email protected]. The inspected terms provide no fixed complaint response deadline or mandatory preliminary negotiation clock; an ordinary ticket is not a published compensation procedure.[29]

The DLMM API exposes historical events for an individual position, including action and time filters with pagination. Preserve the position address, wallet address and transaction signatures, and reconcile claims, deposits, removals and transfers. These event records support accounting; they do not by themselves establish tax basis, a complete cross-wallet ledger or a jurisdiction-ready return. A native universal tax statement was not established.[30]

The MET MiCA whitepaper identifies Meteora Comet Limited, a BVI company numbered 2175599, as token issuer and technology provider, with Meteora Foundation as parent. That token disclosure does not establish a CASP licence for Meteora Nova Limited or a customer compensation scheme. Its stated seven-business-day response time belongs to the whitepaper contact; it should not be used as a general LP complaint deadline.[31]

Meteora’s website privacy policy, updated 28 April 2026, identifies Meteora Nova Limited as the website provider and operator. The public materials distinguish this role from Meteora Comet’s token issuance. Readers should use the entity and terms attached to the service concerned, rather than treating all names in the ecosystem as interchangeable counterparties.[32]

The H1 report supplies newer operating and fee information but does not establish a recovery of the reported OTC loss. DefiLlama indexes a 17 January 2026 social-engineering incident against the group. Those are different evidential statements: an incident classification and an operating report do not justify asserting either full recovery or continuing pool insolvency.[34][2]

Operator

Meteora Nova Limited, website provider

Exchange model

Decentralised

Service scope

Solana liquidity pools, swaps, launches and MET staking.

Client types

Not established

Pricing publication

Public pricing

Pricing scope

Pool-specific swap rates, protocol shares and transaction costs.

Funding scope

Solana token transfers and pool/vault redemption.

Custody and asset handling

User wallets; supplied liquidity is controlled by product programs.

Client eligibility

Territory and legal-capacity restrictions apply.

Support

Community tickets and contractual notices.

Authorisation and registration scope

Token whitepaper; exchange authorisation not established.

Exchange metadata checked 20 Oct 2026Source 1Source 32Source 29Source 4Source 17Source 11Source 35Source 31

The current Referral Staking FAQ describes a three-month campaign: at least 200 MET; staking shares 10% of DLMM protocol fees by time-weighted stake. Referrers receive 8%, referred users 2%, on eligible SOL/USDC-quoted DLMM positions; limit orders, DAMM v2 and blacklisted pools are excluded. A $1 cycle fee threshold applies. The referrer cap is 0.10 USDC per staked MET, each referee’s 25% of that; excess is forfeited. Referral linkage is permanent.[35]

Monthly-cycle rewards become claimable after cycle end, without an exact promised distribution time. Unstaking forfeits pending staking/referrer rewards and affected referees’ current-cycle rewards. Normal withdrawal waits seven days; immediate unstaking charges 10% of the unstaked MET. Falling below 200 MET also stops referred-user earnings. Pending rewards are estimates, not an immediately withdrawable cash balance.[35]

The DLMM data API publishes a 30-requests-per-second limit and endpoints for pools, orders, wallet portfolios, current positions and historical events. Indexed data can lag transaction-time state. A data endpoint is not authority to move a wallet’s funds; transaction builders, the signing wallet and any position delegate supply that authority. No exchange-account withdrawal whitelist is created merely by using the data API.[36]

Meteora’s Agent Skill can build integrations and run supported actions such as swaps, liquidity changes, limit-order cancellation and claims. Its CLI needs a funded signing environment; the documented workflow simulates first and requests confirmation before a real transaction. SDK builders produce unsigned transactions. Someone who supplies a signing key or broad operator authority gives the automation materially more power than a read-only research tool.[37]

The Documentation MCP serves protocol information and documentation search. It should be distinguished from an agent executing CLI commands with a signing key. Ending a chat or disabling a research connection does not itself close positions, cancel on-chain orders or remove delegated powers; each active permission and position needs its own lifecycle action.[38]