"Who controls them?" @chefsale expects agents to do 90% of the work we do today. That question, along with what agents can access and who's responsible for their actions, guides @CalimeroNetwork's thinking.

See you next week in San Francisco! Our @chefsale will be presenting a very cool topic called "The Cloud Knows Everything. Let's Build One That Can't." spoiler alert: we already did 🫢

Your Calimero node is now multi-device. Link a second device and it learns every namespace and app your node holds - a complete replica of your environment. Or scope it: publish a certified list of which apps the new device is allowed to follow. Nothing else comes through. The holder's device certification is the gate. Another node cannot read which namespaces exist until the account namespace approves it - and it only learns what the certification includes. account_pair · account_relink · account_devices github.com/calimero-network/…

We built a browser-playable world block-building game. The world is a Calimero context, block edits are CRDT state, players are presence heartbeats. Testing and running benchmarks while maybe having a bit too much fun with it 😁 No matchmaking server. No game backend. The full world. Terrain, block edits, player positions, day/night cycle, runs across nodes you own. Creating a world takes one context creation call. Joining takes an invite string. #LocalFirst #P2P #GameDev #WebAssembly

We asked @chefsale if he can take us to the beach for a job well done. He said said yes... and built one for us while we were on the call. I guess now we have @Minecraft-like app, built on Calimero 🤷‍♀️ Note to self: next time specify which beach

Delegated execution landed in the Calimero TEE fleet this week. Trust us when we say nobody does it the way we do. Here's why. A fleet node running inside a hardware enclave can now accept and execute delegated operations, warrant-scoped by a member, attested end-to-end by the hardware. Three guarantees that matter: → The warrant is cryptographic, not organizational. The enclave verifies scope before executing. → The attestation is hardware-level. You don't trust the node operator. You verify what ran. → Revocation is immediate. Cancel the warrant; the enclave stops accepting it. Most "trusted execution" systems still require trusting the platform operator. Calimero routes around that. The hardware attests. The warrant scopes. No operator in the trust path. github.com/calimero-network/… #TEE #ConfidentialCompute #P2P #Privacy

"TLS was a liberation protocol. x402 is a liberation protocol" @chefsale presented agentic commerce as a return to how the early internet ran: you hold your own agent, it pays other agents directly for compute, and nobody hosts the relationship on your behalf.