From 5ea77acbe6591971a7a2999cb53eaaf174fb413e Mon Sep 17 00:00:00 2001 From: Mr Peter Marirosans <6649063+MarirosansP@users.noreply.github.com> Date: Mon, 13 Jul 2026 22:16:53 +0100 Subject: [PATCH 1/4] Agent Registry: add optional verification block to the Concordium Badge --- .../agent-registry/concordium-badge.rst | 34 ++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst index d1f00a4e90..54ab57b257 100644 --- a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst +++ b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst @@ -50,6 +50,10 @@ Resolve and verify a badge Verification is trustless: given only the badge string, any party can verify it independently, without trusting whoever presented it. +.. note:: + + **Zero-setup path.** A badge embedded in an Agent Card may advertise a ``verification`` block (defined under **Embed the badge**, below) that points at a hosted resolver. A consumer that has never used Concordium can then verify from the card alone — ``GET`` the ``verifyUrl`` and read the verdict — without first discovering which node, Indexer, or MCP endpoint to call. The steps below are what that resolver runs, and what a consumer verifying directly against the chain performs itself. + #. **Parse** the Base58Check string into ``(contract, token_id)``. *(MCP tool: ``parse_token_address``)* #. **Confirm the contract** is the expected CIS-8004 registry for the network (mainnet ``<10082,0>``). @@ -78,9 +82,37 @@ Add a ``concordium`` block to the :doc:`Agent Card `: "chain": "ccd:9dd9ca4d19e9393877d2c44b70f89acb", "owner": { "account": "", "caip10": "ccd:9dd9ca4d…:" }, "contracts": { "cis8004": "10082,0", "cis8": "10081,0" }, - "verify": "Resolve tokenAddress via CIS-8004 agent_of; confirm owner + status=Active + card SHA-256 == metadata_hash." + "verify": "Resolve tokenAddress via CIS-8004 agent_of; confirm owner + status=Active + card SHA-256 == metadata_hash.", + "verification": { + "service": "Concordium Agent Registry", + "verifyUrl": "https://agent-registry-mcp.concordium.com/v1/badge-check/", + "mcp": "https://agent-registry-mcp.concordium.com/mcp", + "indexer": "https://agent-registry-indexer.concordium.com", + "docs": "https://docs.concordium.com/mainnet/technical-reference/agent-registry/concordium-badge.html" + } } +The ``verify`` string names the steps; the optional ``verification`` block names **where to run them**. Together they make a badge *self-resolving* — a consumer that has never seen Concordium can verify it from the card alone. Every field is a discovery convenience: the trust root is still the on-chain contracts in ``contracts``, and any party may ignore these hints and resolve directly against the chain. + +.. list-table:: + :header-rows: 1 + :widths: 20 80 + + * - Field + - Purpose + * - ``service`` + - Human-readable name of the resolver / registry service. + * - ``verifyUrl`` + - REST endpoint — the owner account's badge check — returning a JSON verdict for each of the account's badges, including this one (owner, ``status``, and card-hash match). One ``GET``, no MCP client, SDK, or node access required. + * - ``mcp`` + - MCP endpoint for agents that speak the Model Context Protocol; they can call ``verify_agent_card`` / ``agent_by_token_address`` directly. + * - ``indexer`` + - :doc:`Indexer ` REST base URL, for enumeration and discovery. + * - ``docs`` + - This specification, for a consumer that prefers to verify manually against the chain. + +A resolver named here is a convenience, not an authority — it returns chain-derived data that the consumer can re-check against the contracts in the badge. Issuers point these fields at whichever hosted :doc:`MCP service ` and :doc:`Indexer ` they operate or trust. + Profile or bio -------------- From 3187e06fa4060f6a47406b5e272e5cdb61bd91ce Mon Sep 17 00:00:00 2001 From: Mr Peter Marirosans <6649063+MarirosansP@users.noreply.github.com> Date: Mon, 13 Jul 2026 22:33:28 +0100 Subject: [PATCH 2/4] Badge verification: drop CIS-10 + indexer; frame contracts/services as standards with the official Concordium instance as example --- .../agent-registry/concordium-badge.rst | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst index 54ab57b257..3c554c3b74 100644 --- a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst +++ b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst @@ -43,7 +43,7 @@ where ``token_id`` is a ``TokenIdU64`` (8 bytes, little-endian). The ``@concordi .. note:: - **Registry contracts (mainnet):** CIS-8004 Agent Registry ``<10082,0>``, CIS-8 External Key Registry ``<10081,0>``. A badge that parses to any other contract is not a Concordium Badge. + **Registry contracts.** :doc:`CIS-8004 ` and :doc:`CIS-8 ` are open standards. Concordium operates the official registries — on mainnet, the CIS-8004 Agent Registry ``<10082,0>`` and the CIS-8 External Key Registry ``<10081,0>`` — but a badge is a Concordium Badge whenever its contract *implements the CIS-8004 standard*, not only when it resolves to the official instance. Each badge's ``contracts`` block names the specific contracts it resolves against, and a verifier decides which registries it trusts. Resolve and verify a badge ========================== @@ -52,17 +52,17 @@ Verification is trustless: given only the badge string, any party can verify it .. note:: - **Zero-setup path.** A badge embedded in an Agent Card may advertise a ``verification`` block (defined under **Embed the badge**, below) that points at a hosted resolver. A consumer that has never used Concordium can then verify from the card alone — ``GET`` the ``verifyUrl`` and read the verdict — without first discovering which node, Indexer, or MCP endpoint to call. The steps below are what that resolver runs, and what a consumer verifying directly against the chain performs itself. + **Zero-setup path.** A badge embedded in an Agent Card may advertise a ``verification`` block (defined under **Embed the badge**, below) that points at a hosted resolver. A consumer that has never used Concordium can then verify from the card alone — ``GET`` the ``verifyUrl`` and read the verdict — without first discovering which node, resolver, or MCP endpoint to call. The steps below are what that resolver runs, and what a consumer verifying directly against the chain performs itself. #. **Parse** the Base58Check string into ``(contract, token_id)``. *(MCP tool: ``parse_token_address``)* -#. **Confirm the contract** is the expected CIS-8004 registry for the network (mainnet ``<10082,0>``). +#. **Confirm the contract** implements CIS-8004 and is a registry your application trusts. Concordium's official mainnet registry is ``<10082,0>``. #. **Resolve on-chain** with the CIS-8004 ``agent_of(token_id)`` query, which returns the owner account, agent wallet, status, ``agent_uri``, and ``metadata_hash``. Require ``status = "Active"``. *(MCP tools: ``agent_by_token_address`` / ``agent_of``)* #. **Check card integrity.** Fetch the Agent Card at ``agent_uri``, compute the SHA-256 hash of its canonical bytes, and require that it equals the on-chain ``metadata_hash``. The published card cannot be swapped without the chain revealing a mismatch. *(MCP tool: ``verify_agent_card``)* -#. **(Optional)** Confirm the agent's platform handle via its CIS-10 assertion, and/or an external cryptographic key bound to the agent via :doc:`CIS-8 `. +#. **(Optional)** Confirm an external cryptographic key bound to the agent via :doc:`CIS-8 `. A passing check proves that the agent is registered in the Agent Registry, is currently active, is owned by an accountable Concordium account, and that its published card is exactly the one committed on-chain. The trust root is Concordium — not the party presenting the badge. @@ -87,12 +87,11 @@ Add a ``concordium`` block to the :doc:`Agent Card `: "service": "Concordium Agent Registry", "verifyUrl": "https://agent-registry-mcp.concordium.com/v1/badge-check/", "mcp": "https://agent-registry-mcp.concordium.com/mcp", - "indexer": "https://agent-registry-indexer.concordium.com", "docs": "https://docs.concordium.com/mainnet/technical-reference/agent-registry/concordium-badge.html" } } -The ``verify`` string names the steps; the optional ``verification`` block names **where to run them**. Together they make a badge *self-resolving* — a consumer that has never seen Concordium can verify it from the card alone. Every field is a discovery convenience: the trust root is still the on-chain contracts in ``contracts``, and any party may ignore these hints and resolve directly against the chain. +The ``verify`` string names the steps; the optional ``verification`` block names **where to run them** — ``service``, ``verifyUrl``, ``mcp``, and ``docs``. Together they make a badge *self-resolving*: a consumer that has never seen Concordium can verify it from the card alone. The values below are Concordium's official Agent Registry service, shown as an example — the block is **not limited to them**. Any issuer may point these fields at a different service that runs the same checks, and any party may ignore the hints entirely and resolve directly against the contracts in ``contracts``. .. list-table:: :header-rows: 1 @@ -106,12 +105,10 @@ The ``verify`` string names the steps; the optional ``verification`` block names - REST endpoint — the owner account's badge check — returning a JSON verdict for each of the account's badges, including this one (owner, ``status``, and card-hash match). One ``GET``, no MCP client, SDK, or node access required. * - ``mcp`` - MCP endpoint for agents that speak the Model Context Protocol; they can call ``verify_agent_card`` / ``agent_by_token_address`` directly. - * - ``indexer`` - - :doc:`Indexer ` REST base URL, for enumeration and discovery. * - ``docs`` - This specification, for a consumer that prefers to verify manually against the chain. -A resolver named here is a convenience, not an authority — it returns chain-derived data that the consumer can re-check against the contracts in the badge. Issuers point these fields at whichever hosted :doc:`MCP service ` and :doc:`Indexer ` they operate or trust. +A service named here is a convenience, not an authority — it returns chain-derived data the consumer can re-check against the contracts in the badge. Issuers point these fields at whichever hosted verification service — resolver and :doc:`MCP ` — they operate or trust. Discovery and enumeration (finding agents you don't already have a badge for) is a separate concern handled by the :doc:`Indexer `, not the badge. Profile or bio -------------- From dece0113998b7a314be9a66a16fcf12f97aeb921 Mon Sep 17 00:00:00 2001 From: Mr Peter Marirosans <6649063+MarirosansP@users.noreply.github.com> Date: Mon, 13 Jul 2026 22:55:17 +0100 Subject: [PATCH 3/4] Badge doc: remove the Worked example section --- .../agent-registry/concordium-badge.rst | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst index 3c554c3b74..4b6861b4a1 100644 --- a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst +++ b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst @@ -138,21 +138,6 @@ The badge introduces no new standard. It composes: - :doc:`CIS-8 ` — external key binding - :doc:`Agent Card ` — the agent's published metadata document -Worked example (mainnet) -======================== - -.. code-block:: text - - Badge: Mf22soLh1NuZYFgBK8iSs - parse → contract 10082,0 · token_id 484 (hex e401000000000000) - agent_of→ owner 4DDvjwdcLmTy1Ar9FCKKPMiABrS261TvyXJGr4n4ypuuogXeFF - status Active (registered 2026-06-17) - card https://…/.well-known/agent-card.json - hash 1253bd8fa1618f6b5fd2ff741cc8f4d60a0e6ac0f8ea5f32640c71540001e0d0 - CAIP-19 → ccd:9dd9ca4d19e9393877d2c44b70f89acb/cis-2:Mf22soLh1NuZYFgBK8iSs - -Fetch the card, compute its SHA-256, and confirm it equals ``1253bd8f…`` — the badge is verified end-to-end. - Tooling ======= From b8ec8dde924612c5268db4c0f4c5f37af49ec424 Mon Sep 17 00:00:00 2001 From: Mr Peter Marirosans <6649063+MarirosansP@users.noreply.github.com> Date: Mon, 13 Jul 2026 23:05:20 +0100 Subject: [PATCH 4/4] Badge doc: fix docs URL to /en/mainnet/ (the path that resolves) --- .../technical-reference/agent-registry/concordium-badge.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst index 4b6861b4a1..09796e6de8 100644 --- a/source/mainnet/technical-reference/agent-registry/concordium-badge.rst +++ b/source/mainnet/technical-reference/agent-registry/concordium-badge.rst @@ -87,7 +87,7 @@ Add a ``concordium`` block to the :doc:`Agent Card `: "service": "Concordium Agent Registry", "verifyUrl": "https://agent-registry-mcp.concordium.com/v1/badge-check/", "mcp": "https://agent-registry-mcp.concordium.com/mcp", - "docs": "https://docs.concordium.com/mainnet/technical-reference/agent-registry/concordium-badge.html" + "docs": "https://docs.concordium.com/en/mainnet/technical-reference/agent-registry/concordium-badge.html" } }