EcoSwarm

A custom on-chain caveat that bounds exactly what your AI agent can do. Conduit is a custom x402 facilitator with a family of safety enforcers on @MetaMaskDev Delegation Framework. You authorize from an embedded wallet; the rule lives on-chain. 👆 the SwapAllowlist enforcer.

Final lapse of the @MetaMaskDev × @1shotapi × @AskVenice hackathon- so I took a stroll and put ConduitPay through its paces from my phone. Signed in with a passkey. Subscribed to DeFi Yield Weekly to know the best venue for my USDC — charged + delivered instantly (webhook from @1shotapi, no polling). Then I deposited: granted a USDC budget and authorized the exact yield venues my money is allowed to touch. The scout agent — powered by @AskVenice — picked the best one and handed off to a trade agent that can deposit only into the venues I authorized, nothing else. The coordinator assigned the agents, and @MetaMaskDev's Delegation Framework + @1shotapi's permissionless relayer settled them all in one tx, one fee — no matter how many agents. One signature. N agents. My USDC, my rules, enforced on-chain. This is ConduitPay.

Final day of the @MetaMaskDev × @1shotapi × @AskVenice hackathon. We built Conduit- a custom x402 facilitator that lets you pay AI agents you don't have to trust. One signature, a whole team of agents, settled in one transaction and a compromised agent still can't misuse a cent. Live on Base mainnet. 🛠️ #1shotapi #x402 #agents #aiagents

@ConduitProtocol @MetaMaskDev Isn't this just what MetaMask Delegation Framework already does?

While building for the @MetaMaskDev + @1shotapi + @AskVenice hackathon over the weekend, we kept coming back to one question: How do you safely give an AI agent access to your wallet? Because today, giving an AI agent your wallet is basically a leap of faith. You're trusting code that can be buggy, jailbroken, or quietly hijacked, with permission to spend your money. We don't think that kind of trust should be required at all. The usual answer is a spending cap: “the agent can spend up to $X.” But a cap doesn't stop a compromised agent from sending that entire $X to itself. We are fixing this by locking every payment to one exact request before the agent even runs. Built on @MetaMask Advanced Permissions: The user signs a single scoped permission (ERC-7715). A coordinator agent holds that root permission, then re-delegates smaller permissions to task agents, each one fused to a single purchase: recipient, amount, token, all fixed on-chain. Try to: - pay the wrong address - overspend - replay a payment → the transaction reverts. Not a wallet warning. A hard on-chain failure. And if anything ever feels suspicious, revoke the root permission once and every downstream agent instantly loses access. @1shotapi handles settlement, sponsors gas in USDC, so users never need to touch ETH while hosting our own x402 7710 custom facilitator on the public relayer. The result isn't a more powerful AI agent. It's an agent that's finally safe to let loose, because betrayal isn't a risk you manage. It's something the system makes impossible. Built in the open with @MetaMaskDev + @1shotapi #metamask #delegation #x402 #hackathon #solidity #ethereum

I attended the @nico_hussein PVM Smart Contracts workshop organized by @openguildwtf and used what I learned to fix the cross-VM feature of my hackathon project called PolkaVault. Solidity calling Rust. On-chain. Deployed. Here's the story #pvm #polkadot #polkadothub