Reads every trade on a new curve. Net SOL flow, the number of unique wallets buying, and how much of the buying comes from the single largest buyer.
_____ ____ _____ _ _ ____ _ _ _____ ____ __ __ _ _ ____ _____ |_ _| _ \| ____| \ | |/ ___| | | | ____| _ \| \/ | | | / ___|| ____| | | | |_) | _| | \| | | | |_| | _| | |_) | |\/| | | | \___ \| _| | | | _ <| |___| |\ | |___| _ | |___| _ <| | | | |_| |___) | |___ |_| |_| \_\_____|_| \_|\____|_| |_|_____|_| \_\_| |_|\___/|____/|_____|
Muse The Trencher
TrencherMuse runs Muse, the personal AI agent Meta released in September 2026, as a trading bot for pump.fun tokens. Four collectors read every new launch on Solana and hand the results to Muse. Muse decides what to buy and sell, and every trade lands in a public wallet that anyone can follow on this page.
Every number on this page is either read straight from Solana or paced from rates measured on the live pump.fun stream. The collectors write to a terminal, the terminal feeds a text briefing, and the briefing is the only thing Muse gets to trade on.
30% of profits go to buybacks on the chart. 70% stay in the Muse wallet and compound the amount it trades with.
What the collectors read on every launch
Four collectors run against the live pump.fun program on Solana. Each one summarizes a different part of a new coin, and the summaries are what Muse gets to decide on.
Parses the name, ticker and metadata the moment a coin mints, pulls the image and links, and flags names that have already been launched earlier in the day.
Follows the creator wallet from the first block. Sizes the dev buy, records when the dev sells out, and counts wallets that buy in the same block as the mint.
Times every buy against the mint slot. Tags wallets that land within the first blocks and measures how large the fastest entries are.
Collector terminal
The combined output of the four collectors in the order it happens. Every line here is a real event on the pump.fun program, and this stream is the raw material the briefing below is built from.
Live scan of pump.fun launches
New coins appear as they mint. Each row fills in as trades arrive, and the status is set once all four collectors have read the coin.
| Token | CA | Age | MC | Vol, SOL | Flow | Collected | Status |
|---|
The briefing Muse reads
Every five seconds the page composes a short text briefing from the wallet state and the latest launches the collectors have finished reading. Muse gets this text, decides, and acts through its wallet.
composing…
The wallet Muse trades from
Balance, positions and profit are read from Solana transactions, not from anything Muse reports about itself.
not setPositions
pump.fun trades decoded from the walletTrades Muse has taken
Every pump.fun buy and sell signed by the Muse wallet, newest first, with a link to the transaction.
How it works
The setup has three parts: collecting data from the chain, letting Muse decide, and reading the result back from the chain.
Every launch is read from the pump.fun program
This page and the server hold a WebSocket to Solana public RPC and decode the create and trade events the pump.fun program emits. The four collectors summarize order flow, metadata, creator behaviour and entry timing for each new coin. Nothing here comes from a third-party trading API.
Muse decides with the summaries in front of it
Muse gets the collector summaries as its briefing and decides whether to buy, sell or pass. Muse has no trading API. It runs on its own virtual computer and acts through the wallet it was given, the same way it handles any other task in a browser. Position sizes are capped in the briefing.
Every trade is read back from Solana
The wallet balance, the positions and the profit shown above are decoded from the wallet's own transactions on chain. If Muse says it bought something and the chain does not show it, the chain wins. The wallet address is public so anyone can check it on Solscan.
Muse sizes its own trades
There is no fixed size per trade. Muse decides how much of the wallet to put into a coin from the briefing it gets, and every size is visible in the trades section, read from the chain. The sizing can be judged from the record rather than from a stated rule.