TxWhy

Error codes / Meteora Dynamic Bonding Curve

PoolIsCompleted

Meteora Dynamic Bonding Curve · Custom(6013) · 0x177d

custom program error: 0x177d

What it means

The launch pool has completed its bonding curve and graduated. Its liquidity has moved, or is moving, to the AMM pool it migrates to, so no swap against the launch pool can succeed any more.

The program's own message: “Pool is completed”

What to do

Trade the token on the pool it migrated to (Meteora DAMM v2 for DBC launches), directly or through Jupiter. Paste the failed transaction into TxWhy to get that pool's address.

Seen on mainnet

The curve graduated. Its liquidity moved to a Meteora DAMM v2 pool, which TxWhy derives from the pool's config and migration fee option and names in the answer. Trade there; nothing against the curve can succeed any more.

From replaying real landed failures through the repair engine, around the clock since September 21, 2026. Every verdict and its reason is on the failure index.

Have the transaction that failed with this?

Paste its signature. TxWhy shows the exact instruction and inner call that raised the error, and rebuilds the transaction when the cause is one it can fix (compute limit, expired blockhash, priority fee, a stale swap quote or a moved limit).

Code 6013 means something else in other programs

Custom codes are private to each program. Check which program actually raised it: it is the innermost failed call, not necessarily the program you called.