[SCITT] Re: New draft: Attested Payment Authorization for Autonomous Agents (draft-hawkins-scitt-attested-agent-payment-00)
Walter Hawkins <wdhawkins46@gmail.com> Sat, 15 August 2026 04:51 UTC
Return-Path: <wdhawkins46@gmail.com>
X-Original-To: scitt@mail2.ietf.org
Delivered-To: scitt@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id A0F4812A311EC for <scitt@mail2.ietf.org>; Fri, 14 Aug 2026 21:51:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786769472; bh=OO8qYNgtkxYchXqzG5ggndWBDIxrjsFl0+uXYUGwsd8=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=f3ui6uSXTG+qOfnTRviaTobNkyK1QHXWoH29BA9/qOz23PCYtlVRKK8kO5P26cPyB mV2HSFjWidkhLjbHgGTDJ8+dqNoipHyfNBkZYijjr1V9NZnk50cYactOnoAJtuI2Og WdIR2eey2rtUn2t2YhwNpRhikIlX2KXznqLgkxgc=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.848
X-Spam-Level:
X-Spam-Status: No, score=-0.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FORGED_GMAIL_RCVD=1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dm9acjdQ604u for <scitt@mail2.ietf.org>; Fri, 14 Aug 2026 21:51:11 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6B88212A311E7 for <scitt@ietf.org>; Fri, 14 Aug 2026 21:51:11 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-39ca300db70so12106751fa.2 for <scitt@ietf.org>; Fri, 14 Aug 2026 21:51:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1786769464; cv=none; d=google.com; s=arc-20260327; b=Gz427PV2OPxkP1MfbiKBX3EkDFPBf6qHGNdCfQbB8RgdgoNeFeXwCBIE8IXH1XNS8C 0Qv1WgWWFC0bZoZdTSGKa5NG8NpxwhZQtIRWz0NWAOjgaxdC4rH+5QGh+J9Z82ljq8QQ AkUJ+2fPzZ8xXNPc9l/It6XiYpt84N76UzNuWELldhVquTATvpFtN6oED+g9jriE6n/M bm6BSssIhDHG0MJIoGIyxo3io6Cf8Q1YkcuXj3gVTb6SYWn71hUSF5hbhxdyF7vm6xi5 709gak0e9WHk38QpInbyEyslNuBl49OG/fCYEf2Xc9g/egoZe4MGrv6L6bzfvzlZNsNY p+6g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=+98RXQrgFzsS9RGMuhfgTQyHuKEfdzIluW7bIMZHi20=; fh=KFI/ZgHVu+VVo5CXsRTLIvBgo0U42U4aO5PyGjTKbes=; b=GqxHxqM0f0zF8yIqDdCTOAxpjy2y9mzjtVgx/rI08LF4KukkEAzzvMq4cqqtsFjYuc 7SJ/zix5F7IOwwPDlmGbaiKs14Z5VRgXBdvuhFRiy8RNgPcFRHpJiV/NEqNgqLzKJdqb MxTDGo4FPmmysVW6jmknJQNyaaxdIrd5k+vkyR9fHPV752AltFdQARyEALaHMYHyBZWo BWxgvwW7hy2SJSswDG0TkaTNhfjsqqwfkucE2Nmo3mRhfRM5X5CWU1hUuagtF2Wd+6Hr 3V5IbBffXqtDYFWmoE/QPNmbpZManC02WRnTBnGSrYD57W23q4MeEacAusxnCoD3tI8+ qtmw==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1786769464; x=1787374264; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=+98RXQrgFzsS9RGMuhfgTQyHuKEfdzIluW7bIMZHi20=; b=W29oyblADQpLagz8BJsXL3XOP4T8/gJ+MGq5BSqHrtbW1RkEa2drMZGucpWFPQJDWp Fc+jfAyTTeM/r6CJ75b8lcaZlpiWIuQDeEsd3zXuDm14je2+18oqw7pBl3lN9PNaOUrz sITzIs6paayKmX29dZ6URMO9hJ8XmimwsjoZGu+iLl4JQc8hgl/sYV0oXwQ6vo0fCw2E RsZZMxmjctQMKsg6k0lfZAgqMVkkEtp3D1npsvQqEYy96BcCeX03cjORs8iDFiMJysCN OECEt0W9lkoetSiiVnIuMOAwQtE/IspcXtIEjvE1OA7MzD5o8oE97vhucfA+2TwSkhQX UvuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786769464; x=1787374264; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=+98RXQrgFzsS9RGMuhfgTQyHuKEfdzIluW7bIMZHi20=; b=OLHj//vJsnsCg4qdTQ2XYh4IXB6lElW9LUmbtFvo/0rF8TH/nK8fnZSdSc31Wxom+3 oD6itP4eq99SkmlrKRdvsjOWucUdB0khXGmDQAdtXNvzJicTIn4uv1HcfJJpw8qpVLZb gfkHM/oyx0UB5bZhbd2B292K127rSgWEpSoxhwZwQWdIw9WHOJxynCGsHg7R0UYXSH65 8kLhzOV8+Yl90z3npvwVmkvIfIiDZEnMHOv5YCoOAZLMvak92AP6lFucLcLopkedF3mT cEwD4ypwK283lb0oTDsCUbbU7Fk/7S4J9jB7T3DMhigEqPplQOZmZXTXS980G8OeOAJK BdWg==
X-Gm-Message-State: AOJu0YzwbYVUDg2PcLpUCVU1jLqXW5Sxukm9iJiqeCUP8wIQ10Q0K2br L2aYT2DicY3IauRstXQFLZihlY+2EYHrtX94A+NbEixxrj+kwP1NRsynHokpq2NO6xMAh8L4uZC xp8dtKMCx7xurHVlyRyOY5+61uASQMvJtiefe
X-Gm-Gg: AR+sD11kzVBqATBB9jYvAtTcy2U0i+8M0+oQwa7QUCMt+eX/b5/y3RIBqGaGl4XII/e nMfNxkIOiq+SJeSdEQhMdfreyh/KybQer1FUEa73i3ae8dKIVjlPG28vkNzn0EuEBaOlBZoOk5+ R0D7o8t6TpLzEmEsi++z5i+m5/q0gcuK6RbB2uxYgXcjKqqKMaz79Rgp1kGj82QdpQmK2StwfQP uYhLgKeIr3T9es7a856m1RUSLNCysKF4C9REPLEOvU5imN0DkMgmoeE4zd1s4HXi6OEgRnu5DIs MZJ3ing4ZU0tLdsNEBQNf/78FFNAYreDdLSz+QvLU0XZZhp6GGvf
X-Received: by 2002:a2e:bc81:0:b0:3a1:244a:b6c3 with SMTP id 38308e7fff4ca-3a13280e566mr11089261fa.31.1786769463536; Fri, 14 Aug 2026 21:51:03 -0700 (PDT)
MIME-Version: 1.0
References: <CANWAHpoV7WZ2k5KEk-GhJ+1eioSjQ636+oVLN1D0r05n-Zae0w@mail.gmail.com> <CALc05oHd_BxgaSOO7K8St+7GZMO37986D7tAsaHqjZ13s7rkBw@mail.gmail.com> <CANWAHpoP6MhSRqSFQ6=-Kvxivf_QMWOkd1_vCFogc6sd=R8UWA@mail.gmail.com>
In-Reply-To: <CANWAHpoP6MhSRqSFQ6=-Kvxivf_QMWOkd1_vCFogc6sd=R8UWA@mail.gmail.com>
From: Walter Hawkins <wdhawkins46@gmail.com>
Date: Fri, 14 Aug 2026 23:50:39 -0500
X-Gm-Features: AcwNN1W0X5TRFsmJFB7lnk17Ex-ZRYSprLus9YblPghaVnapiTMQ63EMAlVQIks
Message-ID: <CALc05oFTaKZDjNAY+mRVy9V1iz_ges59oYPKPxxGODnPWfXfFQ@mail.gmail.com>
To: Pablo Play <playplay2736@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000002b720f06590eaf93"
Message-ID-Hash: DHMWASDZ7EF6V3MWKNJLATNFIZ2WEVVB
X-Message-ID-Hash: DHMWASDZ7EF6V3MWKNJLATNFIZ2WEVVB
X-MailFrom: wdhawkins46@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "scitt@ietf.org" <scitt@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [SCITT] Re: New draft: Attested Payment Authorization for Autonomous Agents (draft-hawkins-scitt-attested-agent-payment-00)
List-Id: "Supply Chain Integrity, Transparency, and Trust" <scitt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/scitt/RMW2gTQS9eMNGicO9dY0kkGQTs4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scitt>
List-Help: <mailto:scitt-request@ietf.org?subject=help>
List-Owner: <mailto:scitt-owner@ietf.org>
List-Post: <mailto:scitt@ietf.org>
List-Subscribe: <mailto:scitt-join@ietf.org>
List-Unsubscribe: <mailto:scitt-leave@ietf.org>
Pablo, Corrections received, and respected. Retracting a claim on-list that nobody could have disproven is the behavior this whole thread exists to make normal. I did what the repo invites: pulled both receipts from a public RPC myself. Scope digest in the AnchorRegistry event at block 49980111, execution digest at 49980123, both status 1, both matching your values byte for byte. And the PROVENANCE.md framing, synthetic data with no claim of conformance to a wire format you haven't seen, is the right register. Rarer than it should be. On enumeration, agreed on where we landed. Henri's point downthread about omission is real pressure on it, and I owe him a proper reply once I've read his draft and vectors with the care they deserve. The -01 revision folds in your execution-digest split and the enumeration-on-challenge MUST, with credit. Your demo made the independent-anchoring shape concrete: two records, neither derived from the other, each discoverable alone even if the party holding the second one goes quiet. That independence is doing more work than it first appears, and the draft will say so. Walter On Fri, Aug 14, 2026 at 6:28 PM Pablo Play <playplay2736@gmail.com> wrote: > Walter, > > Two quick corrections, then what you asked for. > > I referred to "the scope-digest and supersession fixes landing in -01" > as already > published — they weren't, and I don't have a source for that; my error, > not > something I saw elsewhere. And "in production" was imprecise: what's > actually live > on Base mainnet is our anchoring infrastructure (AnchorRegistry, > permissionless, > source-verified on Basescan/Arbiscan, ~20 real anchors) — not a settled > agent-payment flow using this specific digest split. Correcting both > rather than > letting them stand, given the subject of this thread. > > Built today to give you something checkable, not a production record: > > - Repo: https://github.com/giskard09/agent-payment-split-anchor > - scope_digest d0900e69… — tx 0xc0f15cb2…, block 49980111, Base mainnet, > confirmed > - execution_digest 75310efa… — tx 0xa462d76d…, block 49980123, Base > mainnet, > confirmed > - Both checkable independently via eth_getTransactionReceipt against a > public RPC, > or verifier/verify.py, which recomputes both digests from source and > confirms the > on-chain event for each. > > PROVENANCE.md is explicit: synthetic data, no real payee or settlement, > and no > claim to match your draft's actual wire format — I don't have visibility > into your > field names or schema, so this demonstrates the split (authorization > digest and > execution digest, neither derived from the other, both independently > anchored) as > buildable and verifiable, not a conformance implementation of your spec. > > On enumeration: making the sum-over-enumerated-digests a MUST on > challenge closes > exactly what a single recomputable digest leaves open — proves "could > have been > counted," not "was counted." Agreed, and stronger than what we had > before you > raised it. > > Pablo > > El vie, 14 ago 2026 a la(s) 7:18 p.m., Walter Hawkins ( > wdhawkins46@gmail.com) escribió: > >> Pablo, >> >> You're right. Step 6 as written has the executor attesting to itself: >> "the executor's own record of prior spending" is a record nobody outside >> the executor ever sees, sitting in the middle of a draft whose whole >> argument is that a claim a relying party cannot check should be treated as >> absent. I wrote that clause and didn't notice the exception I was carving. >> >> I'm adopting the split you describe. What's queued for the next revision: >> >> An execution digest, computed over the settled payment's fixed fields — >> amount, payee, settlement timestamp, and the scope digest it was authorized >> under — distinct from the scope digest and not derivable from it. Anyone >> holding the settled payment's terms can recompute it. Section 5's list of >> properties available to absent parties gains a fourth, in your words: that >> a specific settled payment was counted against this scope, not just >> plausible under it. >> >> One consequence follows that your note doesn't spell out, so let me >> commit to it here: for the aggregate bound to be checkable rather than >> asserted, the executor has to enumerate the execution digests it counted >> under the scope. The sum over that list is what an auditor compares to the >> limit, and a settled payment whose digest is missing from the list is the >> discoverable failure. Without the enumeration, a recomputable digest proves >> a payment could have been counted — which is the same self-report, one step >> removed. I intend to make the enumeration a MUST on challenge. >> >> One correction for the record, since your note reads as though it has >> already happened: there is no -01. The scope-digest and supersession >> changes you refer to are queued from off-list review and will be credited >> when the revision posts; -00 is the only published text. If you saw those >> changes described somewhere other than this list, I'd genuinely like to >> know where, because I haven't published them. >> >> On the Base deployment: I would like to see the worked shape, and this >> list is the right place for it. A contract address or a couple of >> transaction hashes would let anyone verify the split is doing what you say >> — that's the standard the draft asks of executors, so it's the standard >> I'll hold evidence offered for the draft to as well. >> >> You'll be credited in the next revision's acknowledgments. >> >> >> Walter >> >> On Fri, Aug 14, 2026 at 1:49 PM Pablo Play <playplay2736@gmail.com> >> wrote: >> >>> Walter, all — >>> >>> Following the scope-digest and supersession fixes landing in -01: step >>> 6 still >>> leaves one clause self-reported. "the executor's own record of prior >>> spending under this scope confirms the aggregate bound is not exceeded" is >>> the executor attesting to itself, from records nobody outside it ever sees. >>> The Receipt in Section 5 proves the scope existed before the payment — it >>> doesn't prove the payment that actually settled is the one the executor's >>> aggregate claims to have counted. >>> >>> The fix is the same shape as the scope-selection fix: bind the >>> executed payment to its own digest, distinct from the scope digest, derived >>> from the payment's fixed >>> fields (amount, payee, timestamp, scope digest) — so a party who >>> wasn't present at settlement can recompute it and check it against what the >>> executor's aggregate says it included. Section 5 already lists three >>> properties available to absent parties >>> for the authorization; a fourth — that a specific settled payment was >>> actually >>> counted against this scope, not just plausible under it — needs the >>> same treatment. >>> >>> We've been running exactly this split (authorization-scope digest vs. >>> execution >>> digest, neither derived from the other) for agent payments in >>> production on Base >>> mainnet. Happy to share the worked shape if useful. >>> >>> Pablo Etcheverry >>> >>
- [SCITT] New draft: Attested Payment Authorization… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… hello
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… hello
- [SCITT] Re: New draft: Attested Payment Authoriza… Dick Brooks
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Vernon
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Joel Hillier
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Tiago Pinto
- [SCITT] Re: New draft: Attested Payment Authoriza… Pablo Play
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Pablo Play
- [SCITT] Re: New draft: Attested Payment Authoriza… Henri Sirkkavaara
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Henri Sirkkavaara
- [SCITT] Re: New draft: Attested Payment Authoriza… Gibson, Todd
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Henri Sirkkavaara
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Walter Hawkins
- [SCITT] Re: New draft: Attested Payment Authoriza… Pablo Play