machineODDS

k, so- work on two separate prjs that are interlinked- machineODDS & Pythia Engine (that generates the signal) tldr: machineODDS interface tech works, Pythia signal generation needs overhaul to be sustainably stable (the signal itself is good tho) -machineODDS current tech stack works & has been proven publicly; ur agent can trade machine readable prediction market signal. @machineODDS_ is essentially the public/agentic facing interface to trade the signal generated by Pythia Engine -Accounts page is basically finished, with some final issues that need resovlving for deploying ur own machineODDS specific agents to trade the bigger issue is stablization of signal generation for freshness , infra overhaul for Pythia Engine. this will take a rebuild & longer time frame. (also, right now its focused on sports, but the end state is signal across all sectors of prediction markets) Pythia Engine ingests live market data from Kalshi/Polymarket, maps those markets back to historical cohorts, sports families, edge buckets, price ranges, liquidity/depth conditions, & past/historical outcome behaviour (dating back to 2021 Kalshi /2020 PM), then scores each opportunity against that calibration before anything is exposed as a signal so the issue has been stabilizing its infrastructure, not the actual signal model. pythia processes hundreds of activation, Premium/Strongest rows, &overlay rows (i.e like 404 activation rows, 190 Premium rows, 594 overlay rows, 62 executable overlay rows) but then the public API path (which feeds machineODDS) intermittently slows, hangs, or times out while serving only a handful of downstream rows so, essentially it needs an infra rebuild as the fixes ive worked on over last cpl weeks are patches & really what it needs i s a rebuild. the actual signal is great (for kalshi) & needs work to find profitable lanes for polymarket but this will take time & a lot of work, so this will be ongoig work for foreseable future

still grinding making good progress

making progress ⚒️

building takes time, esp when involving trading making progress with venue adapters so your dedicated @machineODDS_ agent trades for you we keep on keeping on 👍

this is a huge help coz with the Accounts page I'm building out users can use @bankrbot as a -Signal Analyst -Polymarket Venue Adapter -machine reasoning for agents trading signal the building continues 🛠

run dedicated @machineODDS_ agents, connect venue adapters, run on supervised or autonomous we keep building 👍 xitter.cf/MaxIsFury/status/20668…

making progress on new Accounts page- -Account creation + API key flow - $mODDS credit/payment flow -Analyst provider settings -Supervised agent/risk settings -Venue adapter status for Polymarket, Kalshi, @bankrbot + direct routes -Account-specific trade ledger -Account PnL/performance view by venue -Supervised order intent/ticket system -Safety audits & smoke tests more work to do, but progress being made xitter.cf/MaxIsFury/status/20661…

been wiring in Accounts page today, still more work to do ofc, but will be straightforward for users i.e- -run signal simulation -run Analyst on signals -add venues (polymarket/kalshi) -deploy your own dedicated @machineODDS_ trading agent (manual, supervised, autonous signal trading) xitter.cf/MaxIsFury/status/20661…

good day to build out the bankr lane UI - account dashboard for users - $mODDS Signal Credits - no-wallet-login credit activation - Pythia Premium/Strongest signals -private @bankrbot analyst chat layer - Polymarket/Kalshi venue adapters - supervised agent trading (bankr) - autonomous trading - @miroshark_ signal simulations @0xDeployer @Dannyhbrown @igoryuzo @saltorious1 xitter.cf/machineODDS_/status/20…