BadgeMax Pro
Decentralized, cryptographically verifiable badge creation enabling organizations, developers, publishers, and website administrators to create customized SVG badges containing cryptographically signed metadata.
badgemax.pro
A badge can be distributed as an SVG, embedded on a website, and checked against a published issuer key and assertion record.
Features
| Feature | Description |
|---|---|
| SVG Badge Designer | Customize appearance, dimensions, text, and branding |
| Cryptographic Attestation | Embed signed metadata inside the SVG |
| SHA-256 Fingerprint | Generate an identifier derived from badge artwork |
| ECDSA P-256 | Digitally sign attestations with ES256 |
| Public/Private Keys | Generate or import signing keys |
| JWKS Export | Publish public verification keys |
| Assertion Records | Generate active or revoked status files |
| Expiration Metadata | Include optional expiration timestamps in assertion records |
| Verification Page | Export a standalone verify.html |
| Static Hosting | Publish badge, assertion, and public key files without a dedicated signing server |
| Embed Code | Generate HTML for displaying the badge |
| Interactive Fingerprint | Display fingerprint characters with hover and focus effects |
How BadgeMax Pro Works
BadgeMax Pro uses three related artifacts.
1. Badge SVG
The SVG contains:
- Badge artwork
- A fingerprint identifier
- An assertion URL
- Embedded attestation metadata
- A cryptographic signature
- The issuer's public key
2. Public Key Set
A jwks.json file publishes the issuer's public verification key.
The expected location is:
https://your-domain.com/.well-known/bar/jwks.json3. Assertion Record
A JSON file provides the badge's published status.
For example:
https://your-domain.com/a/BADGE_ID.jsonAn assertion can indicate whether a badge is active or revoked.
Typical Workflow
- Customize the badge.
- Generate or import a signing key.
- Generate the badge.
- Download the SVG.
- Download the public JWKS.
- Download the assertion JSON.
- Publish the files on your website.
- Verify the published badge.
What Makes an Attested Badge Different?
A conventional badge is simply an image.
An attested badge also carries signed information that a verifier can check.
The verifier can establish whether:
- The badge artwork matches its recorded hash.
- The attestation signature validates against a public key.
- The embedded public key matches the issuer's published JWKS entry.
- The issuer's online assertion reports an active status.
These checks depend on correct publication, trusted key ownership, and the verifier's implementation.
Browser Requirements
BadgeMax Pro uses modern browser APIs, including:
- Web Crypto API
crypto.subtle- DOMParser
- XMLSerializer
- Blob and object URLs
- FileReader
- Fetch API
- Clipboard API
HTTPS is recommended for normal deployment.
Privacy
BadgeMax Pro displays the commitment:
This site never saves or sells your data.
The supplied signing implementation creates and handles keys within the browser and does not submit private keys to a signing server.
The application also supports fetching remote logo images and verification resources, and the supplied HTML contains advertising code.
These external network interactions should not be confused with BadgeMax Pro selling or storing user data.
Documentation
Continue with:
- Getting Started
- Badge Designer and Branding
- Cryptographic Keys and JWKS
- Attestations and Fingerprints
- Assertion Records and Revocation
- Badge Verification
- Static Hosting and Embedding
- Privacy, Security, and Troubleshooting
Updated about 5 hours ago