$GLOW just launched on pump.fun. Dev holds 2%, low cap, early.
7xwA2FDENLEPW41zpPKKXn8ZoSXC9Ljjbezb9gGvpump
X & Telegram
Name up to 50 X accounts and 25 Telegram channels and groups. Each new post reaches your bot over one socket, seconds after it is posted, and Telegram posts come with their token addresses already picked out. Hand the mint to Lightspeed and the buy goes out in one request.
On Professional: 50 X accounts and 25 chats per server, on 5 sockets.
$GLOW just launched on pump.fun. Dev holds 2%, low cap, early.
7xwA2FDENLEPW41zpPKKXn8ZoSXC9Ljjbezb9gGvpump
New call: $GLOW
CA: 7xwA2FDENLEPW41zpPKKXn8ZoSXC9Ljjbezb9gGvpump
Entry under 20k, size small.
01From post to buy
Only the first step happens on X's or Telegram's side, and how long it takes varies by account and by moment. Everything after the post arrives should take milliseconds.
An account you follow posts on X, or a call goes up in a Telegram channel or group you follow.
X or TelegramOur stream servers in the US, Europe and Asia send it, as a tweet or telegram event, to every socket that follows it.
Telegram posts carry theirs in addresses.solana. On X, the guide's bot reads the text, and where its t.co links point when the text has none.
Lightspeed builds, signs and sends the buy from a wallet only your API key opens, raced over all 8 SWQoS lanes and the block 0 lane.
~50 ms02The streams
Both come from the same stream servers on your Professional key, and one socket can follow both. The limits count what your key follows over all its sockets on a server, with 5 sockets shared by both streams.
Up to 50 accounts
subscribe_tweets follows X accounts by handle, and each new post comes as a tweet event.
id, author and urlid, kind, user, name, text, url, postedAt and receivedAtUp to 25 chats
subscribe_telegram follows channels and groups, and each new post comes as a telegram event, with the token addresses already picked out.
addresses: Solana mints and EVM 0x addresses, from the text and its links, the ones behind link text tooid and editedAt set03Snipe with Lightspeed
Take the mint from the post and hand it to Lightspeed, with nothing looked up on the way. The whole bots are in the X sniper and Telegram sniper guides.
import { io } from "socket.io-client";
// YOUR_STREAM_SERVER: a server's address from your dashboard
const socket = io("https://YOUR_STREAM_SERVER", {
auth: { api_key: "sk_…" }, // your Professional plan's key
});
// Follows belong to the socket: send them again after every (re)connect.
socket.on("connect", () => {
socket.emit("subscribe_telegram", {
chats: ["@solana_calls", "https://t.me/+AbCdEf123456"],
});
});
const seen = new Set(); // every mint already bought or tried
socket.on("telegram", async (p) => {
const mint = p.addresses.solana
.find((m) => !seen.has(m) && m.endsWith("pump"));
if (!mint) return;
// before the request: a repost cannot buy it again
seen.add(mint);
await fetch("https://sol.shrine.trade/api/lightspeed", {
method: "POST",
headers: {
"content-type": "application/json",
"x-api-key": "ls_…", // your Lightspeed account key
},
body: JSON.stringify({
action: "buy", mint, amount: 0.05, slippage: 25,
priorityFee: 0.0002, tip: 0.001,
providers: ["all"], // every lane and the block 0 lane
}),
});
});
subscribe_tweets adds X accounts on the same socket.addresses.solana holds the post's mints in the order they appear, from the text and its links. For X, the guide's bot finds the mint in the text and its t.co links.seen before the request leaves, so the same call posted again buys nothing.04Plans
Included in
The X and Telegram streams come with Professional, with everything Developer has at the highest limits. Posts don't count against any other limit.
Every limit, endpoint by endpoint, is in Plans and limits. Prices are on the pricing page.
No. The streams follow the accounts and chats for you: no X account, no X API key and no scraping on your side, and no Telegram account, api_id or session file to guard. You need a Professional plan's key and a stream server's address, both on your dashboard.
Seconds after it is posted. Each post carries postedAt and receivedAt in milliseconds, so receivedAt - postedAt is the delay, post by post. On X, how long a post takes to reach the stream is decided on X's side, and it varies by account and by moment.
Yes, by an invite link that doesn't need an admin's approval, such as https://t.me/+AbCdEf123456. Following a private chat by its invite link adds a member through that link, which the chat's admins can see. People, bots and t.me/c/… links can't be followed.
On each server, your key may follow 50 X accounts and 25 Telegram chats at once, counted across all its sockets there, with 5 sockets shared by both streams. It may also add 100 new X accounts and 25 new chats a day on each server; accounts and chats already in use on that server don't count.
A followed account's own posts always come, quote posts among them; its replies don't. Its reposts come only if you switch them on for that account, with reposts: true.
The X and Telegram streams come with Professional, on one key.