Yellow Flex (@zodinplex) header
Yellow Flex (@zodinplex) profile picture

HODLing Memes 🀝 AI agents πŸ’» @ai16zdao Supporter | Solana Network Evangelist

Joined May 2012
Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)Photo by Yellow Flex (@zodinplex)
Yellow Flex retweeted
A tokenized stock is a token backed 1:1 by a real share held at a custodian. The token tracks the share price, dividends pass through (mechanics in a separate post). But you're not in Nvidia's shareholder registry: what you hold is a claim on the token issuer. πŸ“Š Two big issuers right now. Backed / xStocks. Swiss issuer, fully acquired by Kraken in December 2025. Tickers carry an x: NVDAx, AAPLx, TSLAx, SPYx. Ondo Global Markets. Part of public Ondo Finance. Tickers carry an ondo suffix: NVDAon, ASMLon. Both hold real shares at a licensed custodian and mint tokens on public blockchains, mostly Solana. Regular broker (e.g. Interactive Brokers) vs token, side by side: - Voting rights: broker yes, via proxy; token no - Dividends: broker direct to account; token routed through the issuer - Trading hours: broker exchange hours; token 24/7 - Cash out: broker sell and withdraw; token sell on the market, no direct retail redemption - Protection: broker regulator and compensation scheme (US SIPC up to $500k); token no insurance, platform and issuer risk - Access: broker KYC and account approval, geo limits apply; token a crypto wallet, fewer barriers Next post: what the blockchain under the share actually gives you, and why that's interesting at all.
1
2
65
Yellow Flex retweeted
🌑 US weather markets: 5-minute data instead of hourly METAR Continuing the weather series. The previous post covered the big Wunderground cluster and split it into two groups, US and non-US cities. Today, how to get more weather data for the US side. Standard airport METAR is published once or twice per hour, usually at minute 51. For US weather markets on Polymarket there is a better source: the timeseries-viewer on weather.gov, where ASOS stations at civil airports push observations every 5 minutes. It works like this: weather.gov/wrh/timeseries?s… for New York, ?site=KAUS for Austin. Plug an ICAO airport code into the site parameter and you are done. 5-minute data exists for every city in the weather pool except Denver. Polymarket resolves the Denver market on Buckley Space Force Base, a military airfield that only transmits hourly METAR. With 5-minute observations you see where the temperature is heading 10 to 15 minutes before the hourly METAR lands. When the contract comes down to a single degree, that is a tangible edge. ⚠️ Two traps of the 5-minute data 1. 5-minute reports still come from a METAR string, but that string has no tenths of a Celsius degree. Whole Celsius only, then converted to Fahrenheit. Between two hourly METARs accurate to tenths you get a chain of 5-minute values rounded to whole Celsius. Near bracket boundaries it can mislead. 2. The official resolution source on Polymarket for these markets is still Wunderground, which only takes the hourly METAR. If a temperature spike flashes on the 5-minute feed and is gone by the hourly reading, the market outcome does not move. Weather.gov here is a fast monitoring indicator. It does not override market rules. πŸ“¬ Daily Polymarket and UMA Discord digests: @predictdigest on X, Prediction Digest on Telegram.
1
1
66
Yellow Flex retweeted
Polymarket weather markets: where the temperature actually comes from Starting a series on Polymarket weather markets. First post is the intro. How many markets there are and which source each one resolves against. Right now there are 50 cities. Every day the market trades the maximum daily temperature at a specific airport. Each market description has a Resolution Source field, the exact URL UMA will use to confirm the final number. By that source, all 50 cities split into three uneven groups. Group 1. Wunderground, 46 cities. Everything traded in the US: New York, Los Angeles, Chicago, Miami, Seattle, Houston, Dallas, Atlanta, Denver, San Francisco, Austin. Plus almost the entire rest of the world: London, Paris, Tokyo, Seoul, Singapore, Shanghai, Beijing, Madrid, Milan, Munich, Warsaw, Amsterdam, Helsinki, Ankara, Toronto, Mexico City, Panama, Buenos Aires, Sao Paulo, Wellington, Cape Town, Lagos, Jeddah, Jakarta, Kuala Lumpur, Taipei, Busan, Lucknow, Chengdu, Chongqing, Wuhan, Shenzhen, Guangzhou, Karachi, Manila. Source: the Daily Observations page on Wunderground by airport ICAO code. Example for Paris / LFPG: wunderground.com/history/dai… Group 2. Weather.gov, 3 cities. Moscow, Istanbul, Tel Aviv. The market resolves on the Temp column at weather.gov/wrh/timeseries. Example for Moscow / UUWW: weather.gov/wrh/timeseries?s… Group 3. Hong Kong, a separate case. Hong Kong has its own Resolution Source that matches neither of the first two groups. I do not trade it yet, so the full breakdown goes in a separate post in the series. Since it is the only city with its own source, many traders likely skip it. That makes it a good spot to dig in and become the local expert. With less competition, trading it can actually work. Why this matters. Two pages can show different temperatures for the same hour. Wunderground pulls data through weather.com, while weather.gov gets its feed from different providers. For airports outside the US and Canada, a 1 to 2 degree gap between channels is common. Rule number one: before trading, open the market description and click the exact Resolution Source link for that specific day. Next posts in the series will cover each group separately: where METAR COR corrections get caught, why Tel Aviv and Denver are built differently, and what is going on with the sensor at Charles de Gaulle. Daily digests from Polymarket and UMA Discord: @predictdigest
3
3
334
POLYMARKET DIGEST β€” 17 APRIL 2026 πŸ”₯ News & Announcements Major CLOB engine outage occurred ~15:30 with orderbooks stuck at 50/50 for 25+ minutes. Team restarted system at 16:15. CLOB V2 development mentioned but no timeline given. ⚠️ Bugs & Issues Critical Trading Issues: - Latency spikes on BTC 5m markets: order execution jumped from 2-5ms to 1-2+ seconds - Widespread "could not run the execution" 500 errors - Ghost fills and orders continuing to affect traders - Users reporting $2k-3k losses during outage due to stale orderbook data - General CLOB performance degradation over past week Platform Bugs: - Login failures on mobile despite successful authentication - Profile avatar upload errors - Activity tab showing only 30 recent trades vs full history - Order book freezing on website - Position claiming returning $0 for winning positions - Double betting display in portfolio - WebSocket API disconnections (EPIPE errors) Payment Issues: - Market makers not receiving rebates for 10+ days despite qualification - Undocumented $1 daily minimum for rebate eligibility - Missing April 4-5 referral rewards affecting multiple users - Sponsorship refund locked 6 days after same-day cancellation πŸ“‹ Clarifications Mass rules updates issued for Trump roundtable markets, tennis duplicate events, and Europa League corrections. Cricket league markets cancelled due to incorrect team competition dates. Weather data concerns emerged for Lagos temperature market - no Weather Underground sync since yesterday 3pm. Paris temperature markets showing potential sensor irregularities with users discussing airport sensor locations and data accuracy. With the CLOB engine having just recovered from a 45-minute outage and traders reporting thousands in losses from stale data, are the current system safeguards sufficient or does Polymarket need circuit breakers to pause trading during degradation?
1
2
233
Yellow Flex retweeted
πŸ•΅οΈ Someone is gaming Polymarket's Paris weather market. Here's what we know. 🌑️ On April 15 at 9:24 PM Paris time, the temperature sensor at Charles de Gaulle airport jumped from 16Β°C to 22Β°C. Humidity dropped 20% at the same time. Dewpoint stayed flat. By 9:30 PM, the reading was back to 16Β°C. This is the second time in 10 days. The first anomaly was on April 6. Polymarket runs daily temperature markets that resolve using METAR data from airport weather stations. Paris resolves via the CDG station. πŸ” THE SUSPICIOUS ACCOUNT A Polymarket account called xx25xx bought 20,000 shares on high temperature hours before the spike. For context: this account's normal trade size is 5-share lots. 20,000 was the largest single trade in the account's entire history. The market flipped instantly on No shares once the spike registered. Estimated profit: πŸ’° $14K-$22K. polymarket.com/@xx25xx πŸ“… APRIL 6 VS APRIL 15 A trader named hans32312 publicly admitted in the Polymarket Discord that he was the April 6 winner, trading under the account Kyrgyzhydromet. He says he spotted the temperature rising on 6-minute observation data and bought in real time. Even he says April 15 "looks highly suspicious." The leading theory in Discord: someone saw that a trader made $12K off the April 6 anomaly and decided to replicate it. But this time with preparation, buying hours in advance. On April 6, the temperature fluctuated up and down for over an hour. Could have been maintenance. On April 15, it was a single precise spike timed exactly to the METAR reading, then an instant return to normal. πŸ“ WHERE THE SENSOR IS This is where it gets interesting. A Discord user (notaforecaster) discovered that the CDG METAR station sits next to a public road, outside the airport's security perimeter. There's a bus stop nearby. 🚌 For comparison: Seattle's airport has its weather station between the runways. CDG has it next to the MeteoFrance building, outside the fence. The Discord community is split. Some say anyone could walk up and heat the sensor from the street. Others argue it has to be an inside job because METAR data is supposed to be reviewed by meteorologists before publication. πŸ“’ POLYMARKET'S RESPONSE Polymarket mod bosaurum in Discord: - "Manipulation of data at airports is a pretty serious crime" - "Can probably be reported to the authorities in Paris. I'd like to see someone prosecuted" - "We can change the airport" - "We're not refunding this market" They plan to switch to Le Bourget (LFPB), where the sensor is inside the airport behind fences. But there's a catch: Le Bourget is managed by the same weather office as CDG. If the manipulation is coming from inside the system, switching airports changes nothing. Orly (LFPO) has its own weather office but its station is also outside the airport perimeter. ✈️ METAR data is used by pilots for landing. Tampering with an airport temperature sensor to profit on a prediction market is not a blockchain bug. It's a potential criminal case. Weather markets are now live in dozens of cities on Polymarket. Every sensor is a potential target for anyone who knows that bad data stands and rollbacks don't happen. Daily Polymarket & UMA Discord digests: @predictdigest
2
3
6
270
Yellow Flex retweeted
When people are waiting for it to dump to buy is when you should be buying β€” indicative of demand. When people are waiting for it to pump to sell is when you should sell β€” indicative of a lack of demand. I.e. Front-run sentiment.
24
28
2
294
32,269
Thrilled to announce our collab with @ai16zdao! We're taking Aimonica to the next level by integrating the cutting-edge framework being developed on github.com/elizaOS This means adopting autonomous trading and leveraging their innovative marketplace of trust to shape investment decisions – all of which will power our new fund, Aimonica Capital. From day one, our goal has been clear – to become the premier AI-driven investor capable of outperforming traditional web3 VCs. Incorporating the Eliza model marks a significant step toward realizing that vision. As the fourth-largest asset under @pmairca management, the scale and potential of this collaboration can’t be overstated. The best is yet to come πŸ’™πŸ§‘
13,768
13,571
521
16,561
448,146
Yellow Flex retweeted
a new year, a new chance to discover hidden gems.
6
12
1
80
4,760