Solana: Listen to pump.fun mints via logsSubscribe

• This script captures newly created pump.fun tokens by subscribing solely to program logs (logsSubscribe).
• On seeing the “Create” instruction, it decodes the token name, symbol, URI, mint address, bonding curve address, and user, then computes the associated bonding curve address.
• This eliminates the need for extra RPC calls (like blockSubscribe or getTransaction), giving real-time data to enable fast sniping of newly minted tokens.
• Compare it with blockSubscribe in separate scripts to see which offers quicker event detection in your setup.

​

Main article

• blockSubscribe — extracts and decodes transactions as the are streamed in the blocks produced. And the script in the bot decodes them on the fly. This means that we get all the necessary data to do our sniping using the blockSubscribe method.
• logsSubscribe — only prints the pump.fun program logs, in our case—for token mints. The problem is we can get and decode from the logs the new token’s name, symbol, mint address, user (creator), and bonding curve address. But the logs do not contain the associated bonding curve address, which we need to do a sniping/buying transaction.

​

How it works

• The script subscribes to Solana logs mentioning the pump.fun program (PUMP_PROGRAM).
• Whenever the program logs an Instruction: Create event, the script looks at the Program data: line in the logs.
• It decodes the data on-the-fly and extracts:
  • The token name
  • The token symbol
  • The token URI
  • The token mint address
  • The bonding curve address
  • The user (creator) address
• It then computes the associated bonding curve address (similar to how an associated token account is derived) via Pubkey.find_program_address().

​

Prerequisites

1. A Solana WebSocket endpoint (e.g., from Chainstack).
2. Python 3.11+ with the dependencies installed through uv:
   Shell

   uv sync
   
3. A .env file in the repository root that includes your WebSocket endpoint as SOLANA_NODE_WSS_ENDPOINT.

​

Usage

1. Run:
   Bash

   uv run cookbook/pumpfun/listen/pumpfun_listen_tokens_logsubscribe.py
   
2. Watch the console for output like this:
   text

   Listening for new token creations from program: 6EF8rrecthR5...
   Subscription response: {"jsonrpc":"2.0","result":{"subscription":...}}
   
   Signature: 5TYqzsc...
   name: MyToken
   symbol: MYTK
   uri: https://arweave.net/...
   mint: 8cYMHFE...
   bondingCurve: 6GUb...
   user: Hwz3...
   Associated Bonding Curve: 5YvN...
   ##########################################################################################
   

​

Script overview

1. Subscribe to logs Uses logsSubscribe to monitor logs referencing the pump.fun program ID.
2. Look for “Program log: Instruction: Create” When that shows in the logs, the script checks subsequent logs for Program data: lines.
3. Decode and parse The script decodes the base64-encoded Program data: and extracts:
   • name (token name)
   • symbol (token symbol)
   • uri (metadata URI)
   • mint (the newly minted token address)
   • bondingCurve (the bonding curve address)
   • user (the token creator)
   It then calculates the associated bonding curve address via:
   Python

   derived_address, _ = Pubkey.find_program_address(
       [
           bytes(bonding_curve),
           bytes(TOKEN_PROGRAM_ID),
           bytes(mint),
       ],
       ATA_PROGRAM_ID
   )
   
4. Print details Outputs the transaction signature, plus the fields noted above, along with the computed associated bonding curve.

​

Compare performance

uv run tools/compare_listeners.py

​

Next steps

• Integrate this script’s output into your buy/sell logic to snipe tokens right as they are created.
• Optionally use a separate script or your own logic to monitor the token price (via the bonding curve) to decide when to buy or sell.

Ake

Director of Developer Experience @ Chainstack
Talk to me all things Web3
20 years in technology | 8+ years in Web3 full time years experience