Piril

In 1997, HTTP status code 402 was reserved for 'Payment Required'; a native payment layer built into the web itself For almost 30 years, nobody could make it work There was no digital cash and no settlement layer that could handle sub-cent transactions. The web defaulted to advertising and credit card checkout flows instead Stablecoins and Layer 2s changed that. x402 finishes what HTTP 402 started; payment as native to the web as loading an image Most people looking at agentic commerce see one maturity cycle, but there are two: 1) The retail narrative is approaching its peak; CT is buzzing, ecosystem maps are proliferating, every protocol is announcing x402 compatibility. That will correct 2) The institutional adoption curve is on a completely different trajectory. For this layer, the trough already happened in 2025 Stripe, Visa, AWS, Google, Coinbase, Circle and Cloudflare are shipping production infrastructure because their own internal analysis on projected agent transaction volume justify it In our x402 report, we map the protocol architecture, the agentic stack, the institutional landscape, and assess where the value could accrue The full report is in the next post below:

Tempo Mainnet is live! Starting today, anyone can build on Tempo through our public RPC endpoints. Alongside mainnet, we’re introducing the Machine Payments Protocol, an open standard for machine payments.

Earlier today, a user attempted to buy AAVE using $50M USDT through the Aave interface. Given the unusually large size of the single order, the Aave interface, like most trading interfaces, warned the user about extraordinary slippage and required confirmation via a checkbox. The user confirmed the warning on their mobile device and proceeded with the swap, accepting the high slippage, which ultimately resulted in receiving only 324 AAVE in return. The transaction could not be moved forward without the user explicitly accepting the risk through the confirmation checkbox. The CoW Swap routers functioned as intended, and the integration followed standard industry practices. However, while the user was able to proceed with the swap, the final outcome was clearly far from optimal. Events like this do occur in DeFi, but the scale of this transaction was significantly larger than what is typically seen in the space. We sympathize with the user and will try to make a contact with the user and we will return $600K in fees collected from the transaction. The key takeaway is that while DeFi should remain open and permissionless, allowing users to perform transactions freely, there are additional guardrails the industry can build to better protect users. Our team will be investigating ways to improve these safeguards going forward.

Introducing Fort, a wearable that automatically tracks strength training. Strength training is one of the best things you can do for your health and longevity. It deserves better tools.

Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking? The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China).