This is basically @nvidia's nightmare. Sure, you'd be locked to one model, but once this tech lets you burn a strong open-source coding or reasoning model into a $300 chip, why would anyone stick with pay-per-token? You get instant answers, total privacy, offline with no cloud dependency. That's literally what's blocking most enterprises from going all-in on AI adoption right now. My prediction, give it a few years and this will be packaged inside our phones.

@openclaw agents forget everything when a session ends. Here is a diagram of how to give it a memory that actually sticks. It wires up Mem0 local Qdrant as a fully self-hosted (or via openrouter), privacy-first memory layer that persists across restarts, extracts atomic facts from your conversations, and recalls the right context exactly when needed. Your Markdown files stay untouched as the source of truth, while Mem0 handles semantic search on top, all running locally with zero cloud dependency once set up. A self-installing Mem0 Qdrant persistent memory upgrade for OpenClaw. A single command is published on GitHub now, just attach the .md file to your OpenClaw chat, hit send, and it walks itself through the entire setup, detects your OS, paths, and architecture automatically. No manual config hunting required.

Summary of Razvan’s statement re: #DBXEN exploit on Telegram: An exploit occurred affecting the DBXEN staking component, specifically staking rewards and benefits. $DXN mining itself is not affected. The core smart contracts cannot be changed, because DBXEN was designed to be fully immutable: - No admin keys - No upgradeability - No ability to pause or modify contracts Why it happened: The exploit resulted from the interaction between the immutable contract logic and changes in the Ethereum ecosystem over time. New standards like EIP-712 and EIP-2612 introduced off-chain approvals and signature-based transactions, changing how transactions and signatures are handled. Because the contracts were written years ago and cannot be updated, these newer infrastructure changes created an unexpected exploit path that didn’t exist when the protocol was built or audited. Smart contracts are immutable, but the surrounding infrastructure (wallets, signing standards, tools, EIPs) keeps evolving. This mismatch makes it very difficult to predict future security conditions when writing permanent code. Next steps: As per Razvan, his team is continuing to investigate, document the exploit, and they'll communicate updates to the community. -- Note: We've posted a banner on all XEN.PUB DBXEN related pages, informing users about the issue.