Question: where would a dated pre-payment fact fit, a caveat enforcer or the client?

オープン
  • 何か問題がありますか？
#215 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
javascript, solidity
領域
blockchain

調査の方向性

This is a design question, not a patch. Read the delegation framework docs on caveat enforcers and redemption, then compare the client hook at bin/x402-gate-hook.mjs in AgenticFinanceGraph/agentic-finance-graph-mcp with the enforcer's amount and target bounds. Check the payee-facts definitions at /def/payee.facts.v2 and the dated EIP7702StatelessDeleGator finding; done is a maintainer answer on where dated external facts belong, not code changes.

索引モデルが issue の本文から書いたものです。

説明

A measured fact first, then one question.

We run Agentic Finance Graph, a read-only ledger of what ERC-8004 agents on Base do with money, read from the chain. Of the 2,029 EIP-7702-delegated wallets bound to ranked agents in our ledger (ranked = a payment seen from the bound wallet), 556 point at EIP7702StatelessDeleGator at 0x63c0c19a282a1b52b07dd5a65b58948a07dae32b (Sourcify match), the second-largest family after Coinbase's EIP7702Proxy (683). Measured 30 October 2026, 14:17 UTC, from eth_getCode on each wallet; a salted random sample of 200 re-read through a public Base node at block 53288713 agreed with our table on 181 of 185 readable wallets, and a coverage correction the same day (our table had held an implementation for only 930 of those wallets until the rest were re-read through a public node) is dated in our register as cp-2026-10-30-7702-impl-backfill. The dated finding with the full list is in our findings feed (kind delegation_families, agenticfinancegraph.com/api/findings), and the implementation set with names is published as a wallet set (agenticfinancegraph.com/api/wallet-sets). Names identify contracts, not the agents on them; nothing here is a trust decision.

The question. Before one of these agents pays, our server can return dated facts about the payee in one call (is it a paying agent, who else pays it, drain or address-poisoning history, the usual size of payments into it; definitions at agenticfinancegraph.com/def/payee.facts.v2). In the delegation model, where does an external, dated fact belong: inside a caveat enforcer that fetches it (with the staleness and availability problems that brings on chain), or in the delegate's client before it redeems the delegation, with the enforcer only bounding amounts and targets? We built the client-side version as an onBeforePaymentCreation hook for x402 clients (bin/x402-gate-hook.mjs in AgenticFinanceGraph/agentic-finance-graph-mcp) and would rather follow the framework's intent than guess it.

If a different venue is better for this kind of question, point us to it and we will close this.

主要言語
Solidity
スター
230
フォーク
122
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

MetaMask/delegation-framework のほかの issue

MetaMask/delegation-framework の issue をすべて見る

似ている issue

Blockchain の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。