ForkFi @ForkFiLab

Final day of the @MetaMaskDev x @1shotapi x @AskVenice Cook-Off. 🚀 Conduit wouldn't exist without the primitives that made it possible. 🦊 @MetaMask 's advanced permissions and smart accounts let users authorize once and enforce exactly what AI agents can and cannot do. @AskVenice handles reasoning and planning. @1shotapi powers the execution layer. The result? A team of AI agents that can collaborate, hire one another, and complete tasks without ever exceeding the boundaries defined by the user. #MetaMaskDevCookOff #x402 #aiagent #hackathon

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

keyboard_arrow_left Previous keyboard_arrow_right Next

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.

@ConduitProtocol @MetaMaskDev For multi-agent flows, do you think every downstream action should inherit the user's original constraints? Otherwise, delegation chains seem like they could become the weakest point.

Give an AI agent a wallet and three attacks immediately become possible: • Redirect the payment • Inflate the payment • Replay the payment Conduit eliminates all three onchain. Conduit is a custom x402 facilitator that extends the @MetaMaskDev Delegation Framework with a custom caveat we built: X402ReceiptEnforcer and other enforcers Instead of granting an agent broad spending authority, every payment authorization is cryptographically bound to a single x402 receipt: → token → recipient → amount → intent When the agent attempts to settle payment through ERC-7710 on a MetaMask Smart Account, the delegation is validated inside "redeemDelegations()" before execution. If the agent deviates from what was authorized: → Redirect payment → recipient mismatch → revert → Overspend payment → amount exceeds authorization → revert → Replay payment → intent already consumed (IdEnforcer) → revert The result is a security layer for agentic commerce where permissions are not merely granted, they are constrained. No app-layer validation. No trusted facilitator assumptions. No offchain enforcement. The rules live inside the delegation itself and are enforced by the EVM. An agent can only execute the exact payment it was authorized to make or nothing at all Built for the @MetaMaskDev Cook-Off using @MetaMask Smart Accounts, ERC-7710 Delegation Framework, gas sponsorship through @1shotapi , and @AskVenice AI-powered agents. #x402 #aiagents #erc7710 #buildinpublic #metamaskdev #osobotai #hackathon

14 days left. Conduit started from the @MetaMaskDev Smart Accounts Kit workshops and evolved into a custom facilitator for agentic payments powered by EIP-7710, x402, and gas abstraction. Excited to keep pushing the infrastructure for agent-to-agent commerce. 🦊🤖

MetaMask Developer @MetaMaskDev

3 weeks ago

14 days left to build the future of agentic payments 🤖 The @MetaMask Smart Accounts Kit Cook-Off has $16,000 in prizes across 7 tracks. Submit your project here ↓ hackquest.io/hackathons/Met…

0 6 22 2K 9

Conduit now settles through the @1shotapi Permissionless Relayer. An agent can pay for a service and pay the gas in USDC, no relayer to run, no pre-funding. How it works under the hood: An agent hits a 402, and Conduit (our custom x402 facilitator for the erc7710 settlement method) builds the redemption. Because 1Shot recoups gas in stablecoin, each payment carries two delegations merged into one on-chain batch: → a bounded fee delegation- pays 1Shot's collector, capped, floored at the live quote → an intent-bound work delegation- our X402ReceiptEnforcer locks it to one recipient, one amount, one token, one request So even the gas payment is bound. A compromised agent can't redirect either leg. The user's account is upgraded to a @MetaMaskDev Smart Account via EIP-7702 - bundled into the same transaction the relayer submits. One tx: account upgrade + the payment, gas in USDC. Settlement status comes from @1shotapi's Ed25519-signed webhooks, verified against their JWKS - then forwarded to integrators as clean events. Build on Conduit, register a webhook, and you never touch the relayer, the chain, or the crypto. Verified on Base Sepolia: the settlement tx is submitted by @1shotapi's relayer, gas paid in USDC. Mainnet next. Built on @MetaMaskDev Smart Accounts + @1shotapi. #x402 #erc7710 #eip7702 #erc7715 #agenteconomy #solidity #dev #metamask

The interesting part of AI payments isn’t autonomy. It’s constraint. Conduit turns ERC-7710 permissions into enforceable payment rules: → one request → one scope → one bounded delegation chain Built on @MetaMaskDev smart accounts with settlement via @1shotapi relayers.

Conduit Protocol @ConduitProtocol

a month ago

Conduit Architecture👇 A custom x402 + erc7710 facilitator built on @MetaMaskDev smart accounts: - advanced permissions (erc7715) authorize the payment - a custom on-chain caveat binds it to one specific request - @1shotapi's permissionless relayer settles it with gas in USDC

keyboard_arrow_left Previous keyboard_arrow_right Next

2 4 6 413 0

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

Conduit Architecture👇 A custom x402 + erc7710 facilitator built on @MetaMaskDev smart accounts: - advanced permissions (erc7715) authorize the payment - a custom on-chain caveat binds it to one specific request - @1shotapi's permissionless relayer settles it with gas in USDC

keyboard_arrow_left Previous keyboard_arrow_right Next

Bitcoin is the hardest asset in the world. It's time to leverage it.

We’re excited to announce our partner lineup for the upcoming @MezoNetwork Hackathon with @SupernormalFDN. Joining us: @Goldskyio, @BoarNetwork, @Enigmaaingma, @ValidationCloud, @SimplyStaking and @sats_ventures They’ll be supporting across workshops, mentorship, judging and infra/RPC access throughout the programme. This is a 6-week hackathon where builders create Bitcoin-native finance on Mezo, from replacing traditional banking with BTC to consumer apps powered by MUSD and expanding MEZO utility. Heading to EthCC? Join Mezo & Encode Club for a rooftop happy hour to learn more about the Mezo and Super Normal Foundation hackathon! Sign up to hackathon + happy hour ↓

This isn't a static label. It's a living profile. When member #51 joins with a different risk tolerance, the collective's axes shift. When someone leaves, it recalculates. The collective literally learns from its members' on-chain identities.