IlionWeb Solutions

Practical ProofBundle example

Alice creates a work. Bob verifies the file he receives.

Alice needs to deliver a digital illustration to Bob. She wants technical evidence tied to the exact file she sent, while Bob wants to check that the received content was not altered. ProofBundle makes that check repeatable without uploading the work to an Ilion server.

Back to productContact Ilion
Alice hands a digital folder to Bob, who verifies it with a magnifying glass.
Alice hands a digital folder to Bob, who verifies it with a magnifying glass.

Practical example

Alice and Bob’s situation

Alice is a freelance illustrator. She has completed a drawing and needs to send it to Bob, the client who commissioned it.

A normal attachment delivers the file but does not automatically organize hashes, a signature, a manifest and timestamp evidence. Alice uses ProofBundle to create a technical dossier for the final version.

Practical example

How it works, step by step

  1. Alice selects the final version

    She chooses the file or directory to document. It should be the same version that will be delivered.

  2. She creates the ProofBundle locally

    The program calculates hashes, prepares the manifest and organizes the evidence. The original work does not need to be sent to Ilion.

  3. She associates a signed claim

    Alice can add an Ed25519 or OpenPGP signed claim and, when needed, request OpenTimestamps evidence.

  4. She preserves the work and evidence

    Alice stores the original file, dossier and keys separately using an appropriate procedure.

  5. She delivers the materials to Bob

    Bob receives the file and ProofBundle through the agreed delivery channel.

  6. Bob runs the verification

    Verification recalculates fingerprints and checks the available manifest, signature and timestamp evidence. The check can later be repeated offline.

Results

What Alice and Bob receive

  • Alice preserves a technical dossier associated with the delivered version.
  • Bob can check whether the received file matches the evidence.
  • Verification does not depend on the future availability of the Ilion website.
  • The check can be repeated after transfer or archival.

Stated limitations

What ProofBundle does not prove by itself

  • It does not automatically prove that Alice is the original author.
  • It does not independently establish legal ownership or the absence of earlier works.
  • It does not replace contracts, public registries, official deposits, copyright bodies, courts or legal advice.
  • Keys and original files still require careful storage.

FAQ

Frequently asked questions about ProofBundle

Does ProofBundle upload my work?

No. The dossier is created locally. You decide how the work and evidence are stored and shared.

Does Bob need to trust Ilion to verify it?

No. The dossier is portable and verification can run without depending on an Ilion server.

Does ProofBundle replace copyright registration?

No. It produces verifiable technical evidence but does not replace legal instruments, official registration or professional advice.

Would you like to test this flow with your own file?

Explore the ProofBundle project or tell Ilion what kind of work, delivery or archive you need to document.

Explore ProofBundle