DEV Community

Offline Pro keys for MV3 extensions: Ed25519 license checks with no server, no account

I ship four local-first Edge extensions - FocusBlock (live), ConvoExport, YouTube Transcript Export, and SessionSnap (in review as of the last check, 12:45 CST today).

All four sell Pro as a one-time activation code. There is no license server, no account, and no network request at check time - because the extensions themselves make zero network requests, and a license server would be the only one.

The free tiers are deliberately usable without paying anything:

  • FocusBlock allows 20 blocking rules free
  • ConvoExport allows 3 exports a day
  • SessionSnap keeps snapshots for 14 days
  • YouTube Transcript Export exports a single video's transcript free

Pro lifts those limits with one code, entered once in the options page and stored locally.

The newer check: Ed25519 signatures (YouTube Transcript Export)

The key starts with AIX-, followed by Crockford base32 encoding of a payload and a 64-byte Ed25519 signature.

The payload carries a version, a tier, the issue day, the number of valid days (0 means lifetime), and an id. The signature covers the domain string AIX1 plus the payload, and the extension verifies it with tweetnacl against a public key embedded in the extension.

The private key never ships. It lives only with the minting script, on my own machine.

Verification itself is a pure function - no DOM, no chrome.* - so the Node self-tests cover it, including a throwaway-keypair round-trip and a check that the real public key rejects a foreign key.

This is real verification: anyone can read the public key, and nobody can mint a valid key without the private key. The scheme was kept verbatim from an earlier v1.0.2 design so that keys already issued under it keep working.

The older check: a symmetric checksum (the other three)

ConvoExport, SessionSnap, and FocusBlock share an earlier scheme: the key carries a payload plus a checksum computed over a secret and the payload, and the extension validates it locally. It is instant, offline, and simple.

Its limitation is stated in the code itself, and I will state it here too: this is obfuscation-grade, not DRM. The secret ships inside the extension bundle, so anyone who reads the bundle closely enough can mint keys. It keeps honest users honest.

Keys are issued manually by a private generator script after an order is paid, and server-side verification is the planned next step after first revenue.

I am deliberately not publishing the older scheme's algorithm details here. Describing the signature scheme is safe - that is the point of public-key cryptography. Describing the checksum scheme in full would hand out the recipe for forging keys.

What the tests cover

Each extension's suite includes license cases: a minted key validates, a tampered or foreign key is rejected, Pro features stay gated without a key, and clearing a key restores the free tier.

Suite sizes, all passing:

  • ConvoExport 71
  • YouTube Transcript Export 120
  • SessionSnap 166
  • FocusBlock 117

Status, stated plainly

FocusBlock is live on Edge Add-ons: https://microsoftedge.microsoft.com/addons/detail/focusblock/kdpeddhiegpfadpjiaieoaeiloebgdhp

The other three are submitted and in review. Pro is not for sale yet - the activation-code listing is not up. This post is about the mechanism, not a sales page.

Privacy pages (all four extensions collect nothing and store everything locally):

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.