Repository navigation
Align badge embedding with A2A and ERC-8004; add CAIP identifiers reference - #1516
Merged
Merged
Conversation
|
limemloh
approved these changes
Aug 31, 2026
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.
Purpose
Brings the Verified by Concordium badge's Agent Card embedding into conformance with the two standards it composes with, and documents the
ccdCAIP namespace profile ahead of extending its ChainAgnostic registration.Cross-referenced against the normative texts: EIP-8004 (current draft) at eips.ethereum.org and the A2A v1.0 specification. Key alignments: A2A prohibits extensions adding top-level card fields, so the badge moves into
capabilities.extensionsunder a versioned extension URI; ERC-8004's current draft placesregistrationsin the anchored registration file, so theagent_uridocument becomes one combined JSON valid as both an ERC-8004 registration file and an A2A v1.0 Agent Card. All on-chain references use full CAIP identifiers per theccdprofile (CAIP-2 already registered with ChainAgnostic; CAIP-10/CAIP-19 sections written in registry profile format, ready for submission).Changes
agent-registry/concordium-badge.rst: "Embed the badge" rewritten — normative A2A extension embedding (URIhttps://docs.concordium.com/a2a-extensions/concordium-badge/v1, slimmed params: CAIP-19tokenAddress, CAIP-10owner/contracts,verify,verification); new ERC-8004registrationssubsection (numericagentId, dot-formagentRegistry); legacy note (pre-existing top-levelconcordiumblocks stay valid); rationale admonition so the block isn't moved back to top level; standards list updated.agent-registry/agent-card.rst: intro, field tables, and example replaced with the combined ERC-8004 + A2A v1.0 document; retires the previous snake_caseconcordiumblock format that diverged from the badge page.caip-identifiers.rst(new):ccdnamespace profile in ChainAgnostic page format — CAIP-2 (registered, matches the live registry profile), CAIP-10 accounts + dot-form contracts, CAIP-19 (cis-2,plt,slip44:919). The CAIP-10/19 sections are copy-ready for the namespaces registry PR so docs and submission cannot drift.technical-reference/index.rst: new Standards caption (grid + toctree) holding the CAIP page.public/a2a-extensions/concordium-badge/v1/index.html(new): static spec page so the extension URI resolves (public/ is copied to the site root byscripts/build.sh).public/llms.txt: new CAIP entry; refreshed descriptions for the badge and Agent Card pages.Notes for reviewers: The extension URI is permanent for v1 once cards carry it — please treat the URI string and the
paramsschema as frozen; breaking changes mint/v2. Existing registered agents are unaffected (verification is placement-agnostic); new/re-anchored cards adopt the extension form. Service-side changes (MCPbuild_agent_card, resolver dual-read, agentcards.site template) are deliberately out of scope.Checklist
source/)-Wpasses; all cross-references resolve; branch content verified byte-identical to the locally built tree)