Puddingify Seal Logo
Register
Free Trial - Ends 2026/06/01

Your Title Goes Here

eleven-52

Production Portfolio
Mr. Smokey Bacon
Creator Information

Mr. Smokey Bacon

✓ Verified
Creator Name:
Mr. Smokey Bacon
Creator Alias
smokeybacon
Creator Email
[email protected]
About The Creator:
Tech/ blockchain entrepreneur
Creator Location:
Toronto | Canada
Creator's Public Key & Authentication ✓ Valid Key
-----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB...
📊 Portfolio Collection: eleven-52
✓ Verified
eleven-52 • 2 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 2 Files
ALL-SETS-MUST-BE-COMPLETE.txt, FILE-SETS-ALL.txt
Merkle Root Hash: 4737ef29235f90c51f6db17979a1dba88115a554b66081d3e6fed3d8b865c90c
Digital Signature & Verification ✓ Verified
DOOyRKLFaPRF76pAoUn+t3qN0NDSpopK...

🌳 Merkle Tree Construction

Step-by-step cryptographic proof showing how all artifacts are bound together

📄 Level 0: Leaf Nodes (Individual File Hashes)

Each file's content is hashed using SHA-256 to create a unique fingerprint. These are the "leaves" of the Merkle tree.

Leaf 1: ALL-SETS-MUST-BE-COMPLETE.txt
Position in tree: 0
bdf5ab59bd252e7553628927a670d47ae019fe233f5b9c0de8660fb389eedf9d
Leaf 2: FILE-SETS-ALL.txt
Position in tree: 1
f09c3d378a708ba7065bcb38ab0c240af2d5d8ca1d8b4cfa4c0041475086801f

✅ MERKLE ROOT (Final Level)

This is the single hash that represents ALL files in the collection. This root hash is included in the manifest that gets digitally signed.

MERKLE ROOT HASH:
4737ef29235f90c51f6db17979a1dba88115a554b66081d3e6fed3d8b865c90c
💡 Why This Matters for Legal Proof:
  • Any change to ANY file will change its hash (leaf node)
  • This changes all parent nodes up to the root
  • The digital signature validates this specific root hash
  • Therefore: ALL files are cryptographically proven by ONE signature
📁 Portfolio Metadata & Verification ✓ Available
Permalink:
https://puddingify.com/creator-profile/smokeybacon/portfolio/eleven-52
📁 File Content Manifest ✓ Verified

SHA-256 hashes of each file's content. These prove the files haven't been tampered with.

# Filename Content Hash (SHA-256) Date Actions
1 ALL-SETS-MUST-BE-COMPLETE.txt bdf5ab59bd252e75...e8660fb389eedf9d 2025-02-16 12:39:02
2 FILE-SETS-ALL.txt f09c3d378a708ba7...4c0041475086801f 2025-05-23 15:56:06

🌳 File Content Manifest Hash (Merkle Root)

Purpose: Cryptographic proof that all file contents are unchanged

This Merkle root is computed from all file content hashes using a binary tree structure. Any change to any file will change this root hash.

4737ef29235f90c51f6db17979a1dba88115a554b66081d3e6fed3d8b865c90c
🏷️ Filename Manifest ⚠️ Modified
⚠️ WARNING: Filenames have been modified!

The current filenames do not match the original manifest hash stored in the database.

SHA-256 hashes of the filenames themselves. Independent verification of which files are included.

# Filename Filename Hash (SHA-256) Actions
1 ALL-SETS-MUST-BE-COMPLETE.txt 8a06a3bd3dbf4fe1...b6666c0584cd3f5e
2 FILE-SETS-ALL.txt b3a2cbf99f8c3a21...eb171cd6ef81217f

🌳 Filename Manifest Hash

Purpose: Proves the list of filenames hasn't been altered

This is a SHA-256 hash of the JSON structure containing all filenames and their metadata. It serves as a tamper-evident seal for the manifest document itself.

5a43bc2fe04b31de78c52b47c0894dcd34cd09bb41bafdd225a160c6621cdf43