SELEKT AUDIT RECEIPT
Public Audit ChainSubject ID: b86d5345-9f0a-4052-9807-0154fe608ddc
Runs in your browser. No data leaves this page.
What does this prove — and who is it for? Scroll to the bottom of this page for a short guide on how producers, composers, game and app developers, podcasters, and score writers each use a verified chain like this one in their day-to-day work.
Selekt's public signing key. The signature above was checked against this key. Anyone can re-verify independently with the same key — see Advanced below.
-----BEGIN PUBLIC KEY-----
MCowBQYDK2VwAyEAWGVkpKotWu1xjBJdIZbg2hLF4psr4L8y6qRFYbPqgmk=
-----END PUBLIC KEY-----
ADVANCED: VERIFY OFFLINEDownload the JSON via the button below and save the public key above to audit-public-key.pem.
For each record, strip signature, compact-stringify the rest, and Ed25519-verify against the key.
Cross-check previous_record_hash against the SHA-256 of the preceding record to confirm the chain.
Node.js snippet:const crypto = require('crypto');
const record = JSON.parse(fs.readFileSync('record.json'));
const { signature: sig, ...rest } = record;
const pubKey = crypto.createPublicKey(fs.readFileSync('audit-public-key.pem'));
const valid = crypto.verify(
  null,
  Buffer.from(JSON.stringify(rest)),
  pubKey,
  Buffer.from(sig.signature, 'base64')
);
console.log(valid ? 'VALID' : 'INVALID');
Download JSONView Certificate PDFPublic Key (.pem)
What was actually verified — event timelineNo audit events recorded for this subject yet. The signed response envelope above is genuine — Selekt did issue this exact JSON at the timestamp shown — but no Layer A audit events (ingest screen, attestation, salvage, re-screen, etc.) have been written for this subject ID yet. Events accrue when the sample is screened, re-screened, salvaged, or used in a Forge generation. Check back after any of those happen.
FULL SIGNED JSON (0 records)The raw bytes that were signed. This is the data your browser’s verification ran against — alter a single character and the signature check would fail.
{
  "subject_id": "b86d5345-9f0a-4052-9807-0154fe608ddc",
  "queried_at": "2026-06-04T01:42:44.063Z",
  "record_count": 0,
  "public_key_url": "https://selektaudio.com/audit-public-key.pem",
  "audit_receipt_url": "https://selektaudio.com/audit/b86d5345-9f0a-4052-9807-0154fe608ddc",
  "cert_url": "https://selektaudio.com/cert/b86d5345-9f0a-4052-9807-0154fe608ddc",
  "events": [],
  "response_signature": {
    "signed_at": "2026-06-04T01:42:44.063Z",
    "algorithm": "Ed25519",
    "public_key_id": "selekt-audit-key-v2",
    "signature": "pVA4gXFR/EA5md0RCJ7U6mlK6JoeJ+zAJtj+acNHUrU5NEewZ32OL36kVHxrADP1NJs8v5LK79yJjCBOaQL7Bw=="
  }
}
What does this mean — and who is it for?
What you just verified is a permanent, cryptographically-signed record of how Selekt screened this sample for copyright issues, when it was added to the catalog, and what was found on any re-screening since. The chain is append-only: nothing here can be quietly changed after the fact, and anyone — a rights-holder, distributor, legal team, technical reviewer — can re-run the same Ed25519 check you ran, entirely in their browser, against the published public key, without ever touching Selekt's systems.
The question every distributor, publisher, sync supervisor, and rights-holder eventually asks is “how do you know this was cleared?” The honest answer most people have is “trust me.” This page is a better answer — a documented, time-stamped screening receipt with a signature anyone can re-verify.
Who can use it, and how:
Producers handing a beat to a label, sync supervisor, or sample-clearance reviewer can attach this URL — one click shows the source, the screening result, and the cryptographic proof. No email-thread forwards or screenshots of database lookups required.
Composers scoring film, TV, games, advertising, or library catalogs can include this URL on cue sheets and submission packs so the music supervisor doesn't have to take their sourcing on faith.
Game developers and app developers can attach it to asset submissions when a store reviewer, publisher, or platform partner asks for proof of music sourcing — and to their own internal asset-clearance ledger so future audits don't have to recreate the trail.
Podcasters can hand this URL to a host network, ad sponsor, or distribution platform reviewing their music selections; it's documented evidence of due diligence whether or not the platform requires it.
Score writers and library composers submitting to sync agencies can attach this URL alongside the cue sheet so the agency knows the underlying material was screened, not just claimed.
Anyone in a copyright dispute or takedown can use this chain as primary evidence of when and how the sample was sourced and screened — independent of anything Selekt says or does after the dispute begins.
The screening isn't a guarantee — no fingerprint database is 100% comprehensive — but it is a documented, time-stamped, signed record that a real industry tool was used to check this sample. That's more than most catalogs can show, and it's what reviewers actually want to see.
Hey — Selekt is still being built.

Public Audit Chain

What was actually verified — event timeline
