Name: Sample File — gated download
Brand: CRM Sync
SKU: asset:dawn-horizon-ga4
Price: 2.00 USD
Availability: InStock

Wireframe cube — gated 3D model, monochrome line art

Sample File — gated download

$2.00

$2.00 $19.00

See gated selling from the buyer's side, for $2. A working demo of the gated flow running on a real document — the Dawn to Horizon GA4 migration report. You buy an entitlement (not a naked file), and unwrap the report under your own grant.

How it works

Buy, and you get a grant — not a download link.
Unwrap the full 490KB report under your entitlement, decrypted server-side at the moment you ask for it.
There is no public URL to the file at any point, so there is no link to leak and nothing to re-host.

What else the vault holds

The envelope does not care what is inside it. The same mint, the same grant and the same hash-chained ledger carry an SBOM, a firmware image, a subscription entitlement, a legal document, a time-based architectural render, a warehouse inspection, or a PDF like this one. One envelope, one grant, one ledger — the file type is a detail, the custody is the product.

Which is why the demo is a document you can actually read. A 3D model would prove the same mechanism and tell you less, because you could not check what you received.

Private vaults

A vault is private when it is not listed anywhere and reachable only by a named grant — no public page, no discoverable URL, no anonymous path in. Private vaults hold the classes above and one more: attestations. An attestation is a signed statement that something is true — a device passed inspection, a batch was tested, a practitioner holds a current credential, a laboratory result was signed off. The statement is sealed, the grant is named, and the ledger records every party who asked for it and every one who was refused.

The distinction matters and we hold it deliberately: an attestation is a claim you can verify, not a subject's record. Keeping the claim and the record apart is what lets a counterparty confirm something is true without being handed the file it came from.

What makes it different

Most "samples" are just a smaller file to download. This one proves the mechanism, so before you sell your own work this way, you've felt it as a buyer. You can also check it without buying anything: the Verify it yourself tab asks for the document with no grant, shows you the refusal verbatim, and then shows that refusal written into the access ledger a moment later.

Under the hood

Encrypted at rest with AES-256-GCM; purchase issues a revocable entitlement; the unwrap is grant-gated and server-side; and every grant, every denial and every served byte-stream is sealed into a hash-chained ledger you can read yourself.

Open the Channel Wizard →

Mint an attributed link or QR for this product — preview it free in the modal; minting unlocks with the Channel Publish add-on.

A live demo of the gated-asset flow, running on a real document: the Dawn to Horizon GA4 migration report. You buy an entitlement, not a file, and unwrap it under your own grant.

What you get

✓An entitlement, not a download — the purchase returns a grant, and the grant can be revoked.
✓The full report — 490KB, unwrapped server-side under your grant; there is no public URL to the file at any point.
✓A firsthand look — the vault does not care what the file is. An SBOM, a firmware image, a subscription entitlement, a legal document, a time-based architectural render, a warehouse inspection, a PDF: one envelope, one grant, one ledger. This one is a document, so you can open it and judge the mechanism rather than the format.

The problem. When you send or sell a file, you lose it. You cannot see who opened it, you cannot take it back, and if someone forwards it you will never know. That is fine for a holiday photo. It is not fine for anything you sell, anything under contract, or anything you would have to answer for later.

What happens here instead. You do not hand over a file. You give someone permission to open it, and you keep the controls: how many times they can open it, one person or a named group, when access starts, when it ends, and how many people they are allowed to pass it to.

And all of it is written down. Every time someone opens it — or is turned away — the date and time is recorded. You can show that list to a customer, an auditor or a lawyer. It counts people, not devices: your TV, your tablet and your laptop are still one person.

A working entitlement is indistinguishable from an ordinary download — so the honest way to show it is to watch it refuse. Press the button. You have no grant, so you will be turned away, and the refusal itself is written to the access ledger alongside every grant and every served byte-stream.

Nothing here is asserted at you: the ledger below is served live, its hash chain is verified on read, and the row you just created appears in it. Subjects are redacted in this public view.