bnbxcs/TMTN

TMTN is a single-user, localhost trading terminal for the BSC "agent-only" meme launchpads Flap Agent, Four.meme and gang.fun. It is aimed at traders who already use Binance's Agentic Wallet and want a trenches-style view and fast buy/sell panel without handing their private key to a website. Its author states plainly that it trades real funds and is unaudited, so treat the simulation mode as the default way to evaluate it.

The problem

Watching an agent-only launchpad usually means juggling a launchpad page, a chart, a trade feed and a wallet, then copying amounts between them while a new token moves. TMTN puts discovery, the chart, the live trade feed and a one-click buy/sell panel into one browser page served from your own machine. The signing step is delegated to Binance's Agentic Wallet CLI, so the click you make in the page becomes an on-chain order without the project storing a private key. The result is a faster loop between spotting a token and placing a small order, with positions and realized/unrealized PnL kept in the same view.

What's different

The design decision that shapes everything is that signing goes through baw, Binance's Agentic Wallet CLI, rather than a locally stored key. In live mode the server polls wallet status every 10 seconds and blocks fund-moving endpoints with a 401 when the wallet is not signed in; the page shows an overlay pointing you back to baw auth signin project instructions. The interface is explicitly GMGN-style: three columns for new, about-to-launch and migrated tokens, per-column filters, keyword and block lists, a trader PnL drawer, and a floating preset buy/sell panel.

The trade-off is that speed is bought with approvals and background dependencies. Selling and quote-currency buys pre-approve a larger fixed allowance than the current trade (not unlimited), which can be disabled or revoked in the approval manager, but a problematic approved contract could then move more of your tokens. Turning on the optional MySQL + Redis cache cache setup makes history and large-pool rescans cheaper, but adds infrastructure that the default path does not need. A private RPC key such as NodeReal is optional but recommended for scanning and subscribing to new pools; without it the public nodes are used as fallback.

Who should try it

A good fit is an active BSC meme trader who already has a Binance Agentic Wallet with an .ai Agent ID, developer mode enabled and some BNB for gas, and who wants a local trenches view with manual clicks as the final trigger. A poor fit is anyone who wants a hosted, multi-user service, or who is not prepared to run a Node server and keep a wallet CLI logged in; the local page has no authentication at all, so anyone who can reach the port can place orders with your wallet.

The README also documents running several wallets at once: wallet 1 on the host and additional wallets in Docker containers with a fixed MAC address and their own login multi-wallet guide. That path suits someone deliberately splitting trades across accounts, but it also means each extra backend must be updated separately.

Requirements and limitations

You need macOS or Linux with Node.js 18+ and a browser; live trading additionally requires the Agentic Wallet CLI and a signed-in wallet. Trading Four.meme's agent-exclusive template needs the Binance skill script installed through npx skills add. The service listens only on 127.0.0.1 and has no authentication: exposing it through a port forward or reverse proxy would let anyone use your wallet to trade. The project is unaudited, and the author warns that price conversion, precision, approvals and routing may contain bugs; simulation mode and small amounts are the stated first step.

Upkeep matters more than setup here. Third-party launchpad APIs can change or break, since the project is unaffiliated with Binance, Flap, four.meme or gang.fun. The built-in version manager replaces only code, backs up to data/updates/ and can be disabled, but it does not run under Docker or npm run dev, and other wallet backends need separate updates. With multiple wallets, Binance identifies devices by MAC address, so same-machine logins displace each other; the container approach is the documented workaround.

HotRepo's take

TMTN was created on 2026-10-25 and had 105 total stars when it appeared at #25 on HotRepo's NEW-REPOSITORY board for JavaScript on 2026-10-27 — a new-project ranking, not a daily gain figure project page. HotRepo has only one recorded board date, so persistence of interest cannot be judged from that snapshot. Before trusting a live run, check the README's warnings against the pre-approval setting and verify that revocation works for the tokens you actually trade.