Sandbox · 1 test record · may be wiped
The Song Seal sandbox.
The same record format, the same pages and the same verifier as the real record host — for test seals. A first draft seal, a dry run before a real one, or just a look at what a record is. Nothing here is a real seal.
What a sandbox record is not. It is not evidence of anything about a real
song: its names are test names, its address is not a permanent one, and the whole
sandbox may be wiped without notice. Every record here is stamped staging
in its own committed bytes, so no real record host will ever accept one — and a
checker reports it as a staging record unless you tell it that is what you expect.
The records it holds
Check a sandbox record
Download its record.json and the file it describes.
The
record.jsonlink beside each record above. The audio is yours: Song Seal never stores the file, only its fingerprint.In a browser: the checker, with the staging box ticked.
Open check.songseal.org, give it the
record.jsonas a file and your audio, and tick “This is a staging (test) record”. Without the tick it stops at “this is a staging record” on purpose: a test record must never pass for a real one by accident.Or offline, with the one-file verifier.
node verify.mjs record.json yourfile.wav --allow-staging
verify.mjs is the same file the real host serves.
--allow-stagingis the same tick: it checks the record as a test record, and nothing it prints makes it a real one.The date, where a record carries anchors.
Sandbox seals can be anchored like real ones: an RFC 3161 token and an OpenTimestamps submission. The verifier prints the exact
openssl ts -verifyandots verifycommands; an authority it does not know is named as one.