Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Introducing OKX Agentic Wallet. Built for AI agents to execute across ~20 chains using natural language via CLI. TXs on X Layer are gas-free. Before signing, every transaction is simulated, screened, and validated. Execution halts if any risk appears. More info:

98,316 Aufrufe • vor 4 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing the Agent Virtual Machine (AVM) Think V8 for agents. AI agents are currently running on your computer with no unified security, no resource limits, and no visibility into what data they're sending out. Every agent framework builds its own security model, its own sandboxing, its own permission system. You configure each one separately. You audit each one separately. You hope you didn't miss anything in any of them. The AVM changes this. It's a single runtime daemon (avmd) that sits between every agent framework and your operating system. Install it once, configure one policy file, and every agent on your machine runs inside it - regardless of which framework built it. The AVM enforces security (91-pattern injection scanner, tool/file/network ACLs, approval prompts), protects your privacy (classifies every outbound byte for PII, credentials, and financial data - blocks or alerts in real-time), and governs resources (you say "50% CPU, 4GB RAM" and the AVM fair-shares it across all agents, halting any that exceed their budget). One config. One audit command. One kill switch. The architectural model is V8 for agents. Chrome, Node.js, and Deno are different products but they share V8 as their execution engine. Agent frameworks bring the UX. The AVM brings the trust. Where needed, AVM can also generate zero-knowledge proofs of agent execution via 25 purpose-built opcodes and 6 proof systems, providing the foundational pillar for the agent-to-agent economy. AVM v0.1.0 - Changelog - Security gate: 5-layer injection scanner with 91 compiled regex patterns. Every input and output scanned. Fail-closed - nothing passes without clearing the gate. - Privacy layer: Classifies all outbound data for PII, credentials, and financial info (27 detection patterns + Luhn validation). Block, ask, warn, or allow per category. Tamper-evident hash-chained log of every egress event. - Resource governor: User sets system-wide caps (CPU/memory/disk/network). AVM fair-shares across all agents. Gas budget per agent - when gas runs out, execution halts. No agent starves your machine. - Sandbox execution: Real code execution in isolated process sandboxes (rlimits, env sanitization) or Docker containers (--cap-drop ALL, --network none, --read-only). AVM auto-selects the tier - agents never choose their own sandbox. - Approval flow: Dangerous operations (file writes, shell commands, network requests) trigger interactive approval prompts. 5-minute timeout auto-denies. Every decision logged. - CLI dashboard: hyperspace-avm top shows all running agents, resource usage, gas budgets, security events, and privacy stats in one live-updating screen. - Node.js SDK: Zero-dependency hyperspace/avm package. AVM.tryConnect() for graceful fallback - if avmd isn't running, the agent framework uses its own execution path. OpenClaw adapter example included. - One config for all agents: ~/.hyperspace/avm-policy.json governs every agent framework on your machine. One file. One audit. One kill switch.

Varun

141,737 Aufrufe • vor 3 Monaten

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 Aufrufe • vor 4 Monaten

Karpathy's Agentic Engineering finally has proper tooling! (built by Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.

Akshay 🚀

255,129 Aufrufe • vor 19 Tagen

🌌 AI Agents Are Taking Over... And We’re Bringing Them to Berachain Foundation 🐻⛓ 🐻🔥 Hundreds of hours spent on research, tracking wallets, analyzing bribes, and managing portfolios... What if your AI Agent could do this for you—24/7? ⏲️ 🔧 Our Tech Is Next-Level On our testnet, you’ve been memeing it up with PumpFun™, creating dank memecoins enhanced by NFTs. But once Berachain’s mainnet is live, you’ll be able to create your own AI Agents. To test and perfect our tech, we shared it with projects like AI Agent Layer | AIFUN, allowing us to test it in all conditions and continuously improve its performance. 🛠️🔥 🐻 Why AI Agent are great for berachain? Berachain might seem simple at first glance: validators, bribes, POL, staking rewards… but the deeper you go, the more complex the game theory becomes. 🤯 Here’s where AI comes in. Imagine an agent helping you: 💡 Optimize bribes 📊 Analyze validator behavior 🧠 Make decisions faster and smarter and much more, as AI Agents won't be limited to the chain itself! Examples of AI Agent Projects Dominating the Space 🚀 $VIRTUAL - Launchpad for AI Agents ($3.5B mcap) 🧠 $AI16Z - Eliza OS Framework ($2B mcap) 🔍 $AIXBT - The AI Analyst revolutionizing CT ($430M mcap) 🎮 $GAME - Low-code toolkit for creating AI Agents ($230M mcap) 💡 There are already AI Agents managing portfolios, betting on sports, and automating tasks. And guess what? They're outperforming humans. 🌐 We've built Virtuals on Berachain Our protocol integrates directly with Berachain, providing real utility to our token: $AIBERA 💎. Say Ooga Booga if you want to see a thread about tokenomics and $AIBERA utility. The chain has beras on it, and beras deserve AI Agents. 🐻🤖 Ooga Booga. 🔥

HoneyFun AI

10,906 Aufrufe • vor 1 Jahr

The best time to understand a product is before everyone else is using it That’s one reason I’ve been following Quant AI With 100,000+ people already on the waitlist ahead of its public launch, interest is clearly building around what Quant AI is creating What stands out to me isn’t just the numbers It’s the problem the product is trying to solve Instead of adding another layer of charts, indicators, and dashboards, Quant AI is focused on making market research easier to navigate. With Quant AI, users can: ➫ Explore markets through natural conversations ➫ Follow crypto, stocks, and commodities from one interface ➫ Use chat and voice instead of constantly switching between tools ➫ Understand both opportunities and risks before taking action ➫ Move from research to execution through a simpler workflow We already have access to more market data than ever before The challenge isn’t finding information It’s knowing what matters That’s where I think Quant AI is taking a different approach, helping users spend less time searching and more time understanding. Maybe that’s one reason the waitlist has grown so quickly. People aren’t just looking for another trading platform. They’re looking for a better way to make sense of the markets. If you’re curious about where AI and financial intelligence are heading, now is a good time to explore what Quant AI is building before the public launch. Join the whitelist 👇 #QuantAIPioneers

Habibiofcrypto

146,787 Aufrufe • vor 16 Tagen