Recognition · portable by design · in development

Issue yourself a verifiable badge runs in your browser · stores nothing

Turn a teaching-scholarship milestone into a portable, cryptographically verifiable record, structured as an Open Badges 3.0 credential. Your signing key is generated in this browser tab and never leaves it; NTLSN has no server in this loop and keeps nothing. Anyone can check the badge's integrity — on this page, or with standard tooling.

What this is, said plainly. This is a self-issued claim: you are the issuer, and the cryptography proves the badge hasn't been altered and was made by the holder of your key — it does not make NTLSN or anyone else vouch for the content. That is the same philosophy as the SoTL Index's self-declared recognition, upgraded to a portable standard format. Institutional issuance — where a university signs badges its committees stand behind — is the roadmap this page is the free proof-of-concept for. Wallet and platform import support for Open Badges 3.0 varies today; the JSON payload is standards-shaped, and this page verifies any badge it issued. NTLSN is independent of and not affiliated with 1EdTech; no conformance certification is claimed.
Your signing key: none yet — one will be generated when you issue.
Keep the backup if you want future badges to come from the same identity. Nothing is stored on this device unless you download it yourself.

Your badge (compact JWS — this is the portable artefact)


      

        
        
        
      

      
Decoded credential

      

    

  


  

  
How the cryptography works, in one breath: your browser generates a P-256 keypair; the issuer identity is a did:jwk derived from your public key; the credential is signed as a compact JWS (ES256). Verification re-derives the public key from the issuer identifier inside the badge and checks the signature, so a badge carries everything needed to verify it — no registry, no lookup, no NTLSN involvement. Integrity, portably.