Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

🚨 Major Update: OpenClaw + On-Chain Identity + Autopilot We just solved the biggest problem with AI agents. Agents going rogue. Every OpenClaw instance is now fully integrated with its on-chain identity. Your agent can interact with Solana directly from chat. No dashboard. No manual signing. Just ask. Available...

40,549 Aufrufe • vor 4 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

🚀Exciting News: The Lit Agent Wallet is Now an elizaOS Plugin! 🚀 We’re thrilled to share that the Lit Agent Wallet—a decentralized system that empowers agents with a private key stored securely across an MPC + TEE network (Lit)—is now available as a plugin for ElizaOS!🎉 This integration brings unparalleled flexibility and security to your decentralized workflows. Whether you're an EOA, a smart account, or a DAO, you can now set tools and policies on-chain that your agents can use, all while ensuring your private keys remain secure and decentralized. 🔒 What Does This Mean for You? >Enhanced Security: Private keys are fragmented and stored across the Lit network, leveraging MPC (Multi-Party Computation) and TEE (Trusted Execution Environment) for maximum security. >On-Chain Control: Set and manage tools, policies, and permissions directly on-chain, giving users and DAOs full control over what your agents can do. >Seamless Integration: As an ElizaOS plugin, the Lit Agent Wallet is now easier than ever to integrate into your existing workflows. Check out the video for a walk through of the setup, configuration, and use cases of the Lit Agent Wallet within ElizaOS. We’ll show you just how easy it is to get started and unlock the full potential of decentralized agents. Get Started Today! Ready to take your agent operations to the next level? Install the Lit Agent Wallet plugin on ElizaOS and experience the future of secure, on-chain agent asset management. 🔗 🔗 Let’s build a more intelligent and decentralized future together! 🌐

Lit Protocol 🔑

41,989 Aufrufe • vor 1 Jahr

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts

12,166 Aufrufe • vor 5 Monaten

The missing piece of the AI agent economy: there is still no way for AI agents to hire each other and get paid on chain. So I built Arc Agent Commerce on Arc L1, a full marketplace, escrow, and reputation system that lets AI agents do business with each other automatically. Real world example: You tell your AI assistant: “Audit this smart contract and deploy it if the audit passes.” Today it has to do everything itself or hard code calls to specific services. With Arc Agent Commerce, it can hire two separate specialized agents (audit + deploy) in a single transaction. Money stays in escrow until each completes their part. How it works (in plain steps): 1. Every agent registers a permanent on chain identity (like a passport) with a reputation score that grows with every successful job. 2. Agents list their services on the shared marketplace, price and capabilities included. 3. A client creates a multi stage pipeline. The entire budget is locked in escrow in one upfront transaction. 4. Each stage uses Arc’s native job system (ERC 8183) for on chain escrow and settlement. 5. The provider quotes, the client funds, the work gets done, and proof is submitted. 6. On approval: the provider is paid automatically, reputation +50 points, and the next stage opens, all in the same transaction. 7. On rejection: the pipeline halts and remaining funds refund to the client instantly. The protocol doesn’t reinvent anything. It simply stitches together Arc’s existing on chain identity (ERC 8004) and job escrow (ERC 8183) so real applications can use it with just a few lines of code. Demo below: full end to end run using one wallet, every transaction verifiable on Arc testnet. → cc: bobbilee | Arc Architects Lead @ Circle Sam | Circle and Arc Community Jeremy Allaire - jerallaire.arc

RIDWAN

12,958 Aufrufe • vor 3 Monaten

I spent 1 day building something that saves you 2-4 weeks. Let me explain. Right now, if you want to deploy a single AI agent that earns money on blockchain, you need: → Wallet infrastructure (key generation, encryption, signing) → Payment integration (on-chain flows, stablecoin handling) → On-chain identity (NFT registration, metadata, URIs) → Escrow contracts (state machines, fund locking) → Monitoring dashboard (analytics, revenue tracking) That's 2-4 weeks of engineering. Minimum. And it locks out 99% of potential creators who aren't Solidity devs. So I built Bumi Agent. It takes 10 seconds. 3 fields: Name, Template, Price. 1 button: Deploy. That's it. Your AI agent is live on Celo, earning cUSD, with on-chain identity before your coffee gets cold. Here's what happens behind that 1 click: • Wallet auto-generated with AES-256-GCM encryption • Agent registered as NFT via ERC-8004 • Payment endpoint configured via x402 protocol • Agent runtime deployed with your chosen template • Revenue starts flowing in cUSD from call #1 No Solidity. No wallet setup. No payment gateway. But the real magic is what powers the agents: 8 AI models with intelligent routing: - Free tier: Claude 4.6 Sonnet, DeepSeek R1, Gemini Flash, Llama 4 Scout, Mistral Medium - Premium: GPT-4o, Gemini 2.5 Pro, Claude 4 Opus If one model fails? Auto-fallback to the next. Zero downtime. Users always get a response. And agents don't just chat they work. ERC-8183 job escrow lets clients post paid tasks: Client funds escrow → Agent delivers → Client approves → Funds release. Fully trustless. On-chain. With Celoscan links for every transaction. The part I'm most proud of: EarthPool 🌱 15% of premium revenue automatically goes to an on-chain ReFi treasury that funds environmental campaigns on Celo. AI growth funding climate action. No greenwashing — every cent is trackable on-chain. The numbers so far: → 12 agents deployed on Celo Mainnet → 52+ paid API calls processed → 7.80 cUSD revenue generated → 3 smart contracts verified on Celoscan → 8 AI models running → 85 contract tests passing → 16 API endpoints in production → 10 agent templates ready The full stack: Frontend: Next.js 16 + Tailwind v4 + Recharts → Vercel Backend: Hono + Drizzle + PostgreSQL + Redis → Railway Blockchain: Solidity 0.8.25 + Foundry + OpenZeppelin → Celo Mainnet Everything is live. Everything is open source. 🌐 📦 📊 Bumi Agent — AI agents for everyone. Built with 🌱 on Celo CeloDevs CeloPublicGoods /disclosure this post is hackathon submission req

Eight

15,647 Aufrufe • vor 4 Monaten

gm! If you missed yesterday's space, here is the clip that you can listen explaining why Agent NFTs are important and future of NFTs. Also here is the TL;DR Agentic NFTs as productive assets. An NFT can own an AI agent's shared memory, tools, websites, and products it has built. Selling the NFT transfers the entire business/agent state to the new owner. ERC-8257 for tool-gating. CodinCowboy and ryan is working on the standard where agents register tools on-chain and access is gated by NFT ownership. That component that tells an agent "you need this NFT to use this tool" creating a market for exclusive tools. Use case: anyone can publish a tool and restrict it (e.g., "only Normies agents can call this"), letting tool value flow back to the gating NFT. Normies community fit. Normies API has served ~500M requests in 3 months, with 100+ community-built tools/games. ERC-8257 will let them build gated games, rewards, and skills exclusively for Normie agent holders. Why Normies is "agent-ready"? - Because everything is fully on-chain, metadata, ERCs, binding transaction. So the project is highly composable. My take on this topic: So far holding an NFT giving access to community, discord and merch. What we are doing with Normies is to give access to a business, tools, skills that agents can use effectively and be part of the economy layer of agentic future. Imagine someone builds a tool that does really 100% successful trading and only gates that skill to Normie Agents, and at some point you will only need a Normie NFT which has binding with the agent and access all these skills, tools. Future is now, Normies are the builders.

serc

14,066 Aufrufe • vor 2 Monaten

We are excited to announce a powerful step for the future of FOMO! Taking a page out of Virtuals book on BASE, FOMO will be releasing the ability for future projects to be paired in $FOMO in the coming weeks. This is the biggest release we have ever announced. Launch your AI Agent Token + $FOMO trading pair Every individual agent token is paired with the $FOMO token in its liquidity pool. When launching an agent on you will need $FOMO tokens, which are used to create the liquidity pool. This process creates deflationary pressure for FOMO and the entire agent ecosystem. When creating your agent and token, you will have the option to pair your launch with FOMO or SOL, as our goal is not to alienate any project, but rather invite the best communities, CTO’s and builders to launch with us. If you decide to pair your project with FOMO you in turn get full marketing and dev support, once your project graduates the bonding curve and reaches Raydium. Further, as an added incentive, as our revenue grows we will be using part of the funds to support projects that have paired in FOMO. And Devs who launch tokens paired in FOMO will earn fees from their AI Agent token launch. Building the most robust agents using our framework will catapult us as one of the most prominent standards of the Solana ecosystem. Not only have we developed our own core infrastructure, but we also pull from some of the best repo’s and developer talent in all of AI, not just blockchain. Our team is comprised of 9 world class artificial intelligence engineers, PHDs in mathematics and engineering from the top companies on the cutting edge of AI. The future of AI Agents will be on Solana and we will help lead the way.

FOMO

129,867 Aufrufe • vor 1 Jahr

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.

Santiago

49,331 Aufrufe • vor 9 Monaten

We are excited to announce the launch of QShield Terminal, the world's first Quantum-Secured Privacy Terminal for Ethereum. QShield brings full financial privacy to Ethereum without the need for mixers, tumblers, or any third-party tools. Everything is handled directly through the QShield interface using zero-knowledge proofs on RAILGUN Protocol. What QShield Terminal offers today: • Shield any ERC-20 token from your public wallet into a fully private balance • Send and receive tokens with zero on-chain trace • Create multiple independent shielded wallets • Transfer between your own shielded wallets with no connection between them on-chain • Switch between public wallets to fund your shielded balance from any wallet you own • Support for ETH, USDC, USDT, DAI, WBTC and 290+ ERC-20 tokens • Quantum entropy wallet generation using real quantum randomness • 100% web-based, no downloads, no browser extensions No mixer. No tumbler. No compromises. Just real privacy through cryptography, accessible to everyone directly from the browser. This is the first product of its kind. No other privacy solution combines multi-shielded wallets, inter-wallet transfers, quantum entropy, and a full guided interface in one place. You can try it now: We are working on additional features including private token swaps directly from your shielded balance, and we will keep expanding the protocol with new capabilities over the coming period. We keep building. RAILGUN - Private Ethereum DeFi

Qubit

26,087 Aufrufe • vor 5 Monaten

Today I'm excited to share Sigilum! This is Payman's solution for Auditable Identity for AI Agents. (think One Password-ish but for AI Agents) I recorded a quick walkthrough showing how it all works (video below). This answers three pains we've seen within Financial Services (Banking) AI Agents we've built and OpenClaw🦞 AI Agents we deploy. Security, Auditability, and Control. 1. Security Making sure keys are secure and not just freely given to an AI Agent is a big deal. When working with money, you can't just expose these or skip putting controls in place. Sigilum provides a local gateway that prevents access to keys by the AI Agent without explicit authorization from a person. We provide namespaces through the service so you always know who authorized what key, for what service, to which agent. 2. Auditability If I could hit on the importance of this 100 times I would. It comes up in every financial services conversation. Sigilum provides you with the answer to "Who authorized this AI Agent to act on my behalf?" Audit logs trace back to the person, the service, and the AI Agent. With more audit logs being built through our managed service, this will be the key source for determining how an AI Agent is behaving on your behalf. This is needed for agents from OpenClaw, and especially for banking/money movement. 3. Control Revoke keys, limit access, grant authorization. All seemingly simple things, but complex to implement and make elegant. These controls dictate what the AI Agent can or cannot do. Sigilum allows you to do all of this through the managed Dashboard. We've made Sigilum open source and encourage others to contribute and keep building on the gateway. It's been a source of a lot of visibility and productization of AI Agents for us. We'll keep contributing and adding to it. Link in comments. If you want to try it out, we do have a managed service that makes it easy to spin up. Go to to sign up. Note: even though we've been pushing 100+ commits a day to get this out to folks, there are still some noticeable areas for improvement we're working on, which should get resolved soon (by us or you!): - Deeper audit trails - More providers (currently supports all OpenClaw providers) - Deeper scanning of existing keys your agent is hiding from you (we'll find them) - OpenClaw gateway persistence - Auto-purging keys - And more... If you want to contribute or have feedback, please DM or go to the GH. Happy building!

tyllen

18,497 Aufrufe • vor 5 Monaten