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

Your Title Goes Here

5588-1102am

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: 5588-1102am
✓ Verified
5588-1102am • 2 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 2 Files
public_key_smokeybacon.pdf, public_key_smokeybacon.txt
Merkle Root Hash: 79960c566dcc68631b2a219e2758c4eca8513aceac61e766e434bc8a0cc65551
Digital Signature & Verification ✓ Verified
YLz+ezJc+yKaYLY3uVmvMmJNOPk7WsVL...

🌳 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: public_key_smokeybacon.pdf
Position in tree: 0
cb713ecf1f4d0eb075092f26d37db47f657e5f6da19b12485d98db4ed1175e1e
Leaf 2: public_key_smokeybacon.txt
Position in tree: 1
5bd3b5b5720ff6c8d7d93f7d209ad7cb86de8b0a4f0d4a428fee1998dff74e61

✅ 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:
79960c566dcc68631b2a219e2758c4eca8513aceac61e766e434bc8a0cc65551
💡 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/5588-1102am
📁 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 public_key_smokeybacon.pdf cb713ecf1f4d0eb0...5d98db4ed1175e1e 2025-08-28 10:49:25
2 public_key_smokeybacon.txt 5bd3b5b5720ff6c8...8fee1998dff74e61 2025-09-20 18:17:15

🌳 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.

79960c566dcc68631b2a219e2758c4eca8513aceac61e766e434bc8a0cc65551
🏷️ 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 public_key_smokeybacon.pdf 73ef0cd69c2a8de6...90fc62fd27cf646b
2 public_key_smokeybacon.txt 58d2a5f90dab23a5...0c5c640917e5054c

🌳 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.

e6ac51c8e17b6e09394f1652cb8334d5378c301d3f636177f17b947f14cc2c98