Skip to content

Badge: key verifyUrl on tokenAddressBase58, not the account - #1512

Merged
ktconcordium merged 1 commit into
Concordium:mainfrom
MarirosansP:badge-verifyurl-token-address
Jul 14, 2026
Merged

ktconcordium merged 1 commit into
Concordium:mainfrom
MarirosansP:badge-verifyurl-token-address

Conversation

@MarirosansP

Copy link
Copy Markdown
Contributor

What

Fixes the verification.verifyUrl example in the Concordium Badge to key on the badge's tokenAddressBase58, not the owner account:

- "verifyUrl": "…/v1/badge-check/<account>",
+ "verifyUrl": "…/v1/badge-check/<tokenAddressBase58>",

Why

A verifier reading a card holds the badge itself — the token address is right there in the concordium block. Keying verifyUrl on the account made it (a) require pulling owner.account out first, and (b) return a list of the account's badges rather than a verdict for this one. Keying on the token address means one GET → one verdict for the exact badge in hand, which is the whole point of a self-resolving badge.

The hosted resolver's /v1/badge-check/:id accepts either form (account → all its badges; token address → that one badge), told apart by the base58 version byte, so nothing else changes.

🤖 Generated with Claude Code

@ktconcordium
ktconcordium merged commit 4413548 into Concordium:main Jul 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants