>>WARNNING ON SCAMS IN ISSUES COMMENT SECTION<<

The issues comment section is often targeted by scam bots willing to redirect you to an external resource and drain your funds.

I have enabled a GitHub actions script to detect the common patterns and tag them, which obviously is not 100% accurate.

This is also why you will see deleted comments in the issues—I only delete the scam bot comments targeting your private keys.

The official maintainers are in the MAINTAINERS.md file.

Not everyone is a scammer though, sometimes there are helpful outside devs who comment and I absolutely appreciate it.

>>END OF WARNING<<

>> FURTHER ROADMAP <<

Hey guys, starting from the next week (week of March 10) we'll be rolling out updates to the bot v2 based on the feedback and the reported issues, including updating to the latest libs, better error handling etc. We are already actively working on it.

That'll be in a separate branch.

Overall, it'll be a gradual development & rollout:

• Stage 1: General updates & QoL
  • Lib updates
  • Error handling
  • Ability to set RPS in the config to match your provider's and plan RPS (preferably Chainstack 🤩)
  • Ability to set dynamic priority fees
• Stage 2: Bonding curve and migration management
  • Integrate logsSubscribe instead of blockSubscribe for sniping minted tokens into the main bot (currently it's separate in the learning examples section that you can integrate yourself)
  • Keep both logsSubscribe & blockSubscribe in the main bot — so that you can try out/choose which one works best for you — plus the Solana node architecture and provders change, so it's useful to have both
  • Do retries instead of cooldown and/or keep the cooldown
  • Checking a bonding curve status progress. As in to predict how soon a token will start the migration process.
  • Script to close the associated bonding curve account if the rest of the flow txs fails
  • Add listening to Raydium migration (and try and figure out the logSubscribe way for it as well) — still not sure if I can FAFO this one out, but had some progress in the past
• Stage 3: Trading experience
  • Take profit, stop loss
  • Sell when a specific market cap has been reached
  • Copy trading
  • Script for basic token analysis (market cap, creator investment, liquidity, token age) + being to go back with Solana archive nodes (e.g. accounts that consistently print token, average mint to raydium time for winning printing accounts and so on)
• Stage 4: Minting experience
  • Ability to mint tokens? (there is a request and there was someone who minted 18k tokens)
• Bonus: Vector.fun
  • There's a lot of pump.fun tokens on vector.fun but I didn't investigate yet if there's anything we can do with it.

Note that the stage progression is from simple to more complex and we don't guarantee everything as move from Stage 1 to the rest.

And we appreciate all your feedback and we'll keep you posted!

>> END OF ROADMPAP <<

For the full walkthrough, see Solana: Creating a trading and sniping pump.fun bot.

For near-instantaneous transaction propagation, you can use the Chainstack Solana Trader nodes.

Sign up with Chainstack.

Make sure you have the required packages installed pip install -r requirements.txt.

Make sure you have your endpoints set up in config.py.

Note on limits

Solana is an amazing piece of web3 architecture, but it's also very complex to maintain.

Chainstack is daily (literally, including weekends) working on optimizing our Solana infrastructure to make it the best in the industry.

That said, all node providers have their own setup recommendations & limits, like method availability, requests per second (RPS), free and paid plan specific limitations and so on.

So please make sure you consult the docs of the node provider you are going to use for the bot here. And obviously the public RPC nodes won't work for the heavier use case scenarios like this bot.

For Chainstack, all of the details and limits you need to be aware of are consolidated here: Limits <— we are always keeping this piece up to date so you can rely on it.

Changelog

Quick note on a couple on a few new scripts in /learning-examples:

(this is basically a changelog now)

Also, here's a quick doc: Listening to pump.fun migrations to Raydium

Bonding curve state check

check_boding_curve_status.py — checks the state of the bonding curve associated with a token. When the bonding curve state is completed, the token is migrated to Raydium.

To run:

python check_boding_curve_status.py TOKEN_ADDRESS

Listening to the Raydium migration

When the bonding curve state completes, the liquidity and the token graduate to Raydium.

listen_to_raydium_migration.py — listens to the migration events of the tokens from pump_fun to Raydium and prints the signature of the migration, the token address, and the liquidity pool address on Raydium.

Note that it's using the blockSubscribe method that not all providers support, but Chainstack does and I (although obviously biased) found it pretty reliable.

To run:

python listen_to_raydium_migration.py

The following two new additions are based on this question associatedBondingCurve #26

You can take the compute the associatedBondingCurve address following the Solana docs PDA description logic. Take the following as input as seed (order seems to matter):

• bondingCurve address
• the Solana system token program address: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA
• the token mint address

And compute against the Solana system associated token account program address: ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL.

The implications of this are kinda huge:

• you can now use logsSubscribe to snipe the tokens and you are not limited to the blockSubscribe method
• see which one is faster
• not every provider supports blockSubscribe on lower tier plans or at all, but everyone supports logsSubscribe

The following script showcase the implementation.

Compute associated bonding curve

compute_associated_bonding_curve.py — computes the associated bonding curve for a given token.

To run:

python compute_associated_bonding_curve.py and then enter the token mint address.

Listen to new direct full details

listen_new_direct_full_details.py — listens to the new direct full details events and prints the signature, the token address, the user, the bonding curve address, and the associated bonding curve address using just the logsSubscribe method. Basically everything you need for sniping using just logsSubscribe and no extra calls like doing getTransaction to get the missing data. It's just computed on the fly now.

To run:

python listen_new_direct_full_details.py

So now you can run listen_create_from_blocksubscribe.py and listen_new_direct_full_details.py at the same time and see which one is faster.

Also here's a doc on this: Solana: Listening to pump.fun token mint using only logsSubscribe