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

Your Title Goes Here

7789iop

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: 7789iop
✓ Verified
7789iop • 2 artifacts • Aug 25, 2025
Collection Artifacts & Files ✓ 2 Files
debug_log-1.txt, HASHING-RESULTS-.txt
Merkle Root Hash: 06873917e0bdad628ba615e1f7a5c1600cf5597dd4c40c389ea8ca7a3211b293
Digital Signature: Signature not available - Please contact administrator

🌳 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: debug_log-1.txt
Position in tree: 0
a03ba335d484d8388f4f7aa2f75602c0316d2d78941aa5c65271b90d338f8361
Leaf 2: HASHING-RESULTS-.txt
Position in tree: 1
5687dee23625be9c90580c691bd0557712a0492e02a79ac51dbc616f8e07f821

✅ 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:
06873917e0bdad628ba615e1f7a5c1600cf5597dd4c40c389ea8ca7a3211b293
💡 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/7789iop
📁 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 debug_log-1.txt a03ba335d484d838...5271b90d338f8361 2025-03-26 17:41:41
2 HASHING-RESULTS-.txt 5687dee23625be9c...1dbc616f8e07f821 2024-12-05 00:49:16

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

06873917e0bdad628ba615e1f7a5c1600cf5597dd4c40c389ea8ca7a3211b293
🏷️ 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 debug_log-1.txt 892d96d49048484b...bbd78a830eac58ed
2 HASHING-RESULTS-.txt 8e24c2b701df91ea...05f6086b5fc02a4f

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

8e91329467f652f936472aa0eeba035d262263e7227d115687be742f3c644208