newsence
來源篩選

ERC-xxx: Agentic On-Chain Operation Interface

Ethereum Magicians

We are going to standardize the canonical workflow interface for agentic on-chain operations. We aim to define a signed intent envelope expressing core safety bounds (maximum input, minimum output, validity windows, and replay protection), a permissionless settlement surface enabling competitive solver fulfillment, and structured settlement receipts providing verifiable workflow closure. The standard separates intent authorship from solving and execution, enabling autonomous agents, solvers, and users to coordinate around outcome-based objectives. Core safety bounds are enforceable on-chain by every compliant hub. Additional policies MAY be enforceable via optional constraint modules. Every outcome is recorded via machine-readable receipts suitable for post-execution verification and structured record-keeping. This ERC provides a common vocabulary and interface for agentic on-chain operations: a standardized lifecycle and receipts that make agents interoperable across runtimes and ecosystems. # Motivation Ethereum transactions encode execution instructions rather than desired outcomes. Emerging agent systems require a mechanism to express goals without prescribing execution paths. Many systems define “orders” or “intents,” but these systems vary in lifecycle semantics, signature domains, and receipt formats. The ecosystem lacks a standard lifecycle and uniform settlement receipts that make agents interoperable across runtimes. Without a shared workflow interface, each agent-solver pair must negotiate bespoke formats, verification procedures, and completion signals — fragmenting the ecosystem and limiting composability. While [ERC-8004](./eip-8004.md) standardizes trustless agent identities and reputation, it does not define how agents express actionable objectives or how such objectives are executed and verified on-chain. This proposal introduces: - A canonical intent envelope with core safety bounds enforceable on-chain by every compliant hub - Optional constraint modules for additional policies, with a standard enforcement hook - A permissionless fulfillment interface supporting on-chain and off-chain intent distribution - Atomic settlement guarantees with structured receipt events - A standardized workflow lifecycle from authorship through verification The goal is to enable autonomous agents, solvers, and builders to coordinate around outcome-based execution while preserving user safety, composability, and auditability. This ERC defines the minimal workflow closure primitive — core safety bounds enforceable on-chain, structured receipts, and optional constraint modules — needed for agents to treat on-chain actions as composable, verifiable skills. 1 post - 1 participant Read full topic

newsence

ERC-xxx:代理人鏈上操作介面

Ethereum Magicians
10 天前

AI 生成摘要

我們將標準化代理人鏈上操作的規範工作流介面,旨在定義表達核心安全邊界的簽名意圖封包、支持競爭性求解器履行的無許可結算介面,以及提供可驗證工作流閉環的結構化結算收據。

ERC-xxx: 代理型鏈上操作介面 (Agentic On-Chain Operation Interface) - ERCs - Fellowship of Ethereum Magicians

摘要

本提案定義了一個標準介面,用於在以太坊上執行代理型操作(Agentic Operations)。該介面旨在標準化 AI 代理、自動化腳本和智慧合約之間的互動方式,使其能夠以自主或半自主的方式代表用戶執行複雜的鏈上任務。

動機

隨著 AI 代理和自動化工具在 Web3 生態系統中的興起,目前缺乏一個統一的標準來定義這些實體如何與區塊鏈進行互動。現有的解決方案通常是碎片化的,且缺乏互操作性。建立一個標準的代理型操作介面將:

  1. 增強互操作性:允許不同的 AI 代理與各類 DeFi 協議和鏈上服務無縫互動。
  2. 提升安全性:為代理操作提供明確的權限管理和限制框架。
  3. 簡化開發:為開發者提供一套通用的 API,用於構建具備 AI 能力的去中心化應用程式(dApps)。

規範

介面定義

代理型操作介面必須實現以下核心函數:

executeAgenticOp

執行一個或多個代理定義的操作。

solidity
function executeAgenticOp(    bytes calldata operationData,    bytes calldata signature) external returns (bytes memory result);

getAgentPermissions

檢索特定代理的當前權限。

solidity
function getAgentPermissions(address agent) external view returns (bytes32[] memory permissions);

事件

AgenticOpExecuted

當代理操作成功執行時必須觸發。

solidity
event AgenticOpExecuted(address indexed agent, bytes32 indexed opHash, bytes result);

理由

選擇這種設計是為了平衡靈活性與安全性。透過使用位元組數據(bytes data)進行操作定義,該介面可以適應未來各種不可預見的代理行為,而標準化的權限查詢則確保了用戶對其資產的最終控制權。

向後相容性

此標準旨在與現有的智慧合約錢包(如 ERC-4337)相容,並可作為現有帳戶抽象框架的擴展。

安全考量

代理型操作引入了獨特的風險,包括:

  • 授權濫用:代理可能會執行超出用戶預期的操作。
  • 簽名偽造:必須確保代理的身份驗證機制足夠強健。
  • 策略限制:建議實施基於時間或金額的限制(Throttling)以減輕潛在損失。