From e6236a9a86454d13be8138a36b45d2d1b201ab81 Mon Sep 17 00:00:00 2001
From: Anton <43762166+smypmsa@users.noreply.github.com>
Date: Wed, 19 Mar 2025 08:13:07 +0100
Subject: [PATCH] docs: update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 9c501bb..38e4048 100644
--- a/README.md
+++ b/README.md
@@ -26,8 +26,8 @@ Overall, it'll be a gradual development & rollout:
   * Ability to set RPS in the config to match your provider's and plan RPS (preferably [Chainstack](https://console.chainstack.com/) 🤩)
   * ✅ 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
+  * ✅ 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