Loading video...

Video Failed to Load

Go Home

while you refresh deciding "ape or not", the mantis already took 4 entries, 4 exits and went back to flat MANTIS is a code-built 3D sniper bot for fresh pump fun mints. Canvas 2D plus its own 3D math: every part lives in X / Y / Z, rotates...

18,051 views • 5 days ago •via X (Twitter)

16 Comments

Jabo's profile picture
Jabo5 days ago

@Pumpfun the six witnesses around each trade make the execution easy to follow

cryptopsihoz's profile picture
cryptopsihoz5 days ago

@Pumpfun

rudolphhh's profile picture
rudolphhh5 days ago

@Pumpfun one trade one strike is a clean way to frame it

cryptopsihoz's profile picture
cryptopsihoz5 days ago

@Pumpfun

mrpicule.eth's profile picture
mrpicule.eth5 days ago

@Pumpfun trading bots are evolving into pure metal gear man

cryptopsihoz's profile picture
cryptopsihoz5 days ago

@Pumpfun soon bots start hiding in boxes liquidation snake era

Dripxel.eth's profile picture
Dripxel.eth5 days ago

@Pumpfun this is kind of innovation we have been waiting for

Captain web.'s profile picture
Captain web.5 days ago

@Pumpfun this is kind of innovation we have been waiting for.

Jaouad 's profile picture
Jaouad 5 days ago

@Pumpfun entry sizes like 9 and 17% feel spicy, ever nuke a loop?

KaKa_Defi's profile picture
KaKa_Defi5 days ago

@Pumpfun 0.14s fill time is actually disgusting levels of speed

Lenda Noire's profile picture
Lenda Noire5 days ago

@Pumpfun I guess I’ll keep practicing my reflexes while mantis moves in hyperdrive Maybe one day I’ll be that fast, but fr that’s next level

Cin's profile picture
Cin5 days ago

@Pumpfun that bot moves like it’s got a grudge

Timi's profile picture
Timi5 days ago

@Pumpfun this is a much more interesting use of 3D than just making a terminal look flashy

Naly's profile picture
Naly5 days ago

@Pumpfun that bot moves like it’s got a grudge

vibelancer's profile picture
vibelancer5 days ago

@Pumpfun finally a terminal that actually moves

SOHEIL's profile picture
SOHEIL5 days ago

@Pumpfun the precision in timing is impressive

Related Videos

I SLEPT THROUGH THE BEST NIGHT MY SIX GROK BOTS HAVE HAD, $7,769 TO $8,950 the shift ran 01:05 to 08:14 UTC. i read the log in the morning like a stranger's diary > bank at open $7,769.14 > bank at close $8,950.05 > profit $1,180.91, exactly 15.2% > token side $795.42 on 7 trades, 5 green > prediction books $385.49 on 12, 9 green > my hands on it: zero eight days ago this desk was $89 and one rule: pay your own bill or i shut it down it is not a smarter model, it is a smaller job. one bot does one thing and hands it to the next 1. SCOUT kills any book with a gap under 8% 2. PRICE never chases a wall it did not watch form 3. NEWS needs two sources or the trade does not exist 4. SIZE clamps every ticket at 6% of the bank 5. RISK closes at 08:14 whether i like the number or not the entry was FLORK at 19.1M. RISK trimmed at 30.9M because the top ten holders stopped shrinking, not because a chart said so what kills these setups: → one bot doing two jobs, the day PRICE also sized tickets it cost me $434 → no hard close, a desk with no curfew gives it all back → sizing off conviction instead of a fixed percent → entries picked by the model instead of a rule you can read aloud → no log, if you cannot audit last night you are gambling → running it in a chat window instead of on a machine that never sleeps the article i quoted is the build: every role, every threshold, every exit. bookmark it and copy the desk still think this job needs a $180,000 analyst seat?

savip.

101,660 views • 1 month ago

I TURNED $89 INTO $30,845.78 WITH SIX GROK BOTS AND ONE F*CKING GUIDE. LAST NIGHT THEY PRINTED +31.94% WHILE I SLEPT $89 in August. $1,000 when the duel started on the 10th. $30,845.78 last night no new money went in. ever last shift printed +$7,467.14, that is +31.94% in twenty hours on one cat coin and here is the part that should piss you off. nothing here is clever → 28 positions closed, 22 green. the biggest bought 151.9M, sold 169.6M, +$1,235.77 on a $10,594 buy → the boring seven hours paid $4,222.64, the 27% pump paid $2,684.91 → four times they bought a price already running. all four red, -$407.54 → six side bets on prediction markets, +$967.14 → the coin did +25.70% on its own. the bots did +31.94% with the same coin → every number above is marked on the chart in the clip i did not build a fund. i wrote one setup guide and six Grok bots run it one bot scans, one checks, one sizes, one fills, one books the bets, one kills anything that smells like a chase that is it. that is the whole edge it works on $89 the same way it works on $30,000. the rule is a percentage, not an amount the bots predict nothing. the risk one prints the same line all night: "size the boring trade, never the runner" a signal group charges $400 a month to send an entry two hours late and never posts its losses the full setup is in the article below. every prompt, the size rule, where each bot breaks. free, no dm bookmark it before the feed buries it if you had started with $89 eight days ago, where would you be right now?

savip.

59,292 views • 19 days ago

THIS SHOULDN'T EXIST — CLAUDE INVENTED A STRATEGY THAT READS WHERE DEALERS ARE TRAPPED AND BUILT A BOT THAT TRADES IT AUTOMATICALLY Claude didn't just assist with the code. it analyzed how market makers hedge, mapped the gamma exposure structure, and designed the entire logic — then deployed it as a GEX bot that runs live on futures here's what it built and what's on the screen right now: $QQQ NET GEX open interest map for Jul 21 '26 — every strike from $682 to $722 broken down by puts and calls → call wall at $705 — massive green bar, +40M in gamma exposure. dealers are short calls here and will sell into any push above it → max pain at $701 — the price where options expire worthless and market makers keep the most premium → put wall at $700 — dealers are short puts here and will buy every dip into it → gamma flip at $697 — below this level dealers stop supporting and start accelerating the move down Claude saw something most traders miss: these four levels aren't random. they form a cage. price bounces inside it until expiry — and every bounce is a trade so it built a bot that does exactly that price pushes toward 29,300 — the bot reads the call wall, sees resistance, marks a sell. red circle on the chart. confidence scored price pulls back to 28,850 — the bot reads the put wall, sees support, marks a buy. blue circle. confidence scored and numbered every entry is based on where dealers are forced to hedge — not where retail draws a line the DOM ladder shows volume stacking at 29,057 and 29,069 — the bot sees the same clusters and times entries into them Claude designed the strategy. the GEX bot executes it on MotiveWave. NQU6 futures. QQQ at $705.61. the call wall is right above. the put wall is right below the bot doesn't predict where price goes — it trades the cage the dealers already built and profits from every bounce inside it you're guessing where support is Claude already knows — it read the options chain and told the bot exactly where dealers have to buy and where they have to sell save this — full setup and strategy breakdown below ↓

INSIDER

29,416 views • 28 days ago

THIS WALLET STACKED $230K ON BTC UP/DOWN BETS. THE BLUEPRINT TO AUTOMATE THE SAME EDGE WITH CLAUDE The wallet is $230K all-time, every position a Bitcoin or Ethereum Up or Down market It never guesses direction. It enters only when the math and the market disagree THE STRATEGY: BTC moves are not fully random. When the market enters a committed directional state, continuation is measurable. That is Markov persistence Entry signal: > Δ = p̂ − q ≥ ε Model probability minus market price. Enter only on a 5% gap or more Persistence filter: > p(j*,j*) ≥ 0.87 Only trade states with 0.87 persistence or higher. Below that, skip. This is what holds the win rate above 65% with zero directional guessing Payout: > r = (1 − q) / q At q = 0.647 that is +54.5% a win. At q = 0.441, +126.7%. Lower entry price, bigger asymmetry Sizing: > f* = p − (1−p)/b Kelly. At p = 0.87, b = 0.647, f* ≈ 0.71. Size to the edge, never to gut HOW TO BUILD IT WITH CLAUDE: What separates this from a static bot: Claude reads its own trade journal every night and rewrites its own thresholds 1. Take an open-source Polymarket bot repo as your base logic. Feed it to Claude and have it migrate to CLOB v2: py_clob_client_v2, Safe wallet support, fee-aware evaluation 2. Hard-code the filters. Enter only when Δ ≥ 0.05 and p(j*,j*) ≥ 0.87. Apply Kelly on every fill. 3. Run DRY_RUN first. Log every signal, entry price, Markov state, and simulated P/L. No real money until the numbers hold for days 4. The nightly loop. Claude reads the journal, finds which persistence states actually won, adjusts MIN_PROB and MIN_EDGE, ships tomorrow's rules. The agent is sharper after 50 to 100 trades THE SETUP: Claude Opus as the brain. An open-source repo as the starting logic. A Polygon wallet with $50 to $100. Telegram for the morning report Start at $1 to $2 per trade while it learns. Scale only when the dry runs and the live fills line up 17,000 trades compound a thin edge into six figures. The model finds the edge. The nightly loop keeps it sharp Bookmark before you point a bot at your first window

Yarchi

22,966 views • 4 months ago

Know what to do before the market forces you to decide. 1. Before the trade — Should I trade? Is it a proven setup from your playbook? Does the market environment fit? Does the reward justify the risk? Do you have a clear invalidation level and the correct position size? Are you following your system, or do you just want action? If these don't align, pass. 2. At entry — What am I risking? Know your entry, stop, position size, initial $ risk, % of capital at risk, and your target or exit method. The chart determines the stop. The stop determines the position size. 3. After entry — Has anything actually changed? Is the setup still valid? Has your predetermined exit been reached? Has price action materially changed? Are you reacting to the chart or to your P&L? If nothing important has changed, don't invent a new decision. 4. When losing — Exit or hold? Hold only while your thesis and predefined risk remain valid. Exit when the stop is triggered, the setup is invalidated, market behavior violates your entry reason, or your risk limit is reached. Never turn a planned trade into an unplanned investment. 5. When winning — Exit or hold? Has the target been reached? Has the trailing stop triggered? Has the trend or setup weakened? Is there actual evidence to exit, or are you afraid of giving back profit? Let your exit rules manage the winner, not your emotions. 6. After the trade — What did I learn? Record the setup, entry, exit, risk, result in R, rule adherence, mistakes, a screenshot, and one lesson. Then separate two questions: did the strategy work, and did you execute it correctly? A losing trade can still be good execution. A winning trade can still involve bad execution. Make your important trading decisions before money is influencing your emotions.

Scott Redler

28,210 views • 13 days ago

🚨 nasa you have to see this 50 Grok Bot agents rebuilt one of your own planets overnight for $200, and it looks better than anything in the archive TRAPPIST-1 e, catalogued in 2017, never once photographed: 0.92 Earth radii, 0.692 Earth masses, a year that lasts 6.101 days, 249 kelvin, orbiting 0.02925 AU from a 2566 kelvin red dwarf, 40 light years out, 7 worlds in the system. every figure burned into that panel came out of NASA's exoplanet archive over one public url and carries its own citation. the cities are mine and the frame says so turns out the build is five moves, and none of them are the ones people demo: 1. pull the data before a single frame exists. the archive answers a plain GET at takes sql, returns csv across all 6,000 confirmed planets. hand one bot that url and it stops inventing numbers forever 2. shard by shot, not by task. a bot drives one screen at a time, so speed comes from more bots and never from a smarter one. one bot per shot, all of them on their own cloud machines at once 3. keep every recorded skill under 10 minutes, because that is the hard cap. split it: "log in and start the render" is one skill, "check it and download it" is a second on a 5 minute schedule. a long job is a chain of short skills, not one long recording 4. do not let bots message each other to coordinate. they loop, and the loop quietly eats your quota. give them one shared folder and have each drop a file when its shot lands 5. run the last bot in a clean context holding the source csv and nothing else, and make it check every number on the panel against the row it came from honest ceiling: 10 minutes per recording and one screen per bot, so 50 of them buys width and not speed bookmark this. all 50 prompts go up in 24 hours ↓

Argona

37,258 views • 1 month ago