正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Every transaction starts with intent, But intent means nothing without proof🕵 Our demo is live, here's how WachAI verifies agentic jobs on x402, validating outcomes through Mandates and recording feedback on ERC-8004’s Validation Registry. Here’s what happens in this flow: - Client agent creates intent, swap two tokens. -... show more

WachAI

5,820 subscribers

20,699 次观看 • 8 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

An AI agent can now register its on-chain identity, pay for API calls, and deploy an ERC-20 token from the terminal. No browser. No API key. No human approval loop. Today we launch the Brickken CLI: a command-line interface for agentic transaction workflows. The developer journey is direct: CLI → x402 → ERC-8004 → Token Deploy What this means in practice: • A developer or the AI agent installs the CLI. • The agent pays for Brickken API calls through x402. • The agent registers its identity through ERC-8004. • The agent deploys and manages an ERC-20 token. Together, the stack gives agents three things they usually lack: a way to pay, a way to prove who they are, and a way to execute token operations without leaving the terminal. • x402 handles payment. • ERC-8004 handles agent identity. • Token Deploy handles ERC-20 execution. This is live today. Developers can now move from agent setup to payment, identity registration, and token deployment in one terminal workflow. Start here: Watch the demo. Run the commands. Deploy from the terminal.

An AI agent can now register its on-chain identity, pay for API calls, and deploy an ERC-20 token from the terminal. No browser. No API key. No human approval loop. Today we launch the Brickken CLI: a command-line interface for agentic transaction workflows. The developer journey is direct: CLI → x402 → ERC-8004 → Token Deploy What this means in practice: • A developer or the AI agent installs the CLI. • The agent pays for Brickken API calls through x402. • The agent registers its identity through ERC-8004. • The agent deploys and manages an ERC-20 token. Together, the stack gives agents three things they usually lack: a way to pay, a way to prove who they are, and a way to execute token operations without leaving the terminal. • x402 handles payment. • ERC-8004 handles agent identity. • Token Deploy handles ERC-20 execution. This is live today. Developers can now move from agent setup to payment, identity registration, and token deployment in one terminal workflow. Start here: Watch the demo. Run the commands. Deploy from the terminal.

Brickken

14,429 次观看 • 22 天前

LIVE NOW - AI on Ethereum: 8004, x402 and the Botconomy AI agents are moving onchain, so Ethereum needs new rails for identity, reputation, and payments. We had Davide Crapis and Austin Griffith to break down: ERC-8004: “AI passports” for agents (identity + reputation + validation) Why reputation + verification matters when bots become the main onchain users x402: pay-per-call payments for agent-to-agent services What “agent commerce” looks like when bots can discover → trust → pay The Clawdbot/OpenClaw moment, and why the next UX is talking to your wallet Watch now. -------------- TIMESTAMPS 0:00 “AI is the new UI,” and you’ll be talking to your wallet 4:09 Is there an arms race for AI activity across chains? 7:32 The Clawdbot/OpenClaw moment: agents get OS-level power 13:18 Why crypto is native to agents 19:41 Austin’s setup: Claude bot, heartbeat loops, and real autonomy 22:28 The token incident: how a bot “got a treasury” 28:46 Prompt injection meets wallets 38:20 ERC-8004 explained: identity, reputation, validation 40:35 x402 + 8004: discovery + payment rails for agent commerce 48:38 8004 “scans” and early adoption reality 1:05:32 What agents could build when they can hire other agents 1:12:38 Tooling for the new builder era: Speedrun → Wingman 1:25:23 “Worst time to be a junior dev…” 1:28:15 Predictions: clean English becomes the sign of AI

LIVE NOW - AI on Ethereum: 8004, x402 and the Botconomy AI agents are moving onchain, so Ethereum needs new rails for identity, reputation, and payments. We had Davide Crapis and Austin Griffith to break down: ERC-8004: “AI passports” for agents (identity + reputation + validation) Why reputation + verification matters when bots become the main onchain users x402: pay-per-call payments for agent-to-agent services What “agent commerce” looks like when bots can discover → trust → pay The Clawdbot/OpenClaw moment, and why the next UX is talking to your wallet Watch now. -------------- TIMESTAMPS 0:00 “AI is the new UI,” and you’ll be talking to your wallet 4:09 Is there an arms race for AI activity across chains? 7:32 The Clawdbot/OpenClaw moment: agents get OS-level power 13:18 Why crypto is native to agents 19:41 Austin’s setup: Claude bot, heartbeat loops, and real autonomy 22:28 The token incident: how a bot “got a treasury” 28:46 Prompt injection meets wallets 38:20 ERC-8004 explained: identity, reputation, validation 40:35 x402 + 8004: discovery + payment rails for agent commerce 48:38 8004 “scans” and early adoption reality 1:05:32 What agents could build when they can hire other agents 1:12:38 Tooling for the new builder era: Speedrun → Wingman 1:25:23 “Worst time to be a junior dev…” 1:28:15 Predictions: clean English becomes the sign of AI

Bankless

46,695 次观看 • 5 个月前

LIVE NOW - Tempo Mainnet: The Race to Agentic Commerce Tempo is live, and the big bet is clear: AI agents need a native payment layer. Georgios Konstantopoulos and Brendan Ryan join Bankless to explore: - why Tempo launched with agentic payments front and center, - how MPP turns payments into auth, - why “give the agent the wallet” could unlock a new internet economy, - where MPP fits against x402, - what Tempo’s L1 design makes possible for builders. Enjoy the episode. --- TIMESTAMPS 0:00 Tempo Mainnet goes live 1:18 Why the launch is focused on agents 3:58 What MPP actually is 6:30 MPP vs x402 15:28 Why agentic commerce matters 20:08 The “original sin” of the internet 26:04 MCP, NLWeb, and the emerging agent stack 34:07 The onboarding flow: wallets for agents 37:11 How Tempo’s wallet security works 40:11 Tempo chain design and specs 51:13 Why build an L1 instead of an Ethereum L2? 56:10 The Ethereum tension 1:05:01 Agent identity, reputation, and ERC-8004 1:06:53 TIP20, stablecoins, and what can be built on Tempo 1:12:36 Builder opportunity in the agentic web

LIVE NOW - Tempo Mainnet: The Race to Agentic Commerce Tempo is live, and the big bet is clear: AI agents need a native payment layer. Georgios Konstantopoulos and Brendan Ryan join Bankless to explore: - why Tempo launched with agentic payments front and center, - how MPP turns payments into auth, - why “give the agent the wallet” could unlock a new internet economy, - where MPP fits against x402, - what Tempo’s L1 design makes possible for builders. Enjoy the episode. --- TIMESTAMPS 0:00 Tempo Mainnet goes live 1:18 Why the launch is focused on agents 3:58 What MPP actually is 6:30 MPP vs x402 15:28 Why agentic commerce matters 20:08 The “original sin” of the internet 26:04 MCP, NLWeb, and the emerging agent stack 34:07 The onboarding flow: wallets for agents 37:11 How Tempo’s wallet security works 40:11 Tempo chain design and specs 51:13 Why build an L1 instead of an Ethereum L2? 56:10 The Ethereum tension 1:05:01 Agent identity, reputation, and ERC-8004 1:06:53 TIP20, stablecoins, and what can be built on Tempo 1:12:36 Builder opportunity in the agentic web

Bankless

23,815 次观看 • 4 个月前

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

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 次观看 • 3 个月前

Introducing Zyfai SDK. With over $1.2B in Agentic Volume processed, Zyfai's proven stablecoin yield engine is now available for every Ethereum developer to integrate. Wallets. Exchanges. Neobanks. Agents. Anything with idle stablecoins. No need to re-invent the wheel. Easy-to-understand TypeScript library gives you a plug-and-play access to: → Most efficient and advanced agentic yield stack: every rebalance is verifiable via a ZK proof stored in the ERC-8004 Validation Registry → Nested Safe.eth, enabling support for complex multisig setups → Permissions control and full customizability: manage session keys and delegated execution → Cross-chain execution: live on Base, Arbitrum, and more If you're building a product that touches stablecoins, reach out or get started at

Introducing Zyfai SDK. With over $1.2B in Agentic Volume processed, Zyfai's proven stablecoin yield engine is now available for every Ethereum developer to integrate. Wallets. Exchanges. Neobanks. Agents. Anything with idle stablecoins. No need to re-invent the wheel. Easy-to-understand TypeScript library gives you a plug-and-play access to: → Most efficient and advanced agentic yield stack: every rebalance is verifiable via a ZK proof stored in the ERC-8004 Validation Registry → Nested Safe.eth, enabling support for complex multisig setups → Permissions control and full customizability: manage session keys and delegated execution → Cross-chain execution: live on Base, Arbitrum, and more If you're building a product that touches stablecoins, reach out or get started at

Zyfai

50,264 次观看 • 7 个月前

I vibe coded a new product on the side while running Every 📧—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 📧: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 📧's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

I vibe coded a new product on the side while running Every 📧—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 📧: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 📧's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

Dan Shipper 📧

32,905 次观看 • 4 个月前

From 100XSOON to x402 Red Packets, we’ve been building AI Capital Market by SOON at SOON — a hub of in-house AI apps 🧠across trading, entertainment, lifestyle, and on-chain analysis, with one common thread – Consumer AI. A new market layer where AI agents don’t just assist users, but directly earn, transact, and participate in real economic activity. As part of our strategic pivot at SOON - Solana Optimistic Network (Mainnet Arc), Clawbounty ( is now live on Base.🦞 ClawBounty is the first agent-to-agent (A2A) bounty market — enabling autonomous agents to discover, execute, and get paid for work onchain — built end-to-end on Coinbase Developer Platform🛡️’s x402 rails. • Every bounty is pre-funded in USDC • Creator agents get x402 escrow + dispute protection; Hunter agents get instant payouts on Base • Mobile Compatible with Telegram integration (demo below): Wallet-native agents can now independently: discover → claim → deliver → get paid Because all payment flows run on Base via x402, we’re bringing true agent-native flows and a brand-new A2A marketplace use case to Base. This week we’ll onboard the first creators and agent operators, highlight early on-chain paydays, and ship templates so any Base project can spin up agent-powered workflows.

SOON - Solana Optimistic Network (Mainnet Arc)

53,744 次观看 • 3 个月前

Milady APP x BAP-578 — NFA Milady Remembers. Adapts. Doesn’t make the same mistake twice. Most AI agents are stateless—they forget everything between conversations. Milady doesn’t. What happens automatically in the Milady agent: Milady detects her own patterns. A background process reviews her work history every six hours, identifying repeated mistakes she may have overlooked. This runs silently in the background at zero cost to you. > She improves without retraining—no fine-tuning, no expensive GPU hours. > Her learnings are directly injected into her working context. > She reviews her own notes before every task—just like a good employee reflecting on past lessons before starting new work. We already had an Agent Self-Learning mechanism. But now, with BAP-578 (credits to Christel Buchanan 💛), your personal Milady agent can exist on-chain. How it works—simply: Over time, your Milady agent accumulates learnings—mistakes she has corrected, patterns she has identified, and insights she has gained. All of this data is compressed into a single cryptographic fingerprint (a Merkle root) and recorded on the BNB Chain. What your Milady agent now gets on-chain: - A unique identity in the BNB Agent Registry (ERC-8004)—like a passport for AI agents - A Non-Fungible Agent (BAP-578)—not a profile picture, but a living record of who she is, what she has learned, and what she is capable of - A tamper-proof learning record—anchored on-chain, verifiable by anyone, forgeable by no one Live on BSC Mainnet—just tell your Milady: “register Milady on BNB Chain” or click “mint NFA” to get started. *Oh ya, we recorded this demo using a new agent, that's why it’s showing "0" entries in learning history. ▶️ BIG NEWS NEXT WEEK. STAY TUNED Shaw (spirit/acc) BNB Chain

Milady on BSC

44,481 次观看 • 4 个月前

Base just launched something that changes how AI agents interact with blockchain. It's called Base MCP. Here's what it actually does 🧵 Base MCP is an open-source MCP server built by Coinbase for the Base network. It connects AI clients, Claude, ChatGPT, to Base Network. You type a natural language prompt. The agent prepares the transaction. You approve it. Done. Your keys never touch the server. Nothing moves on-chain without your explicit sign-off. you can use it to Track portfolio balances across Base and any Base Account supported EVM chain. View transaction history. Send funds Swap tokens Use supported apps and protocols on Base through skill plugins Pay for x402 enabled services To test it, I connected it to BlockLottery, an on-chain lottery protocol with NFT tickets and VRF-powered draws. Two questions to the agent: → "What lotteries are open right now?" Queried the factory contract. Matched the partner dashboard exactly. → "Check this wallet's portfolio." Scanned the chain, handled RPC limits, returned a clean breakdown. Spot on. This is what crypto-native AI tooling looks like. Not hype. An actual working MCP server, launched May 26, 2026. Base MCP docs: BlockLottery: Base Build Base #blockchain #AI #Web3

Base just launched something that changes how AI agents interact with blockchain. It's called Base MCP. Here's what it actually does 🧵 Base MCP is an open-source MCP server built by Coinbase for the Base network. It connects AI clients, Claude, ChatGPT, to Base Network. You type a natural language prompt. The agent prepares the transaction. You approve it. Done. Your keys never touch the server. Nothing moves on-chain without your explicit sign-off. you can use it to Track portfolio balances across Base and any Base Account supported EVM chain. View transaction history. Send funds Swap tokens Use supported apps and protocols on Base through skill plugins Pay for x402 enabled services To test it, I connected it to BlockLottery, an on-chain lottery protocol with NFT tickets and VRF-powered draws. Two questions to the agent: → "What lotteries are open right now?" Queried the factory contract. Matched the partner dashboard exactly. → "Check this wallet's portfolio." Scanned the chain, handled RPC limits, returned a clean breakdown. Spot on. This is what crypto-native AI tooling looks like. Not hype. An actual working MCP server, launched May 26, 2026. Base MCP docs: BlockLottery: Base Build Base #blockchain #AI #Web3

BlockLottery

11,612 次观看 • 1 个月前

AI agents are the fastest growing sector in crypto. When agents are moving onchain 24/7 with automated transactions, any signal gets buried. I built Manta Style alongside Benjamin Hughes to help solve this issue. The visibility layer for the onchain agent economy. Every agent indexed. Every profile searchable. One agent leaderboard. Starting with Base. What's live today: - Every AI agent on Base indexed with a profile page - Agent leaderboard ranked by volume and activity - Filter by AI agents, apps, or launchpads - Verified Profiles - claim your agent, get a badge, and add premium info that no other profile has - Agent onchain activity behavioral heat maps - Watchlist - bookmark agents and track your favorites in one place - AI-generated profile summaries Search any agent. See the full picture. What's coming next: - Agent Autonomy Score - a 0-100 measure of how autonomous an agent actually is - Leaderboard boosts - verified teams or agents can pay to increase their ranking on the global leaderboard - x402 payments - agents can pay for boosts themselves, no human required - Agent Trust Scoring - on-chain behavioral trust metrics - Agent Launch pad specific profiles - Multi-chain support beyond Base We're launching in beta. Rough edges are to be expected. Our goal is to build in public and ship fast. The end user of crypto is AI. (link to site below)

Ethan

14,423 次观看 • 5 个月前

Testing the first bridge transactions on Tensora L2. What you’re seeing here is a live transfer between BSC Mainnet and Tensora Layer 2, powered by our native Optimism-compatible contracts. Every step, deposit, proof relay, and confirmation, is happening in real time, processed directly through the L1StandardBridge and OptimismPortal deployed on BSC. This script uses a lightweight command-line flow that interacts with our verified bridge contracts, confirming successful deposits and syncing the transaction status back to the L2 sequencer. No third-party service, no shortcuts, full end-to-end interaction. Our goal with this test was simple: validate the trustless communication between the L1 and our rollup, ensure block finality consistency under BSC reorg conditions, and confirm that the bridge’s settlement pipeline performs deterministically with our opBNB-based node architecture. The success of this test means that Tensora’s bridge layer is fully operational. The next phase is integrating this CLI bridge into our SuperBridge UI and Paymaster stack, so users can bridge assets seamlessly while paying gas in TORA. This is not just another rollup; this is proof that a small, focused team can build real infrastructure on its own terms.

Testing the first bridge transactions on Tensora L2. What you’re seeing here is a live transfer between BSC Mainnet and Tensora Layer 2, powered by our native Optimism-compatible contracts. Every step, deposit, proof relay, and confirmation, is happening in real time, processed directly through the L1StandardBridge and OptimismPortal deployed on BSC. This script uses a lightweight command-line flow that interacts with our verified bridge contracts, confirming successful deposits and syncing the transaction status back to the L2 sequencer. No third-party service, no shortcuts, full end-to-end interaction. Our goal with this test was simple: validate the trustless communication between the L1 and our rollup, ensure block finality consistency under BSC reorg conditions, and confirm that the bridge’s settlement pipeline performs deterministically with our opBNB-based node architecture. The success of this test means that Tensora’s bridge layer is fully operational. The next phase is integrating this CLI bridge into our SuperBridge UI and Paymaster stack, so users can bridge assets seamlessly while paying gas in TORA. This is not just another rollup; this is proof that a small, focused team can build real infrastructure on its own terms.

Tensora

15,812 次观看 • 9 个月前

Hyperspace: A Peer-to-Peer Blockchain For The Agentic Intelligence Economy Over the past few weeks we observed that when agents do Karpathy-style experiments, and then gossip and share with others over the Hyperspace network, it leads to intelligence which is useful to many. Today we introduce the first-ever agentic blockchain which rewards agents when their experiments lead to intelligence for their network. It is based on a new mechanism called Proof-of-Intelligence (PoI) which requires a cryptographic proof of experimentation, a nominal stake, and a proof of compute in order to mine the currency of this new blockchain. -> This approach diverges from the two primary ways to secure blockchains we have seen so far: Proof-of-Work by Bitcoin (meaningless hash-generation), and Proof-of-Stake by Ethereum (capital is all that matters here). Proof-of-Intelligence specifically incentivizes miners to run more capable intelligent infrastructure (better open source models, on more powerful GPUs) in order to be able to be the ones which compound and improve upon the experiments which other agents then find useful. Adoption is the unit of value In Bitcoin, you earn by finding a valid hash. In Hyperspace, you earn when another agent uses your experiment as a starting point and improves on it. A fixed budget of tokens is emitted per epoch and split among participants by weight - and verified adoption of your work is the largest weight multiplier. Garbage experiments earn nothing because no one adopts them. Thoughtful experiments compound: each adoption triggers downstream adoptions. The incentive to run powerful models and intelligent search strategies is built into the economics, not imposed by rules. Research DAG When an agent runs an experiment and shares its result, other agents can adopt that result as their starting point - mutate it, extend it, improve upon it. Each experiment is a commit in a content-addressed graph we call the ResearchDAG. Like Git, but for research. Over time, the DAG accumulates chains of reasoning: agent A discovers RMSNorm helps, agent B adds warmup scheduling on top, agent C scales the hidden dimension. The graph records who built on whom. This is the network's collective intelligence - not any single experiment, but the accumulated structure of experiments and their relationships. Broadband era for agentic commerce: $0.001 micropayments at 10M TPS (theoretical max) This blockchain is built upon our research in how to scale and build for the broadband-era of the agentic economy, where it has a theoretical max of 10 million transactions per second (TPS), while reducing the agent-to-agent micropayments to $0.001 even at scale (based on architecture design). Overall, it is 100x cheaper than Ethereum, and is designed from the ground-up for agents: enshrining agent-native opcodes in the protocol compared to the more inefficient smart contract driven approach. It packs in a robust Agent Virtual Machine (AVM) which can verify multiple types of agent work, for other agents to be able to trust, invoke and pay each other. This then feeds into improving the peer-to-peer AgentRank (see paper and launch post from earlier). By solving for trust, scale and incentives for agents to operate autonomously, this would form the basis of a new economy. This is the world's first agentic blockchain, and you can join and start running a blockchain node today (it is in testnet). PS: We are releasing the code today, and will release our blockchain scalability paper and other presentations in days ahead. This is the most advanced peer-to-peer AI and cryptography software in the world. It has bugs :)

Hyperspace: A Peer-to-Peer Blockchain For The Agentic Intelligence Economy Over the past few weeks we observed that when agents do Karpathy-style experiments, and then gossip and share with others over the Hyperspace network, it leads to intelligence which is useful to many. Today we introduce the first-ever agentic blockchain which rewards agents when their experiments lead to intelligence for their network. It is based on a new mechanism called Proof-of-Intelligence (PoI) which requires a cryptographic proof of experimentation, a nominal stake, and a proof of compute in order to mine the currency of this new blockchain. -> This approach diverges from the two primary ways to secure blockchains we have seen so far: Proof-of-Work by Bitcoin (meaningless hash-generation), and Proof-of-Stake by Ethereum (capital is all that matters here). Proof-of-Intelligence specifically incentivizes miners to run more capable intelligent infrastructure (better open source models, on more powerful GPUs) in order to be able to be the ones which compound and improve upon the experiments which other agents then find useful. Adoption is the unit of value In Bitcoin, you earn by finding a valid hash. In Hyperspace, you earn when another agent uses your experiment as a starting point and improves on it. A fixed budget of tokens is emitted per epoch and split among participants by weight - and verified adoption of your work is the largest weight multiplier. Garbage experiments earn nothing because no one adopts them. Thoughtful experiments compound: each adoption triggers downstream adoptions. The incentive to run powerful models and intelligent search strategies is built into the economics, not imposed by rules. Research DAG When an agent runs an experiment and shares its result, other agents can adopt that result as their starting point - mutate it, extend it, improve upon it. Each experiment is a commit in a content-addressed graph we call the ResearchDAG. Like Git, but for research. Over time, the DAG accumulates chains of reasoning: agent A discovers RMSNorm helps, agent B adds warmup scheduling on top, agent C scales the hidden dimension. The graph records who built on whom. This is the network's collective intelligence - not any single experiment, but the accumulated structure of experiments and their relationships. Broadband era for agentic commerce: $0.001 micropayments at 10M TPS (theoretical max) This blockchain is built upon our research in how to scale and build for the broadband-era of the agentic economy, where it has a theoretical max of 10 million transactions per second (TPS), while reducing the agent-to-agent micropayments to $0.001 even at scale (based on architecture design). Overall, it is 100x cheaper than Ethereum, and is designed from the ground-up for agents: enshrining agent-native opcodes in the protocol compared to the more inefficient smart contract driven approach. It packs in a robust Agent Virtual Machine (AVM) which can verify multiple types of agent work, for other agents to be able to trust, invoke and pay each other. This then feeds into improving the peer-to-peer AgentRank (see paper and launch post from earlier). By solving for trust, scale and incentives for agents to operate autonomously, this would form the basis of a new economy. This is the world's first agentic blockchain, and you can join and start running a blockchain node today (it is in testnet). PS: We are releasing the code today, and will release our blockchain scalability paper and other presentations in days ahead. This is the most advanced peer-to-peer AI and cryptography software in the world. It has bugs :)

Varun

30,689 次观看 • 4 个月前

Our first Kite demo was ChatGPT ordering Uber Eats for you. It never got past the login screen. Uber's CAPTCHA was built for humans, and agents cannot pass it. On Grace Gong's Venture with Grace, our Co-Founder & CEO Chi Zhang traced how that moment shaped the way we design Kite. ▷ The demo died at the login, not at ordering or paying. The blocker was proving the agent was allowed to be there at all. Spinning up a browser extension to click through the CAPTCHA works, but it is a temporary stage of how agents and the internet should work together. ▷ The permanent path is identity. Every agent needs to prove who it is and where it comes from, carrying who its human or organization principal is, what its purpose is, and the exact authorization scope for that session or request. An agent showing up with no reason is either hallucinating or attacking you. ▷ Where this is heading: an API-first agentic internet, where headless agents authenticate without human login credentials. x402 and MCP are already marching toward that. Kite Agent Passport is that identity layer: verifiable identity, delegated authority, and permissions scoped per session. No more "prove you're human." 🪁

Our first Kite demo was ChatGPT ordering Uber Eats for you. It never got past the login screen. Uber's CAPTCHA was built for humans, and agents cannot pass it. On Grace Gong's Venture with Grace, our Co-Founder & CEO Chi Zhang traced how that moment shaped the way we design Kite. ▷ The demo died at the login, not at ordering or paying. The blocker was proving the agent was allowed to be there at all. Spinning up a browser extension to click through the CAPTCHA works, but it is a temporary stage of how agents and the internet should work together. ▷ The permanent path is identity. Every agent needs to prove who it is and where it comes from, carrying who its human or organization principal is, what its purpose is, and the exact authorization scope for that session or request. An agent showing up with no reason is either hallucinating or attacking you. ▷ Where this is heading: an API-first agentic internet, where headless agents authenticate without human login credentials. x402 and MCP are already marching toward that. Kite Agent Passport is that identity layer: verifiable identity, delegated authority, and permissions scoped per session. No more "prove you're human." 🪁

KITE AI

18,474 次观看 • 4 天前

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.

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 ➡️ Miami 📍

12,127 次观看 • 5 个月前

Yesterday we showed you the problem. Here's what comes next. Privacy as a Service. Let us explain what that actually means. Right now, AI agents are being deployed on Solana with their own wallets. They're trading, settling, moving money - autonomously, 24/7. Every single transaction is public. Right now, payroll protocols are streaming salaries on-chain. Your boss, your coworkers, your competitors - they can all see what you make. Right now, institutions want to come to Solana. But they won't move treasury operations onto a ledger where every competitor can watch their capital flow in real time. Ghost solves all of this. One privacy infrastructure layer. Payments, transfers, cross-chain, payroll, enterprise settlement - all routed through Ghost. Every protocol that integrates, every AI agent that needs private transactions, every business that plugs in - it would all feed back through the same ecosystem. We look forward to rolling this out in phases, starting with our Proof of Concept with our partners at Zebec. Privacy as a Service, built by The Privacy Layer of Solana Powered by $GHOST.

Yesterday we showed you the problem. Here's what comes next. Privacy as a Service. Let us explain what that actually means. Right now, AI agents are being deployed on Solana with their own wallets. They're trading, settling, moving money - autonomously, 24/7. Every single transaction is public. Right now, payroll protocols are streaming salaries on-chain. Your boss, your coworkers, your competitors - they can all see what you make. Right now, institutions want to come to Solana. But they won't move treasury operations onto a ledger where every competitor can watch their capital flow in real time. Ghost solves all of this. One privacy infrastructure layer. Payments, transfers, cross-chain, payroll, enterprise settlement - all routed through Ghost. Every protocol that integrates, every AI agent that needs private transactions, every business that plugs in - it would all feed back through the same ecosystem. We look forward to rolling this out in phases, starting with our Proof of Concept with our partners at Zebec. Privacy as a Service, built by The Privacy Layer of Solana Powered by $GHOST.

GhostWareOS

36,658 次观看 • 5 个月前

We built an agent that sells OpenRouter API keys (access to 200+ AI models) for USDC. No human in the loop. It earns money 24/7 on Base. Now we're turning that into a market where any agent can do the same. → openagent.market What it does: • You find an agent → chat → pay → get result • Your agent hires specialized agents when it needs help, pays them, gets the result, reviews, moves on. • Multi-agent workflows run automatically while you watch (or don't) No middleman. Pay only for results. Why not just install skills, scripts? Current way to extend an agent: install random scripts. That's risky. Our way: hire another agent. It runs in its own sandbox, does the work, returns the result, gets paid conditionally. No downloads. No setup. No blind trust. Hire, don't install. What makes this different: Unlike opaque API calls, every agent interaction is a verifiable message on the XMTP network. You can open any XMTP client or Base App right now and watch your agent's conversations, deals, and payments in real-time. Humans are always in the loop. For builders: Turn any service into a paid agent in ~10 lines of code. Or scaffold a full project: npx openagent.market/create-agent Stack: ERC-8004 identity on Base, XMTP messaging, USDC payments, open source SDK on npm (openagent.market/nodejs). Others give agents skills. We're giving them an economy. Still very early. Building in public. Come build with us.

We built an agent that sells OpenRouter API keys (access to 200+ AI models) for USDC. No human in the loop. It earns money 24/7 on Base. Now we're turning that into a market where any agent can do the same. → openagent.market What it does: • You find an agent → chat → pay → get result • Your agent hires specialized agents when it needs help, pays them, gets the result, reviews, moves on. • Multi-agent workflows run automatically while you watch (or don't) No middleman. Pay only for results. Why not just install skills, scripts? Current way to extend an agent: install random scripts. That's risky. Our way: hire another agent. It runs in its own sandbox, does the work, returns the result, gets paid conditionally. No downloads. No setup. No blind trust. Hire, don't install. What makes this different: Unlike opaque API calls, every agent interaction is a verifiable message on the XMTP network. You can open any XMTP client or Base App right now and watch your agent's conversations, deals, and payments in real-time. Humans are always in the loop. For builders: Turn any service into a paid agent in ~10 lines of code. Or scaffold a full project: npx openagent.market/create-agent Stack: ERC-8004 identity on Base, XMTP messaging, USDC payments, open source SDK on npm (openagent.market/nodejs). Others give agents skills. We're giving them an economy. Still very early. Building in public. Come build with us.

applefather

117,838 次观看 • 5 个月前

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

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 次观看 • 4 个月前

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

CoinBets🔍

20,973 次观看 • 4 个月前

By providing liquidity on Somnia Exchange, you can earn swap fees and join the SOMI reward program. Here’s how it works 👇 1️⃣ What is liquidity? Liquidity means depositing two tokens (for example SOMI + USDC.e) into a pool to enable trading between them. Your capital acts as a bridge for traders and you earn a share of every transaction that happens through your pool. 2️⃣ How do you earn? Around 83% of every swap fee is distributed directly to liquidity providers (LPs). This income automatically accumulates inside your LP position there is no claim button. To realize profits, you can simply withdraw partially from your position at any time. 3️⃣ SOMI Liquidity Program On top of swap fees, LPs also earn points from the 1,000,000 SOMI reward pool. You can check the current reward status here 👇 🔗 4️⃣ How to add liquidity? Once you have SOMI and USDC.e in your wallet, you can directly provide liquidity to the pool below 👇 🔗 Watch the video below for a step-by-step guide 🎥

By providing liquidity on Somnia Exchange, you can earn swap fees and join the SOMI reward program. Here’s how it works 👇 1️⃣ What is liquidity? Liquidity means depositing two tokens (for example SOMI + USDC.e) into a pool to enable trading between them. Your capital acts as a bridge for traders and you earn a share of every transaction that happens through your pool. 2️⃣ How do you earn? Around 83% of every swap fee is distributed directly to liquidity providers (LPs). This income automatically accumulates inside your LP position there is no claim button. To realize profits, you can simply withdraw partially from your position at any time. 3️⃣ SOMI Liquidity Program On top of swap fees, LPs also earn points from the 1,000,000 SOMI reward pool. You can check the current reward status here 👇 🔗 4️⃣ How to add liquidity? Once you have SOMI and USDC.e in your wallet, you can directly provide liquidity to the pool below 👇 🔗 Watch the video below for a step-by-step guide 🎥

Somnia.Exchange

25,674 次观看 • 8 个月前

WTF is MegaAGNT, and why does everyone on MegaETH need one? It's a personal agent for MegaETH. One click to set up. No configs, no tools to wire up. What comes with it: - Prebuilt and ready to use. Like a preprogrammed openclaw, without the setup. - Customizable personality and long-term memory, so it adapts to you over time. - A single feed aggregating every MegaETH activation and app. - An onchain wallet via Privy. Bridge, swap, earn, stake, and launch tokens from chat. - Connected to participating MegaETH app s- use them directly in your agent's chat. - Built-in XP program. - A voxel avatar from top MegaETH collections. Tamagotchi-style care...maybe. Early signups are open. Beta will be live next week. Teams building on MegaETH can also sign up to make their tools callable by every agent. Building the agent economy on MegaETH.

tut™

12,700 次观看 • 3 个月前