u/Dramatic_Spirit_8436

On Polymarket, "Will no Fed rate cuts happen in 2026?" is priced at 69.5% YES. On Kalshi, the same contract is at 65%. Both platforms say roughly 2 to 1 odds the Fed holds all year.

The weird part is who believes it more. Polymarket's base is overwhelmingly crypto and tech. Kalshi's is traditional finance. The group whose portfolios literally depend on easing (BTC, DeFi yields that already look anemic next to 5% treasuries, basically all of crypto) is pricing "no cuts" 4.5 points HIGHER than the tradfi crowd. You'd think they'd be the ones talking their book in the other direction.

I first noticed the divergence a few weeks back on Surf while messing around on a free account. Wasn't even looking for it. The gap first crossed 4 points in late April, and $4.2 million in Polymarket volume later, it still hasn't compressed. Contract resolves end of 2026 so this isn't about to expire and stop mattering.

Actually, that's the part I keep getting stuck on. When matched contracts on two liquid platforms diverge for weeks, usually arbitrage closes the gap pretty fast. The fact that it persists tells you the two trading populations genuinely disagree on magnitude, not direction. Both think no cuts is likely. Crypto traders just think it's MORE likely. And these are the most liquidity sensitive participants in the entire market, people who feel a prolonged hold before anyone else does.

For anyone positioned in risk assets on the assumption that easing eventually arrives: the people most exposed to that bet being wrong are the ones abandoning it.

Every month I was spending about 6 hours pulling together a competitive landscape report for my agency's email marketing clients. They wanted to see where their current platform sat relative to alternatives on three axes: pricing per 10k contacts, deliverability score (from EmailTooltester and GlockApps benchmarks), and aggregate G2 satisfaction rating. I was doing this in Google Sheets, screenshotting a scatter plot that honestly looked like something from a 2014 blog post, and pasting it into a slide deck. Clients never complained. I kept making copy and paste errors and dreading the first Monday of every month.

So I automated the whole thing. The report runs on a monthly cron, scrapes current pricing pages for Mailchimp, Klaviyo, ActiveCampaign, ConvertKit, Brevo, Customer.io, Drip, Omnisend, MailerLite, and GetResponse. I was genuinely surprised Customer.io even publishes list pricing given their enterprise lean, but they do and it scrapes cleanly. The agent pulls deliverability benchmarks from public test sources, grabs G2 scores via their API, and renders everything into an interactive bubble chart (Chart.js) inside a single HTML file. Each bubble is sized by G2 review count as a rough proxy for market presence, positioned with monthly cost at the 10k contact tier on one axis and deliverability percentage on the other.

Some findings from the May 2026 run. Brevo scored 93.6% deliverability, up from 90.1% three months ago, now sitting just 2.2 points behind Klaviyo's 95.8% at roughly half the cost for the same contact tier. That was the number that made me go back and manually verify the scrape twice. MailerLite continues to be the pricing outlier, coming in under $50/mo for 10k contacts while holding a G2 score above 4.5. ActiveCampaign raised its Lite tier pricing again (third increase in 12 months) without a corresponding bump in deliverability or satisfaction, which is exactly the kind of slow drift my clients never notice until renewal sticker shock hits.

Actually that last point led to a real conversation. One of my clients had been on ActiveCampaign for two years and hadn't registered that their effective per contact cost crept up 22% since they signed. I showed them the delta column in the tracker and they started a migration conversation that same week. Probably the single most useful thing the report has done, and it was a byproduct I didn't plan for.

The setup runs on a MuleRun agent with a cron schedule. I described the scrape targets, the benchmark sources, the comparison logic, and the chart layout in plain language; took about 45 minutes to get the first version right. The part that ate the most time was handling pricing pages with nonstandard markup. Omnisend loads their pricing dynamically with about four different slider states, so the scrape specifically captures the 10k contacts position rather than trying to parse every tier. Getting that one source reliable probably took more iteration than the other nine combined, which I did not expect going in.

The other recurring challenge is full page redesigns. GetResponse overhauled their pricing page in April and broke the scrape for one cycle. I added a fallback that flags "unable to confirm current pricing" in the table rather than silently displaying stale numbers. That ended up building more trust with clients because they could see the system being transparent about its own gaps instead of confidently showing wrong data.

Below the chart there's a sortable comparison table with exact numbers, a delta column, and a flag for any platform that moved more than 10% on any metric since the prior month. The whole thing deploys as a hosted page I share via link. Clients treat it like a dashboard now rather than a static PDF. A couple have asked if they can trigger a fresh pull on demand instead of waiting for the monthly cron, which I keep saying I'll set up and keep not doing.

So an AI found CVE-2026-42945 in nginx. 18 years in the rewrite module, CVSS 9.2, affects ~19M instances. Found in 6 hours. 4 out of 5 findings confirmed as remote memory corruption.

18 years of human review missed it. Thousands of contributors. Fuzzing. Static analysis. All missed it. The bug was a logic issue in the two phase processing that only showed up under specific concurrent conditions.

Makes me wonder what else is hiding in our infra repos. We run tfsec and checkov on everything and they catch the obvious stuff. But they missed a terraform module where a security group allowed 10.0.0.0/8 ingress on a port that only needed access from a single /24. Technically valid, but way broader than necessary. Started using verdent for review on our terraform modules and it flagged that immediately. Both scanners and two human reviewers had approved it because the rule wasnt technically "open". Embarrassing.

If 18 years of nginx review can miss a CVSS 9.2, our infra code is probably full of similar blindspots.

Okay idk if this is even worth a full post, but it’s been stuck in my head for a few weeks and I wanted to hear how other Protestants think about it.

I’m Protestant and I wear Christian inspired stuff sometimes. Not the huge church camp shirt type thing, more like regular clothes where a verse, a cross, or some biblical image is worked into the graphic. Most of the time I don’t think that hard about it. I just like the shirt and put it on.

A few weeks ago I wore a GuidingCross tee to church. It had a verse in the graphic, and I thought it was pretty subtle, or at least I hoped it was. After church one person said they liked it and thought it was a good way to bring faith into normal life. Then someone else said kind of the opposite, that putting Scripture on casual clothes can make it feel more like decoration than something serious.

That second comment stuck with me more than I expected. Not because I think wearing a verse tee is automatically wrong, but because I also don’t fully trust the whole “my intentions are good so it’s fine” thing. I feel like that can excuse a lot if you let it.

Then I started asking myself the more awkward question. If someone actually asked me about the verse on the shirt, would I want to talk about it, or would I feel weird because honestly I mostly bought it because I liked how it looked? I don’t really have a clean answer to that rn, which is probably why I’m still thinking about it.

So yeah, I’m not looking for a final answer or anything. I’m just curious where other Protestants draw the line. What makes Christian clothing feel reverent to you, and what makes it feel cheap or unserious? Is it the design, the intent, whether you’d actually talk about it if someone asked, or something else?

I've been refining my token research process over the past few months and wanted to share a complete breakdown on Ondo Finance as an example, since it's been getting attention with the RWA narrative heating up but most of the analysis I see is surface-level price action takes. The goal here is to show a repeatable framework, not to shill a specific token.

Starting with fundamentals: Ondo is building tokenized real-world asset products, primarily USDY (a tokenized note backed by short-duration US Treasuries and bank deposits) and OUSG (tokenized short-term US government bonds). TVL across their products sits around $850M as of this week, which is up roughly 340% from where it was six months ago. They've integrated with multiple chains including Ethereum, Solana, Mantle, and Sui. The team has traditional finance backgrounds — the founder previously worked at Goldman Sachs in their digital assets division, and they raised $34M across rounds from Pantera, Coinbase Ventures, and Wintermute among others. The protocol generates revenue from the spread between the underlying yield and what's passed through to holders, which gives it an actual cash flow model unlike most DeFi tokens.

On-chain holder distribution is where it gets interesting. Top 100 wallets control approximately 85% of the circulating supply, which is concentrated but not unusual for a token this early in its distribution curve. What matters more is the trend: the number of unique holders has grown from roughly 22K to over 48K in the past 90 days, and smart money wallets (tagged fund and institutional addresses) have been net accumulators over the past 30 days. There's been a noticeable pattern of accumulation in the $0.80-$0.95 range from wallets associated with known crypto funds.

Social sentiment trajectory shows a divergence that caught my attention. Mindshare for ONDO among tracked crypto KOLs has been climbing steadily over the past 3 weeks, currently ranking in the top 15 by mention volume across 100K+ tracked accounts. But the sentiment split is roughly 62% bullish, 24% neutral, 15% bearish — which is actually more balanced than you'd expect for a token in an uptrend. The bearish sentiment clusters around concerns about regulatory risk for tokenized securities and the concentrated holder base. Historically, tokens where social sentiment runs ahead of price tend to correct, but in this case price has actually been leading sentiment, which is a healthier setup.

Vesting and unlock schedule is critical and often overlooked. ONDO had a major unlock event in January 2024 when roughly 1.94 billion tokens (19.4% of total supply) entered circulation. The next significant unlock is a series of community access sale vesting completions, but the big one to watch is the continued linear unlock for ecosystem growth and protocol development allocations running through 2025. Current circulating supply is approximately 3.2B out of 10B total, meaning roughly 68% of tokens are still locked or unvested. That's a meaningful overhang and something any position sizing should account for.

Technical setup on the daily: price is trading above the 21 and 55 EMAs with the 8 EMA acting as dynamic support on pullbacks. RSI is at 58, which is constructive but not overheated. The $1.05-$1.10 zone has been resistance on three separate tests. Volume profile shows a high-volume node around $0.90 which would be the logical support if the broader market pulls back. ADX is at 28, indicating a trend is present but not at the extreme levels we're seeing in BTC right now.

The whole process for pulling this together took me about 15 minutes using a combination of on-chain data, social tracking, and technical analysis through Surf, compared to the 2-3 hours it used to take me when I was manually cross-referencing Etherscan, CoinGecko, Twitter search, and TradingView in separate tabs. The key efficiency gain isn't just speed — it's having the on-chain holder data, social sentiment metrics, and technical indicators in the same research flow so you can spot divergences between them immediately rather than trying to mentally stitch together data from five different sources after the fact.

The framework itself is what matters more than the specific token. For any project I'm evaluating, I run through the same five layers: fundamentals and revenue model, on-chain holder distribution and smart money flows, social sentiment trajectory and KOL attention, vesting and unlock schedule pressure, and technical structure. When three or more of these align in the same direction, that's when I pay closer attention. When they diverge, that's usually a signal to wait or reduce size.

None of this is financial advice — I'm sharing the research methodology, not a trade recommendation. The RWA space has legitimate regulatory uncertainty that could change the thesis overnight.

DeepSeek dropped the full V4 paper this week. preview from april was 58 pages, this version adds a lot of technical depth.

What stood out for me.

FP4 quantization aware training. theyre running FP4 QAT directly in late stage training. MoE expert weights quantized to FP4 (the main gpu memory consumer). QK path in the CSA indexer uses FP4 activations. 2x speedup on QK selector with 99.7% recall preserved. inference runs directly on the FP4 weights.

Efficiency table is striking:

Model	1M context FLOPs	KV cache
V3.2	baseline	baseline
V4-Pro	27% of baseline	10% of baseline
V4-Flash	10% of baseline	7% of baseline

Training stability, two mechanisms.

Trillion parameter MoE has the loss spike problem, divergence, unpredictable failures. they documented two fixes.

Anticipatory routing. they deliberately desync main model and router updates. current step uses latest params for features, but routing uses cached older params. breaks the feedback loop that amplifies anomalies. 20% overhead but only kicks in during loss spikes.

SwiGLU clamping. hard limits on the SwiGLU linear path (-10 to 10) and gate path (max 10). suppresses extreme values that would cascade.

Generative reward model. instead of separate reward models for RLHF, they use the same model to generate and evaluate. trained on scored data, model learns to judge its own outputs with reasoning attached. minimal human labeling, reasoning grounded eval, unified training.

Human eval results. chinese writing, V4-Pro 62.7% win rate vs gemini 3.1 pro, 77.5% on writing quality specifically. white collar tasks (30 advanced tasks across 13 industries), V4-Pro-Max gets 63% non loss rate vs opus 4.6 max. coding agent eval, 52% of users said V4-Pro is ready as their default coding model, 39% leaned yes, less than 9% said no. tracks my own use, swapped V4-Pro into my verdent runs last week and havent noticed a quality hit on day to day work.

The headline for me is FP4 QAT with minimal quality degradation. if this generalizes the cost structure of training and inference shifts a lot, especially noticeable on multi agent setups where one task can spawn 5-10 model calls.

Paper link in comments.

Been with the same company for about 4–5 years now. Overall it's been stable, but salary growth has been pretty limited. I guess i just got used to it and never really pushed to change anything. Every now and then recruiters would reach out, and i usually ignored them or declined right away without thinking too much

this time was a bit different. I don't even know why, but i decided to actually hear them out and go through the process. Didn't expect much, but things moved pretty quickly. Interviews went smoother than i thought, and the offer they gave was around 50% higher than what i'm making now.

The only thing is the new role includes some supply chain responsibilities, which i haven't really dealt with before. My current role is more on the operational side, so this feels like stepping into something new. Talked to a few friends about it and most of them said it could be a good opportunity to grow, especially since supply chain experience seems useful long term. So i decided to take the offer. Feels a bit risky but also kind of exciting. Now i'm just trying to get up to speed before starting. Reading around, watching videos, trying to understand how things actually work in practice.

I've been following embodied intelligence research for a few years now, and something clicked for me recently about why we keep seeing incredible lab demos of robots folding laundry or making coffee, but nobody's actually living with one of these things. The problem isn't hardware. Dexterous hands, force controlled joints, even wheeled mobility platforms are all pretty mature at this point. The bottleneck is architectural, and it sits inside the AI itself.

Practically every major embodied AI system today runs on some flavor of VLA: Vision Language Action. The idea sounds elegant. A vision module recognizes objects in the scene. A language module parses the instruction or context. An action module generates motor trajectories. Three specialized networks, chained together. The issue is what happens at the boundaries between those modules. When rich visual information (spatial relationships, material properties, lighting context) gets compressed into a token sequence to hand off to the language module, you lose fidelity. When language understanding gets compressed again into action space, you lose more. It's a game of telephone. By the time the action module decides how to move the arm, it's working with a blurry summary of what the vision system actually saw.

In a lab, this works fine. The lighting is controlled, objects are placed in known positions, there are no cats jumping on tables. But a real home is an adversarial environment for this kind of pipeline. Every second can produce a novel situation. Slippers kicked under the couch at a weird angle. A plate half hanging off the counter. A child's backpack dropped in the hallway. The VLA pipeline doesn't understand why that plate is about to fall. It can only reproduce trajectories it has seen before. If it hasn't seen a plate in exactly that configuration during training, it either freezes or does something wrong.

The analogy that made this concrete for me is Apple Silicon's unified memory architecture. Before the M1, Macs had a CPU, a GPU, and separate memory pools. Data had to shuttle back and forth across buses, creating latency and bandwidth limits. When Apple unified everything into a single memory space, performance jumped not because any individual component got dramatically faster, but because the bottleneck of data transfer between components disappeared. The same logic applies here.

A new approach called World Unified Model (WUM) architecture does something conceptually similar for embodied AI. Instead of training vision, language, action, and physics prediction as separate modules and then stitching them together, WUM trains all four jointly inside a single network from the very first day. There is no module boundary. The system sees a cup and begins preparing a grasp trajectory simultaneously. It feels the weight through force feedback and adjusts grip force in the same forward pass. Critically, it also learns physics: gravity, inertia, friction, momentum. So when it encounters that plate hanging off the counter in a home it has never visited, it can infer the plate will fall and take preventive action, not because it memorized that specific scenario, but because physics is consistent across environments.

X Square Robot just announced WALL-B, which they describe as the first production grade foundation model built on WUM architecture. What caught my attention wasn't the announcement itself but three specific technical claims. First, native proprioception: the model internally senses its own spatial dimensions (arm reach, body width) and judges whether it can fit through a gap or reach a shelf without relying on external sensors or constant self observation. Second, physics grounded zero shot generalization, meaning it can operate in homes it has never trained in. Third, and this is the one I find most interesting, in the wild self evolution. When the robot fails at a task, instead of halting and returning an error, it adjusts strategy and retries. If the retry succeeds, that success gets written into the model parameters directly. No engineer intervention, no trip back to the lab. The analogy their CTO used was learning chopsticks: you drop them thousands of times, each failure adjusts your motor control, and eventually the skill stabilizes.

They also made a point about data quality that resonated. Most embodied AI models are trained on what they called "sugar water data" from labs: clean, controlled, and plentiful but nutritionally empty for real world performance. Their approach instead collects data from hundreds of real volunteer households with all the messiness that entails: different lighting in every room, floors covered in toys and delivery boxes, pets that rearrange the environment constantly. The argument is that this messy, unpredictable data is what actually builds generalization.

The honest framing was refreshing too. They explicitly positioned their robots as being at an "intern" stage. They will make mistakes. They might put slippers in the kitchen or pause mid task to process. But they work continuously and improve with every interaction. They committed to deploying WALL-B powered robots into real volunteer homes by May 26, with privacy protections including on device visual masking (raw images never leave the device), explicit opt in consent, and no third party data sharing.

I think the bigger question for the field is whether this architectural shift from modular pipelines to unified models represents the kind of phase transition that actually unlocks real world deployment at scale over the next five to ten years. If WUM works as described, the implication is that the data flywheel from real home deployment becomes the moat, not the model architecture itself. The first system that can reliably operate in messy real environments collects better data, which makes it more reliable, which gets it into more homes. That feedback loop could be decisive.