正在加载视频...

视频加载失败

I BUILT A BOT THAT PREDICTS NBA GAMES BEFORE TIPOFF. IT RUNS EVERY DAY AT 5:00 PM. HERE'S WHAT'S INSIDE. Three data sources. Three probability layers. One automated pipeline. No manual input. Every evening the bot wakes up. Pulls today's NBA slate. Builds features from live data.Generates predictions. Sends...

48,649 次观看 • 5 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

A guy running quant models for a tennis betting syndicate DM'd me last month. "We spend $40K/month on data feeds. What are you using?" A webcam pointed at a tennis stream. Not metaphorically.YOLO tracks both players and the ball 30fps. A second model maps the court to real meters. Every 5 seconds I get three numbers: aggression positioning, court coverage, rally intensity. Those feed into a Bayesian engine. Beta prior on serve probability, updated every game, 15,000 Monte Carlo sims sampling from the posterior. Not point estimates - distributions with confidence intervals. 62% +/- 3% is a trade. 62% +/- 18% is noise. Most people never compute the interval. "Okay but models are wrong" That's why the model is only layer two out of five Layer three connects Polymarket and a bookmaker simultaneously. When my model says 71%, Polymarket says 62%, bookmaker says 67% - something is mispriced. Layer four is the unfair one. Claude reads every press conference transcript, news article, and social post from the last 48 hours. Extracts structured signals - injury flags, form deltas, surface comfort. JSON, not vibes. A player mentioned shoulder tightness at a presser. Claude flagged injury probability 0.25. Bookmaker didn't adjust for 3 hours. Polymarket never did. I was already in Layer five compares all four sources and finds the edge. Value, arbitrage, fade, or intel override when Claude catches something critical. "What's your hit rate" 2,400 ATP matches backtested. Model alone: 61%. With market bridge: 67%. With Claude: 72% Live 11 weeks: 247 contracts, 178 winners, +$14,200 from $1,800 He went quiet then wrote "my syndicate is rethinking our entire pipeline. We've been doing this 6 years and never used CV on live streams" They spend $40K/month. My setup: a Claude subscription and an API key Bot:

zostaff

55,452 次观看 • 5 个月前

9 repos that mass replace a $150,000/year NBA analytics department. all free. all open source. -> replaces Second Spectrum and SportVU YOLO tracks every player and ball from any broadcast. assigns teams by jersey color. court keypoint detection builds a tactical top-down map. speed, distance, passes - all from a TV feed. no sensors. -> replaces paid NBA prediction services ($100/mo) XGBoost + Neural Net. moneyline and totals. Kelly Criterion sizing. 69% accuracy. pulls odds from FanDuel/DraftKings automatically. the most starred NBA betting repo on GitHub. -> replaces an entire quant sports desk 5-model ensemble: XGBoost + PyTorch MLP + Ridge + Lasso + baseline. Optuna-tuned hyperparameters. SQLite database with box scores, play-by-play, betting lines, injury reports. production-grade. -> replaces manual daily prediction workflows XGBoost/LightGBM with GitHub Actions automation. scrapes new data, retrains models, outputs daily win probabilities. set it and forget it. -> replaces ELO subscription services custom ELO + Ridge + XGBoost + Neural Networks ensemble. full data scraping pipeline. comprehensive visualizations. FiveThirtyEight-style ratings from scratch. -> replaces Four Factors analytics dashboards ELO rating system + Four Factors + PCA dimensionality reduction. detailed comparison of 10+ models. honest 65.3% accuracy - because that's what real NBA prediction looks like. -> replaces computer vision analytics platforms ($500/mo) YOLO player/ball tracking. automatic team assignment. court keypoints. pass and interception detection. speed and distance. full tactical view. modular architecture. -> replaces shot tracking hardware YOLOv8 detects ball and hoop in real-time. linear regression predicts trajectory. registers makes and misses automatically. works on any video feed. -> replaces paid sports data subscriptions ($300/mo) official Python client for NBA. com API. box scores, play-by-play, shot charts, player tracking. 40+ years of data. zero cost. the foundation every NBA ML project is built on. like + bookmark you'll need this when you build your first NBA prediction bot

zostaff

103,649 次观看 • 4 个月前

An OpenAI researcher sat down next to me at a coffee shop in Mission District I had my terminal open. Three panels. Live trades scrolling. He was reading something on his laptop. Glanced over. Stopped reading. "That's not a dashboard. That's a live scoring engine. What model is running that" I told him. Claude Code. Four repos. $25 a month. He closed his laptop. "I work at OpenAI. We benchmarked Claude internally last month. You're using it to trade prediction markets?" I opened one link. 86 million trades. Every wallet. Every entry. Every exit. The entire Polymarket history since day one. "This is public? We quoted a seven-figure budget to reconstruct this kind of dataset from on-chain data. The project is still in review" I told him Claude Code connects directly. It reads the whole dataset. Finds the wallets that win. Then finds WHY they win. Then copies the pattern. He pulled his chair closer. "Walk me through the exit logic" Top wallets exit before resolution 91% of the time. They capture 86% of the move and cut losers at 12%. Everyone else holds to 58%. Same entries. Completely different exits. My bot cuts at 85% of expected move. Or on a 3x volume spike. Whichever hits first. "Who gave you that threshold" Claude Code found it in poly_data. In about 20 minutes. "We had a team of nine working on this exact problem for six months. They never shipped it. You did it in a weekend with a competitor's model" I opened another link. Three commands. 500+ markets. No API key. Claude scores them in 20 minutes. "That's our internal eval pipeline. Except it took us six months and you built it on a Saturday" My setup: Claude API - $20/mo VPS - $5/mo poly_data - free polymarket-cli - free 19 days. 4 agents. 74% win rate. +$9,400. Copytrade here: I showed him the article where I broke down every repo, every command, every dollar. He read it for five minutes. Then looked up. "You just published what we presented to Sam last quarter. Using the other team's model" He texted me the next morning. "My director found your thread. Take it down" Too late.

Lunar

159,942 次观看 • 5 个月前

A Google DeepMind researcher cornered me at a bar in Hayes Valley I was showing my Polymarket PNL to a friend. She leaned over. Didn't introduce herself. "That's not a trading app. Show me your stack" I told her. Claude Code. Four repos. $25 a month. She set down her drink. "We tested this internally. You connect Claude directly to a dataset. It builds its own detectors. But nobody ships it because compliance kills everything" I asked what she meant. She took my phone. Opened one link. 86 million trades. Every wallet. Every entry. Every exit. "You don't tell Claude what to look for. It finds the wallets that win. Then it finds WHY they win. Then it copies the pattern" Her team spent 9 months building this for a hedge fund. 14 people. $2M budget. "The part that took us the longest - exit logic. Everyone thinks entries matter. They don't. Exits are the entire game" I told her my bot cuts at 85% of expected move or on a 3x volume spike. She went quiet. "Who taught you that" Claude Code found it in poly_data. Top wallets exit before resolution 91% of the time. They capture the move and leave. She opened another link. "This is the scanner. Three commands. 500+ markets. No API key. Claude scores them in 20 minutes" "That's our exact infra. Except it took us 9 months and you did it in a weekend" My setup: Claude API - $20/mo VPS - $5/mo poly_data - free polymarket-cli - free 19 days. 4 agents. 74% win rate. Copytrade here: I showed her the article where I broke down every repo, every command, every dollar. She read it for five minutes. Then: "You just open-sourced our entire pipeline" She texted me the next day. "My team lead saw your thread. Take it down" Too late.

Lunar

124,458 次观看 • 5 个月前

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 次观看 • 25 天前

Using Claude Fable 5, I built a model that predicts the entire 2026 FIFA world cup.. every single game, not just the final.. so let me break the whole thing down. what it does, how it works, and exactly how i built it.. #1 First what it does: it predicts all 104 games of the tournament. not just who lifts the trophy, but every group match, every knockout, the full path from the round of 32 to the final.. everything lands in one dashboard: > group stage, every match with each team's win % and the chance of a draw > standings, how all 12 groups are projected to finish > bracket, the full knockout tree with each team's odds of advancing > champion odds, who's most likely to actually win it all and it doesn't freeze after one prediction. the moment a real game is played, it locks that result in and re-runs everything around it. so the odds move live as the tournament goes, week by week you watch favorites rise and contenders collapse. #2. How it works: the core idea is simple. the model only ever predicts one thing, a single match. the real trick is the repetition. it learns from decades of match history, then plays the whole tournament out from the first game to the final, tens of thousands of times. each run it records who advanced and who won. do that enough and you stop getting one guess and start getting real odds, one team lifts the trophy in maybe 14% of the runs, another in 9%, and so on. #3. So, how i built it ? i didn't hand-write most of the code. i broke the project into 4 pieces, described each one to fable, and let it build while i focused on getting the football logic exactly right. - The data every international match going back over a century, around 50,000 games, plus each team's elo rating, which is the truest measure of strength, and the official 2026 schedule. garbage data means garbage predictions, so this part mattered most. - The features i turned that raw history into signals the model can learn from, the elo gap between the two teams, recent form, goals scored and conceded, and a home boost for the hosts, usa, canada and mexico. - The model for each match it predicts the expected goals for both sides, then turns that into win, draw and loss probabilities plus a likely scoreline. that's what feeds the simulation. - The tournament engine this was the hard part. the 2026 world cup is brand new, 48 teams, 12 groups, a round of 32 that's never existed before, and 8 "best third-placed" teams that slot into the bracket by a fixed fifa table. even the group tiebreakers changed this year, head to head now counts before goal difference. get any of it wrong and the whole bracket falls apart, so i built it carefully and tested the format until it was exact, then wrapped it in a simulation loop that plays the tournament out tens of thousands of times. and the last piece, the live part. as real results come in, they get locked, and only the unplayed games get re-simulated. that's what makes it a living model instead of a one-time prediction. all of it outputs to a clean dashboard you can actually read and screenshot.. right now, before kickoff, it already has a clear favorite to lift the trophy.. 👀 btw who's your pick to win the 2026 world cup?

Axel Bitblaze 🪓

63,796 次观看 • 3 个月前