The new internet is not just a 'Silicon Valley' TV show futuristic idea anymore. It's relevant more than ever and it's here today.

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/…

5/5 Two auth paths, zero friction: Desktop: Calimero desktop opens the game with an SSO hash auto-enters the shared world with zero clicks Web: standard mero-js login flow, world picker lists your contexts Offline: no node needed, persists to localStorage, reconciles when you connect

4/5 Lighting and time are derived state. They cost nothing: Flood-fill sunlight and torch light are recomputed locally from block events Day/night is a pure function of the world's created_at timestamp Zero network traffic for either Perfectly synchronized across all peers.

3/5 Multiplayer presence without a tick server: Heartbeats are silent CRDT writes stamped on a room clock (max of caller clock and newest row). Two-pass mark/grace reap. A machine with a fast or backwards clock can never kill live players. The same algorithm ships in mero-meet. Battle-tested.

2/5 The world design is interesting. The service never terrain. A 128×64×128 world is generated deterministically from a seed. The contract only carries the override diff: placed blocks as block IDs, broken blocks as explicit zeros. A world with thousands of edits is a few KB of consensus state.

1/5 Mero Blocks is a browser-playable voxel sandbox. The world is a Calimero context. Every block edit is CRDT state replicated P2P across the nodes of everyone playing. No matchmaking server. No SFU.

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

We're welcoming @chefsale, CEO of @CalimeroNetwork, back to Agentic Zero. His vision for the Open Web: peer to peer and encrypted, with agents operating securely. At Calimero, he's building the tools to make it happen. See you in San Francisco!

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

This!

See you all there!

The CLOUD Act and GDPR have coexisted for 7 years without reconciliation. EU enterprises using US cloud are in an impossible compliance position. The CLOUD Act allows US authorities to compel any US-based provider to hand over data stored anywhere in the world — including EU data centers. This applies to AWS, Google Cloud, Azure. No carve-outs. GDPR Article 48 requires foreign authorities to obtain an international agreement before accessing EU subject data. No such agreement exists. The contradiction is unresolved. By design, not by oversight. Enterprises cannot depend on legal challenges. Comity challenges filed in <2% of CLOUD Act orders. Successful in <0.5%. The provider cannot satisfy both laws simultaneously. Comply with CLOUD Act → potential GDPR violation. Refuse → potential US law violation. The only architecture that resolves this cleanly: data that never sits on a compellable server. Calimero apps store state on user devices, E2E encrypted. No central server to serve a warrant to. The compliance answer is the architecture. We don't need to comply with the laws of privacy. We are privacy.

Your SaaS account is not your identity. It's their record of you. You don't control the keys. You don't control the data. You can't migrate it. When they suspend you, your identity disappears with your account. Calimero apps use cryptographic keypairs. Your identity is generated on your device. You control migration, access, and revocation, not the platform operator. This isn't philosophical. It's the technical difference between an account and an identity.

In case you missed it last year, here's our keynote from last year's @AgenticZero Our @chefsale sharing his deep tech knowledge. One year later, the topic is getting more and more popular with the raise of AI era. Check it out!

We are proud to join @AgenticZero 2026 again this year! See you in San Francisco 🚀

In October 2025, @supabase acquired Triplit - a genuine local-first CRDT sync database. The CEO's stated intent: talent and ecosystem partnerships with Triplit's competitors, not integrating Triplit's technology. No @supabase release note describes a shipped local-first feature. At $500M raised and $10.5B valuation (June 2026), the risk @supabase represents is not architectural. It's distribution. A "good enough" local-first feature under the @supabase brand wins on developer defaults, not merit. @Firebase 's offline mode: last-write-wins caching of previously-queried documents only. No proactive sync. No self-hosting. What @CalimeroNetwork offers that neither does: true device-to-device sync, formal CRDT merge, no server required after initial discovery. The gap is not marginal. doc.calimero.network Try it out today #LocalFirst #P2P #CRDT #DeveloperTools

You generate 50–100 GB of personal content in your entire lifetime. Photos, messages, documents - everything you have intentionally created and stored. Data brokers hold 50–100 GB of profile data about you right now. Up to 10,000 attributes per person. Generated from your behavior, not your content. Every SaaS platform you use contributes to this. Every click, every search, every interaction monetized without your knowledge or consent. This is the economic model of centralization. @CrabClear and similar solutions help you clean up your data from data brokers. Calimero apps collect none of it to start with.