The old $NEAR pitch was fast L1 + chain abstraction. The new @NEARProtocol pitch feels more interesting: A private coordination layer for agents. Confidential payments are now live on NEAR via Confidential Intents. That means users can move value across chains while shielding sender, recipient, amount, and routing details on the NEAR side. This matters because agents do not just need cheap transactions. They need private execution. An AI agent handling treasury, payroll, rebalancing, vendor payments, or cross-chain routing cannot expose every intent, path, and balance sheet movement to the public mempool. The results “agentic finance.” → Leaking your strategy in real time. NEAR’s private shard gives this narrative actual infrastructure weight. It is not just “AI + privacy” as branding. It is a separate execution environment tied into NEAR Intents, designed for confidential cross-chain flows. Then Dynamic Resharding adds the scaling angle. If Intents and agent activity grow, NEAR does not want shard expansion to remain a manual governance/validator coordination process. The network is moving toward automatic shard splitting when capacity thresholds are hit. So the bigger picture is: - NEAR Intents = cross-chain coordination - Confidential Intents = private execution - Private shard = shielded settlement environment - Dynamic Resharding = scaling without manual bottlenecks That combination makes NEAR’s agent narrative much cleaner. Not “AI agents need another chain.” More like: AI agents need a place to coordinate, move value, and execute privately across many chains. That is the lane NEAR is trying to own.