One file. Two channels. One of them locked.
A Zariia release is an ordinary music file. Any player in the world plays it. Riding alongside the audio, in the same file, is a second channel held under a key.
Encrypted, not buried
The sealed channel is not tucked inside the waveform so that nobody can tell it is there. That would be steganography, and it is not what this is. The second channel rides beside the audio, plainly present, and what protects it is a lock rather than a hiding place.
Anyone who inspects the file can see that a sealed channel exists. That is intended, and it is the honest position. What the key protects is the hearing.
Presence open. Content keyed.
Two things follow, and both are gains. There is no capacity ceiling, so the sealed channel can be a complete second production at full fidelity rather than a thin ghost squeezed into the gaps. And there is no detectability problem to lose, because nothing was ever claimed to be undetectable.
A block sitting in plain view in the file, legible as a block, saying nothing at all about what is inside it.
Nothing here hides. The lock is the whole mechanism, and the lock is visible.
How it survives an ordinary player
The audio is untouched
The file's audio frames are the open track, byte for byte. The format is lossless, so the song does not merely sound similar — it is identical.
The seal rides in metadata
The sealed channel travels in application metadata blocks, which a conformant player is required by the specification to skip over when it does not recognise them.
So an ordinary player just plays
It plays the open song and steps over the sealed part without complaint. No error, no prompt, no sign that anything was skipped.
A wrong key is refused
The seal is authenticated. A wrong key or a tampered file does not open partially or degrade gracefully. It fails, and the failure is enforced rather than reported.
The same object, three ways.
Streaming re-encodes audio, which strips the sealed channel away. That is not a fault to engineer around. It gives the object three lives, and the three do different work.
The public face streams anywhere, because it is just music. The whole thing travels as a file and a secret. Try it in the player ▸
What this is not.
Stated plainly, because a thing like this attracts claims it should not make.
- It does not hide. The sealed channel's presence is open by design. Zariia is not covert, claims no undetectability, and is not built to defeat anyone. The lock protects the content and nothing else.
- The music is real. Authored, avowable, worth hearing on its own terms. Not filler wrapped around something else.
- It is only as safe as the key. The music sounding identical is a solved problem. Everything else rests on who holds the key and how they treat it. There is nothing further to over-claim.
- Streaming strips it. The complete object exists only as the exact file. A constraint to design around, not a bug awaiting a fix.
- Nothing here is verified. No authority stands behind any of it, no badge, no tick, no institution vouching for anything. There is no moderator and there will not be one.
- A key is not a membership. It opens the record, and that is all it does. Being in a scene is made some other way — by turning up, playing, being asked back — and nobody is enrolled in anything by holding thirty-two bytes. A key that reaches you is evidence that somebody thought of you, which is a good thing to be and is not a rank.
- Everything here can be copied except the giving. Any recording can be copied, and a sealed channel that leaves the room can be copied too. That was never the part this format protected. What does not copy is the handing over — a key reaches you because a person chose to give it, and chose you, and you both know it. That is not a security measure. It is simply not a thing that reproduces. Neither is the warmth of a room, which no channel carries.