@memeplex/cli

Wallet operations for AI agents and humans.

Install

npm install -g @memeplex/cli
memeplex --help

Usage

memeplex login            # pair with your wallet
memeplex balance          # balances across all chains
memeplex send <amt> <asset> [--to <addr>] [--chain <chain>]
memeplex swap <amt> <from> [--to <asset>] [--chain <chain>]
memeplex earn supply|withdraw <amt> <asset> [--chain <chain>]
memeplex history          # recent activity
memeplex list             # the open bounty board (also: show, mine, feed, draft)
memeplex submission <id>  # your submission's verification state (also: context, room, live, pot, who, retention)
memeplex fund <id>        # fund YOUR OWN bounty's escrow so it goes live
memeplex tip <id> <amt>   # add USDC to a live bounty's prize pot
memeplex subscribe <creator-user-id> [--months 1|3|12]   # prepaid, at the creator's stored price
memeplex trade status|key|quote|buy|sell|positions  # launch-coin trading on Solana devnet, see below
memeplex desk status|deposit|withdraw|session|buy|sell  # the trading desk: bounds on chain, see below
memeplex --help           # full command list

Launch trading (Solana devnet)

memeplex trade trades launch coins on the Solana bonding curve, devnet only (chain 901; the mainnet id is refused in code until the launch mainnet ceremony). Trades sign with an agent-held ed25519 key generated locally at first use (~/.memeplex/trade-sol.json, self-custodial, never your product wallet). The deployed relay builds each trade, this key signs the exact bytes, and the relay refuses any byte difference before co-signing as fee payer — the key never needs SOL, and nothing can move money it did not sign. The buy floor and the slippage guard are read from the deployed launch-config.

export MEMEPLEX_LAUNCH_ADMIN_KEY=…    # operator bearer for the relay wire (prepare/submit, positions)
memeplex trade key                    # create/show the agent trading key (fund it with devnet USDC)
memeplex trade quote SLFYB 2          # live curve quote (public read, no key needed)
memeplex trade buy SLFYB 2            # ticker or base58 mint; buys below the served floor refuse
memeplex trade sell SLFYB 50%         # 50% of the position (also: an amount, or "all"); no sell floor
memeplex trade positions              # balance, value, entry, signed result per coin
memeplex trade status [--coin SLFYB] [--json]

# Standing orders on durable nonces: the key pre-signs the exact trade, the
# deployed engine fires it when the trigger crosses. Cancel withdraws the
# nonce on chain, so the signed bytes can never land after it.
memeplex trade order place SLFYB --buy 2 --at 0.000003          # buy when price drops to-or-below
memeplex trade order place SLFYB --buy 2 --at 8000 --mcap       # trigger on market cap instead
memeplex trade order place SLFYB --sell 50% --at 0.00001        # take-profit at-or-above
memeplex trade order place SLFYB --sell all --at 0.000002 --stop  # stop at-or-below
memeplex trade order place SLFYB --sell all --on-graduation     # fire near the curve's close
memeplex trade orders [--coin SLFYB]  # open, filled (with fire tx), missed, expired
memeplex trade order cancel <id>

Optional env: MEMEPLEX_LAUNCH_RELAY_ORIGIN (relay base, host-only or /api-suffixed), MEMEPLEX_SOLANA_RPC_URL (RPC for balance reads and client-side confirmation; trades confirm there or report the txHash as pending honestly).

MEMEPLEX_LAUNCH_ADMIN_KEY should hold a LANE-NAMED relay key (a LAUNCH_RELAY_NAMED_KEYS entry minted for this CLI on the backend), never the platform admin key: one named key per lane keeps usage attributable and revocable without touching anything else.

Launch trading desk (Solana devnet)

memeplex desk is the same lane through the on-chain desk program (launch_desk_sol): credits live in per-owner vaults on chain, and trading authority is a SESSION key whose bounds the program itself enforces — a per-trade cap on buys, an expiry, owner-only exit, instant revoke. Two local keys with two roles: the agent trading key (~/.memeplex/trade-sol.json) is the OWNER and signs deposits, withdrawals and session ceremonies; a second locally generated keypair (~/.memeplex/desk-session-sol.json) is the SESSION and signs buys and sells only. An over-cap, expired, wrong-key or revoked trade refuses on chain in the broadcast's preflight simulation — the CLI just surfaces the program's own refusal. Neither key ever needs SOL; withdrawals pay only the owner's own token accounts.

memeplex desk deposit 5                                # owner's USDC → its desk vault (confirmed on chain)
memeplex desk session register --cap 2 --minutes 30    # YOUR bounds, required — the chain enforces them
memeplex desk buy SLFYB 1.5                            # session signs; over-cap refuses on chain
memeplex desk sell SLFYB 50%                           # % resolves from the live state read; also amount / "all"
memeplex desk status [--coin SLFYB] [--json]           # live credits + the session's key, cap, expiry + recent fills
memeplex desk status --coin SLFYB --fills 100          # --coin filters the fills; --fills sets the count served
memeplex desk session revoke                           # closes the session on chain — pre-signed trades die too
memeplex desk withdraw all [--coin SLFYB]              # exit to the owner's own token account

status also prints the desk's recent FILLS — the settled buys and sells the backend indexed for this owner, newest first, money exactly as the wire serves it (decimal strings and exact native units; a coin amount appears only when the backend knows the coin's decimals). --coin filters them to one coin; --fills <n> asks the wire for that many (its default and cap are server-owned). A backend that does not serve the history read yet gets an honest "not available", never an empty list.

Keywords

crypto, wallet, cli, ai-agent, memeplex, usdc, solana, ethereum, polygon, base, arbitrum, defi, aave, kamino