ChimeraDefi

Swarm riders and Swarm-native companies AI-use even among highly AI-native people is power-law distributed. There seems to be a new class of people — call them “swarm riders” — who are capable of consistently commanding large swarms of agents to productive ends. This is a new kind of managerial skill, analogous to the skill it takes to manage large organizations of people, but wholly different in nature and of course more technical. Based on the swarm riders we know (including many at @Tempo and @Paradigm), these people are capable of productive token spend that is 1000x-10000x higher than median software engineers, and 100x higher than top 5% Claude Code users. The art of swarm riding is different from software engineering and more akin to machine learning, where practitioners grapple with black box systems: defining reward functions and evals, transmuting non-verifiable problems into verifiable problems, running experiments, etc. Swarm-native companies are a new class of company founded by and populated by swarm riders. These companies are organized around swarms in a way that conventional companies will struggle to replicate, as the cost of internal human coordination is sand in the gears of an effective swarm. Effective swarm-native companies will define the right reward functions and evals, remove functional and bureaucratic barriers, and then let the swarms cook. We’ve gotten to see a few swarm-native companies up close — reshaping financial rails @Tempo, building a new gaming platform @Spawn, cyber swarms at Cathedral Systems — and it’s clear these teams wield a significant advantage over pre-AI teams. Some questions I’ve been wondering about: 1) How fast will swarm riding diffuse through the economy? The implications for token spend could be significant. 2) Can swarms be effectively adopted by existing companies or will it generally track the formation of new swarm-native companies? 3) What becomes scarce as swarm capabilities themselves commoditize (through frontier models becoming better at swarming, swarm capabilities built into harnesses, etc)? Cultures and teams that can define reward functions well and otherwise get out of the way?

Canada’s Real-Time Rail (RTR) is a new national payment infrastructure owned and operated by Payments Canada. It allows participating financial institutions, credit unions, and payment service providers to send and receive account-to-account payments that clear and settle in seconds, 24 hours a day, 365 days a year. It launched on November 9, 2026. How it differs from Interac e-Transfer Many people confuse the two, but they are not the same: •Interac e-Transfer is a consumer-facing service. You send money using someone’s email address or phone number. It feels fast for users, but historically the funds did not fully clear and settle between banks in true real time. •Real-Time Rail is the underlying national “rail” (infrastructure). It handles the actual exchange, clearing, and settlement of the money in real time between financial institutions. e-Transfer is expected to begin migrating its clearing and settlement onto the RTR in 2027. The familiar e-Transfer experience will largely remain, but it will eventually ride on the new infrastructure. Key features •True real-time settlement: Funds are available to the recipient almost immediately, and payments are generally final and irrevocable once settled. •Always on: Works evenings, weekends, and holidays with no cut-off times. •Data-rich payments: Uses the ISO 20022 messaging standard, so more structured information (like invoice numbers) can travel with the payment. •Built-in fraud tools: Includes centralized fraud services (such as confirmation of payee and real-time risk scoring) from day one. Canada is the first G7 country to launch a real-time system with mandatory centralized fraud controls. •Higher limits: System limit starts at $100,000 (financial institutions can set lower customer limits). Current status and rollout The system is live, but access is phased. Some smaller institutions and fintechs are already connected; the major banks are coming online later. The goal is for over 90% of Canadian bank accounts to have access by the third quarter of 2027. In short, the Real-Time Rail is the modern backbone that makes instant, final, data-rich payments possible across Canada. It is not a new app or a replacement for e-Transfer—it is the national infrastructure underneath (and eventually supporting) faster money movement.

Contract looks like Python -- indentation has meaning, fairly rigid about formatting, fairly sparse. And it is explicit and stron gly typed and pulls complexity forward into authoring like Rust. Your Contract code describes both your UI like you would in React an d also your state and data flow, the way you would with Redux or Zustand or TanStack Query.

Update #2 (after meeting with the @bot @SpaceXSI engineering team): - Team is great. They care a ton. They owned it. - They admitted that it was almost entirely from pulling Opus 5.5 out. Which is now back as of this AM. - Learned a little bit about the context-compaction process with Grok 4.7-summarize which is not a public model. Plays a role in routing config and the summary we get back. - Grok 5.0 should be insane next level (just as an aside point) - I am somewhat surmising on why stuff went so poorly over the weekend but a lot of it has to do with not just pulling Opus 5.5 out but when they did that a known problem (and was on cursor as well) showed up which is when you switch the model mid task (which would’ve happened by removing our 5.5) it cannot remember the context and even of what it can gather its truncated (likely do to 4.7-summarize compacting). So in our case what likely happened was we had a lot of stuff mid flight that was likely pulling on opus 5.5 heavy, then it got pulled, routed to different model, forgot the context, and turned incredibly dumb. We laughed when I showed them a project that was mid flight in a doc. The first half of the doc was intelligently designed, formatted, etc. and the second half of the doc was a wall of seemingly incoherent, non formatted text. Again, I’m surmising but I think it was dumber model with all context removed - I won’t say much here but Elons comment on it being “unsustainably high relative to revenue” was a much larger chess move. Won’t say much past that. Not my place. But he’s definitely playing a much larger chess match than just “Grok bot isn’t sustainable”. - The problems we all experienced should be fixed and I do not think they want to go back to what they experienced over the weekend with the hit it took. - They are very much focused on the enterprise use case for grok bot in the future All in all, how’s this impact my decision making moving forward with the enterprise contract we have: - Honestly still weighing the decision vs just using team plan. Working through some terms - the reason to move forward is pretty simple. Unlimited users (so not paying per seat but for usage), access to forward deployed team and engineers for support and circumstances like I just experienced, very granular governing and guardrails for the org. That’s it Impressed with the team overall and I think the main benefit to staying vs moving to open source (for a company like mine vs being a solo/small company) is trusting their ability to ship and keep building plus keep it maintained. Shoutout to @ASankarraman for jumping in to help and to the @SpaceXSI, @bot, and @elonmusk teams

guys I'm not doing more pitch meetings, sorry :( if you're interested just send your desired allocation to my email the deck is at: bend-lang.com/deck.pdf locking in now, see you

Meet Penny, our new AI financial assistant. Penny will be able to do things like, send an e-Transfer, pay your credit card bill, buy stocks, sell stocks, or help you max out your TFSA — by text, email, or in the app. It won’t move anything without your approval and is built with protections throughout for extra security. Coming soon. *Actual features when made available may differ than shown.

Firearm charges laid against resident following fatal home invasion in South Glengarry, Ont. ctvnews.ca/ottawa/article/fi…

don’t search #Duolingo 👀🥵

No public evidence supports Larimer writing 2 million lines of C++ in one year with zero safety or liveness bugs. Graphene/BitShares/EOS involved substantial C++ work by him and teams, but codebases of that scale over a single year by one person, bug-free, is not documented and exceeds typical high-output rates. His 2028 claim is a personal biblical timeline calculation, not a verifiable technical prediction.

Hard to overstate how big this is. tl;dr - CVE-2026-98432: a remote use-after-free in the Linux IPv4 TCP handshake (kernels 4.4+). Any unpatched server that accepts IPv4 TCP on an MPTCP listener can be taken over as root, with no credentials. Go servers built with Go 1.24+ use MPTCP listeners by default. Ubuntu and RHEL have no fixed kernel yet. Check with ss -Mlnp. Quick fix for Go: GODEBUG=multipathtcp=0.

Austin, TX (OCT.25.2026)- We knew the day would come. Zoox vs Waymo vs Cybercab #SunsetProject

We are aware of a small number of users who have experienced unauthorized transfers of funds from their wallets, totaling approximately 400,000 USDT. Our preliminary investigation suggests that our API documentation site, which is hosted by a third-party provider, may have been compromised, potentially affecting a small number of users over a short period of time. The API documentation site has been taken offline as a precaution and will remain offline until our investigation is complete. At Predict.fun, we take the security of our users and their funds extremely seriously. As such, we will fully reimburse all affected users for any funds lost as a direct result of this incident. Once our investigation is complete, we will publish a full post-mortem detailing what happened and the steps we're taking to prevent similar incidents in the future.

The Founding Fathers tied voting rights to property ownership. Their (correct) reasoning was that only property owners have skin in the long game. Brazilian stocks plunged nearly 25% after an election, the market has made it very clear that it thinks. Yet non-owners barely feel the pain even if everyone pays eventually for the cost of socialism. The solution, however, isn’t fewer voters, but more capital owners. A healthier democracy requires widespread capital ownership, not just income redistribution. Universal stock grants held in trust until age 25–30, with earlier access for education, would give everyone a stake in the country’s future. There’s an obvious irony in using redistribution to defend capitalism. The goal isn’t to socialize ownership but rather to decentralize it. A society dependent on the state is different than a democracy of individual owners with a stake in its future.

Always amazed when I learn about a new public company for the first time. Especially one that did YC and is based in SF/NYC. @BillionToOneInc is a $5B+ public company ($BLLN) that I never heard of before today. Despite it being YC S17 and the fact that I did YC myself a couple batches afterwards, I had no clue it existed. As far as I can tell, it's @ycombinator's biggest bio success story too. Checked the X account and it has 1,302 followers. Have never seen on a podcast, a wsj article, on the timeline, etc. but yet a monster bio company making very real revenue! Goes to show that there are likely multiple companies founded in last 10 years (not just the sleepy under the radar midwest ones from decades ago) still based in hot areas (BillionToOne is in Menlo Park) that still don't show up on the "timeline" and are even public (BillionToOne IPOed last year) that fly very under the radar...looks like the buzz makes no difference to its success!