Keep a dated record
of the finished work.
When a project moves between drafts, clients and platforms, it can be useful to preserve evidence of exactly what existed at a particular release point. Daisybee records a compact commitment, not your files.
What can you seal?
Design / artwork pack
Seal exported images, source deliverables or a finished asset pack as one release.
Manuscript / document set
Keep a cryptographic record of a submitted draft plus its supporting files.
Client deliverable
Record the exact folder delivered to a client, collaborator or marketplace.
A record you can verify later.
Prepare one folder
Put the files that define the release together and choose that folder in the browser.
Create the commitment
Daisybee builds a Merkle root from local hashes and records the root on Gardennet.
Save your evidence
Keep the receipt with the originals; the PDF and public page make the commitment easy to reference.
One release. One Evidence Certificate. Verification remains free.
Evidence package.
Local receipt with paths, sizes and SHA-256 hashes.
Merkle commitment recorded on Daisybee Gardennet.
PDF certificate with certificate ID and QR verification link.
Privacy-safe public verification record.
Evidence ZIP plus optional OpenTimestamps proof.
Proof, not a legal verdict.
Gardennet is experimental and resettable. The portable receipt and optional Bitcoin/OpenTimestamps path are designed to make the evidence useful beyond a screenshot of one private database.
Before you buy.
Does this prove I created the work?
Not by itself. It is evidence of a cryptographic commitment at a point in time, not a legal decision about authorship or ownership.
Are filenames made public?
No. The public record does not publish the individual filenames or file hashes in your local manifest.
What should I keep?
Keep the original files and the full Daisybee receipt. Those let you rebuild the Merkle root later.