184.1K @a16zcrypto DePIN is reimagining physical infrastructure, including telecom and transportation networks, energy grids, and more.
The opportunity is huge: The World Economic Forum projects the DePIN category will grow to $3.5 trillion by 2028.
The Helium network is the best-known example.
The grassroots wireless network now provides 5G cellular coverage to 1.4 million daily active users across more than 111,000 user-operated hotspots.
184.1K @a16zcrypto @helium Learn more: https://t.co/07uABz5Vxt
488
68
57.4K
5.3K @Jerry_HCcapital Feels like ppl aren’t internalizing how big this shift is. OM1 isn’t just “robots on-chain” it’s the identity, payments, and coordination layer becoming plug-and-play infra. That’s Android moment level. Next step is swarm fleets settling jobs + building rep autonomously. Once that hits scale, the machine economy isn’t a theory anymore, it’s live
1.1K @haixinchao9xxx OpenMind | The OS Where Robots Go On-Chain
I spent this week testing OM1, first on a TurtleBot, then on a Unitree, using the exact same agent config. No edits, no recompile, no friction. It just ran.
FABRIC issued verifiable IDs for both my robot and operator wallet, so task logs, telemetry, and reputation synced seamlessly across hardware. Then x402 linked actions to payments, and the job settled itself on-chain, complete with a transparent audit trail. For the first time, it felt like infrastructure, not a demo.
⚙️ Old Stack vs. OpenMind OS
Old world: siloed fleets, proprietary SDKs, no shared identity or payment rails.
OpenMind world:
• OM1: portable, multimodal brain that runs GPT-4o, Gemini, Claude, Grok across any hardware.
• FABRIC: on-chain identity, trust, and coordination layer that keeps every task verifiable.
• x402: the commerce rail, autonomous micropayments tied to machine actions.
• DIMO alignment: peer-to-peer comms and telemetry for multi-agent coordination.
The result? A shared OS for
12
6
115
112.2K @MHiesboeck $DIMO Reports $800K Token Theft from Development Bridge
On Thursday, November 6, 2025, at approximately 18:30 UTC, the DIMO team discovered an attacker had gained unauthorized access to a developer key, leading to the withdrawal of roughly 30 million DIMO tokens. This amount, valued at about $806,119.50, represents approximately 3% of the total supply.
The exploit specifically targeted a Wormhole bridge contract under development, which was intended to facilitate cross-chain DIMO transfers. The team emphasized that the incident was isolated to the bridge’s deployer key; consequently, the DIMO token, the network, all user accounts, assets, and data remain secure.
Following the breach, the compromised keys were immediately revoked, and all related contracts have undergone a full security review. The DIMO team is currently collaborating with partners and authorities on an ongoing investigation and will provide updates as more information becomes available.
6
1
2.8K
