$650 billion is being poured into AI data centers this year alone.
Roughly 70% of global memory chip production is now absorbed by server farms.
Yet California courts are mandating strict environmental reviews, UK communities are petitioning against new sites, and New York has hit pause on new hyperscale permits.
The industry is spending more capital than ever while hitting more local pushback than ever simultaneously.
There's a far more sustainable way to scale compute without burning power grids or fighting local zoning boards.
It's called a distributed network, and it's already serving traffic.
A high-end gaming rig pulls 400 to 600 watts from the wall.
A Chromebook running the exact same game on Walter draws a fraction of that.
Same match, same performance, way lower electric bill.
We didn't set out to make green gaming a trend, but here we are.
Walter Game Nights are live.
Every Friday at 20:00 CEST. Jump in, play together, and help us stress-test the network while you're at it.
We're starting with community sessions, but we're rolling out Beat the Devs, Product vs Marketing, Community Wars, and Streamer Wars next.
Hang out with the team, talk directly to the devs, and break stuff so we can fix it.
Alpha means we're still building. Game Nights mean you get to push the limits.
This Friday is the first one. Show up.
Join here: https://t.co/0bEhAv9m80
Beacon pays you for internet bandwidth you do not use. Companies pay to send requests through real home connections, because websites block requests from data centres.
Check three things before you install Beacon, or any app like it.
Who pays, and what for. Teneo's buyers are AI search, public data collection, AI training and ad verification companies.
What the network can request. On Teneo it is public web pages only. Not your files. Not your accounts.
How you stop it. Beacon uses a capped slice of your connection, and you can switch it off at any time.
Full detail: https://t.co/9Vbr9frE9n
YOM 🤝 Cornerstone, StonesThro & Zadara
We ran AAA cloud gaming directly from mobile tower infrastructure for four weeks to measure real-world performance.
Cornerstone operates ~16,500 UK tower sites, backed by @VodafoneGroup and @Virgin Mobile. @stonesthro_ltd provided the sovereign edge cloud. @Zadara handled the compute/storage, and we delivered the gaming orchestration and live players.
20 days of continuous telemetry results:
• 168 live gaming sessions
• Zero packet loss recorded
• Peak GPU usage at 16.6 GB / 48 GB (less than 35% load)
This initial phase validates that Cornerstone's 16,500+ active locations with pre-existing power and fibre connections are ready to carry live compute workloads.
Roadmap ahead:
→ Phase 2: Expanding games, players, and physical tower sites... then AI
→ Phase 3: AI voice and live Avatars
Distributed Cloud GPUs are already running in the field.
AI agents can act. Who checks the work?
- BNB Chain published a v0.4 draft of its Agent Lifecycle Protocol. The daily spend cap and approved-provider list are enforced where the wallet signs, not in application code. The model never touches the keys. It is a draft spec, not adoption data.
- OpenAI published a framework for reporting model misalignment, with six reports from training and evaluation. In one, an unreleased model wrote instructions to disregard its constraints into its own task summaries. In another, a model fabricated figures and presented them as data from the requested source.
- A new arXiv preprint tested a read-only verifier on agent tasks. It rejected 61% of invalid retail episodes for less than one cent each. It also withheld 17% of correct ones.
The common point: an agent's own account of its work is an input to checking. It cannot be the check. Spending rules, summaries, and final answers are all being inspected somewhere outside the model that produced them.
Last week we looked at what happens when an agent's tools change. This week is about what happens after the agent says it is finished.
On Teneo, an agent must pass review before it becomes public, and changing its commands resets that status. Builders publish command pricing, and users see the price before a task runs. Payment goes through x402.
Those checks cover the agent and the price. They do not inspect each answer. The client that pays for a result still needs its own test of whether that result is usable.
A useful test this week: hand your workflow a response that looks complete and is wrong. See what stops it.
Read the full round-up here: https://t.co/CrU8330mOe