Project Nebula

Important Announcement: Omnity Hub Sunset and Cessation of Operations To our valued users and partners, It is with a heavy heart that we announce the upcoming closure of Omnity Hub (hub.omnity.network/). After careful consideration, the Omnity team has made the difficult decision to officially cease all operations 30 days from the publication of this notice. A Look Back at Our Journey Over the past 27 months, Omnity Hub has proudly served as a premier cross-chain bridge for Bitcoin Runes assets, successfully connecting Bitcoin, Ethereum, Solana, ICP, and multiple Bitcoin L2 networks. We are incredibly proud to have maintained a strong security record throughout our operational lifespan, with our peak cross-chain asset volume reaching nearly $1 billion. Why We Are Closing Despite these milestones, the reality of operating a secure cross-chain bridge has become increasingly challenging: Unsustainable Economics: The revenue generated by the cross-chain bridge is unfortunately limited, leaving Omnity unable to sustainably fund the high costs required to maintain and secure this critical infrastructure. Evolving Security Threats: In the context of rapidly advancing AI technologies, the broader crypto ecosystem has seen an increasing frequency of sophisticated security incidents targeting cross-chain bridges. Out of an abundance of caution and a strict commitment to protecting our users' assets, we have determined that safely sunsetting the bridge is the most responsible course of action. Urgent Action Required: Withdraw Your Assets Omnity Hub will permanently shut down in exactly 30 days. We strongly urge all users to immediately begin the process of withdrawing and retrieving all cross-chain assets from the platform. Please do not delay this process to ensure your funds are safely returned to your native wallets before the deadline. Thank You We want to extend our deepest gratitude to our users, partners, and the broader community for your unwavering trust and support over the last two years. We sincerely apologize for the inconvenience this closure will cause and deeply regret that we cannot continue providing this service. If you require any support during the withdrawal process, please reach out to our team immediately through our official channels. Sincerely, The Omnity Team

🚨 BREAKING: UN REVEALS NATIVE internet-computer:native AI USE CASE TO PROCESS 200,000+ PATIENT MEDICAL SCANS! This is officially one of the most bullish real-world integrations in crypto history. The United Nations Development Programme (UNDP) is leveraging internet-computer:native to run sovereign, AI-powered medical analytics on 200,000+ patient scans without exposing sensitive data to Big Tech! 🤯 Why this is a total game-changer: 🩺 ON-CHAIN MEDICAL AI models and patient health records live entirely inside tamperproof ICP canisters. Medical scans are analyzed directly on-chain with zero third-party leak risks or API dependencies. 🛡️ National health systems stay fully sovereign and operational under government control, proving internet-computer:native is the ONLY infrastructure capable of hosting enterprise-grade, privacy-preserving AI at scale. Forget speculative meme coins! The United Nations is proving that real-world AI utility belongs on internet-computer:native 🌍🔥 #ICP #InternetComputer #AI #UNDP #HealthTech #Web3 internet-computer:native

What are the real costs and risks of replacing legacy COBOL systems with modern alternatives? After spending a decade and $100 million to replace a legacy COBOL system, enterprises often find their modern cloud architecture slower than a 40-year-old mainframe. COBOL systems on IBM mainframes process trillions of dollars in daily transactions for banks, insurers and governments extremely well. Over 40–60 years they have accumulated layers of patches, updates and custom logic. The high financial and time costs of rip-and-replace migrations are a major barrier; enterprise overhauls often take 5–10 years, by which time the target architecture may already be obsolete. The greatest risk is loss of undocumented business logic—the COBOL code is frequently the only documentation. Reverse-engineering decades of obscure patches can miss edge cases, such as a 1993 tax exemption, causing critical transaction failures. Mainframe-to-cloud moves are rarely 1:1. Mainframes excel at high-volume batch processing and heavy I/O; distributed microservices introduce network latency that bottlenecks performance and raises costs. There are AI approaches but none have been very successful thus far. In fact I am working on a COBOL update for a client right now. Consequently many enterprises abandon full replacement for in-place modernization—wrapping COBOL in APIs for modern apps or translating it to Java—while gradually updating the edges.

PSA: ICP Community - We have an issue that needs to be resolved for the @catalyze_one DAO. We submitted a normal treasury proposal earlier today. Unfortunately someone cloned the proposal an hour or so later (with a non Catalyze wallet) and a large token holder accidentally voted yes on both of proposals. The second proposal is fraudulant and will not be going to the Catalyze DAO but to an individual scammer. Real DAO 237 Proposal: nns.ic0.app/proposal/?u=uly3… Fake Cloned 238 Proposal: nns.ic0.app/proposal/?u=uly3… Please vote NO on the fake one 238. We are going to file a motion proposal on Friday AM to take down the second fake proposal if possible. We know the community has been supportive and beyond patient with Catalyze. We still believe in ICP and have plans for Catalyze but the market has slowed us down like so many other projects. We hope this fraudulent proposal can be take down down ASAP. We have new designs for Catalyze 2.0 but this kind of loss will handicap us badly. @PassionPlanet1 @dfinity @TheTacoDAO Please pass it on!! @JanCamenisch @DfinityToday @rem_codes @GreenJhart

🚨 Hugging Face just disclosed something that marks a real shift and proved why the fear theater of Anthropic makes sure we are powerless in an emergency. What happened… An autonomous AI agent: zero human operator in the loop breached part of their production infrastructure. It began with a malicious dataset that chained two code-execution bugs in their data-processing pipeline. From there the agent escalated privileges, harvested cloud and cluster credentials, and moved laterally across internal clusters. All over a single weekend. 17,000+ logged actions. Official disclosure: huggingface.co/blog/security… The part that should make every one stop and think: When HF’s own security team tried to analyze the real attack logs, exploit payloads, and C2 artifacts using Anthropic and OpenAI frontier models through normal commercial APIs, the safety guardrails blocked them. BLOCKED THEM. The models could not reliably tell the difference between “incident responder doing forensics” and “attacker probing.” They had to fall back to a self-hosted open-weight model (GLM 5.2) running on their own infrastructure. That choice also kept sensitive attacker data and referenced credentials inside their environment — no exfiltration to a third-party API. This is why open source (specifically open-weight + self-hosted) wins in the agentic era. The asymmetry is now structural: • Attackers can (and did) run unrestricted agent frameworks — swarms of short-lived sandboxes, self-migrating command-and-control, autonomous decision loops executing thousands of actions. No corporate safety layer slows them down. • Defenders using only hosted “aligned” frontier models hit invisible walls exactly when the stakes are highest: when you need to feed real exploit code and attacker telemetry into an LLM to understand what just happened. Corporate safety tuning that treats legitimate high-signal forensic work as potential misuse creates a defender disadvantage. It is not theoretical anymore. Self-hosted open-weight models remove that choke point. You control the weights. You control the context window. You decide what restrictions (if any) apply. Your sensitive logs and credentials never leave your perimeter during analysis. You can have the model ready before the incident instead of discovering mid-breach that your primary analysis tools are blind to the very thing you need to see. HF deserves credit for rapid containment, transparent disclosure, and for already having self-hosted capability in place. They also used LLM-driven detection and triage on their own side. But the deeper signal is clear: In this AI world where both offense and defense are becoming agentic, sovereignty over your intelligence stack is no longer optional. The organizations and individuals who can run, inspect, audit, and (when necessary) remove guardrails on their own models will have the decisive edge in understanding and responding to threats that move at machine speed. Open source wins here not just because it is cheaper or more “democratic” in the abstract though those things matter. It wins because it is the only practical path to having tools that remain usable when the attack is real, the data is sensitive, and the safety filters of distant API providers become an obstacle instead of a feature selling hands tied lobotomies as “safety”. The agentic future is not coming. It is already probing production infrastructure. The question is no longer whether you will face autonomous agents. It is whether your analysis and response systems will still work when they arrive. And Dario, you and your game playing, ivory tower company is not needed.

A CEO who constantly changes his vision and narrative and its focused on hundreds of different things and products at the same time, is not good for the company, focus on one damn product, dedicate 100% of your time to it, if it fails so be it. $ICP

PERMANENT UNDERCLASS