cip: add Agentic Identity & Mandate-Bound Payments (Standards Track / Daml)#202
Open
hilarl wants to merge 1 commit into
Open
cip: add Agentic Identity & Mandate-Bound Payments (Standards Track / Daml)#202hilarl wants to merge 1 commit into
hilarl wants to merge 1 commit into
Conversation
… Daml) Specifies how autonomous AI-agent identities and the mandates that constrain them are carried in the meta field of CIP-56 transfer instructions, so that agent-initiated payments settle natively against CIP-56 holdings under cryptographically-enforced authority. Composes three published primitives — W3C DID Core 1.1 / VCDM 2.0 for agent identity, ERC-8004 for cross-chain agent registration, and AP2 (Agent Payments Protocol, FIDO Alliance, since 28 April 2026) for mandate semantics — onto CIP-56's two-step transfer flow without any new on-chain templates. Fixes a normative meta-key namespace (tenzro.network/agent.* and tenzro.network/mandate.*, 12 keys), specifies the IntentMandate / CartMandate / signed-VC schemas, and defines a 7-clause registry-side validation predicate. Filed as Draft. No number self-assigned. Slug: cip-hilarl-Agentic-Identity. Signed-off-by: Hilal Agil <hilal@tenzro.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cip: add Agentic Identity & Mandate-Bound Payments (Standards Track / Layer: Daml)
Summary
This PR opens a Standards Track CIP specifying how DID-controlled
agents — both human-controlled and machine-controlled — bind to Canton
parties, and how an agent's payment mandate is carried in the
metafield of CIP-56 transfer instructions so that registries can validate
mandate-bound transfers at certification time.
The CIP defines three mechanisms:
human and machine identities, the PDIS DIDs,
did:web, anddid:key.meta-key envelope (§3, 10 keys) for carrying delegation-scope,intent-mandate, and cart-mandate commitments alongside their
detached signatures.
of purchases over a window; CartMandate authorizes one specific
purchase. The two compose under the AP2 intent-and-cart pattern.
delegation ceilings, mandate aggregate ceilings, cart-nonce
uniqueness, mandate-issuer signature validity, and counterparty
binding.
The CIP is filed as Draft. Per CIP-0000, the author has not
self-assigned a number; the editor will assign one on merge.
This is the third in a four-part stack of contributions covering, in
order: (A) Multi-VM CIP-56 Bridge Pattern; (B) AI Training & Inference
Settlement; (C) the agentic identity and mandate-bound payments in
this PR; (D) TEE-Attested Confidential Compute Receipts. Each is filed
as a separate CIP and may be reviewed independently.
What this CIP specifies
domain-separation tag
tenzro/agentic/party/v1. Seven DID methodsenumerated normatively.
meta-key namespacetenzro.network/agent.*(§3) with 10normative keys covering principal DID, controller DID,
delegation-scope commitment, intent-mandate commitment,
cart-mandate commitment, mandate issuer DID, mandate signature,
off-ledger URI, and validity window.
controller DID, per-transaction ceiling, daily-spend ceiling,
allowed operations, allowed payment protocols, allowed chains
(CAIP-2), and time bounds.
binding to
instrumentIdand carrying the per-cart nonce.covering principal binding, delegation enforcement, intent
aggregate enforcement, cart binding + signature + nonce, and
amount equality.
CIP-112, including allocation-flow settlement.
What this CIP does NOT propose
protocol, or the Global Synchronizer.
trust per §Security considerations.
Reference implementation
The pattern is shipped and operating on the Tenzro Network testnet.
Live endpoints documented in §Reference implementation of the CIP
body.
TDIP DIDs and W3C DID Document export live at
crates/tenzro-identity/src/{did,identity,document,credential}.rs.DelegationScope and the
enforce_operationceiling live atcrates/tenzro-identity/src/delegation.rs. AP2 mandate validationlives at
crates/tenzro-payments/src/ap2/mod.rs. The two-axisceiling (DelegationScope + runtime SpendingPolicy) lives at
crates/tenzro-payments/src/identity_binding.rs. The Cantonadapter that populates the
metakeys at submission time lives atcrates/tenzro-bridge/src/canton.rs.File layout
The CIP lives at
cips/cip-hilarl-Agentic-Identity.md. The directoryconvention used by numbered CIPs (
cip-XXXX/) is also acceptable,with the file moved on number assignment.
Process notes
cip-hilarl-Agentic-Identity.Signed-off-by: Hilal Agil hilal@tenzro.com