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

Your Title Goes Here

1101_SUNDAY1

Production Portfolio
Mr. Smokey Bacon
Creator Information

Mr. Smokey Bacon

✓ Verified
Creator Name:
Mr. Smokey Bacon
Creator Alias
smokeybacon
Creator Email
About The Creator:
Tech/ blockchain entrepreneur
Creator Location:
Toronto | Canada
Creator's Public Key & Authentication ✓ Valid Key
-----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB...
🔒 X.509 Digital Certificate ✓ Valid
Serial Number:
6f0b871e427f836b487615f5b6b6ccd46d5f0123...
SHA-256 Fingerprint:
eed2f37e2b6ff7785c413d61b1656cc07d19341c...
Certificate Status:
✓ ACTIVE & VALID
Certificate is currently valid and active.
Originally Valid From: November 23, 2025
Valid Until: November 21, 2035
Issued By:
C=CA, ST=ONTARIO, L=TORONTO, O=Puddingify Creators Network, OU=Certificate Authority, CN=Puddingify Root CA, [email protected]
📊 Portfolio Collection: 1101_SUNDAY1
✓ Verified
1101_SUNDAY1 • 2 artifacts • Nov 2, 2025
Collection Artifacts & Files ✓ 2 Files
NDA_Hillier20250824.txt, FredHillier_NDA_20250823.txt
Merkle Root Hash: 8039c62f147caca386aa79817d1e2f9ad3ef61cd36898632833b0ea0dcb84f46
Digital Signature & Verification ✓ Verified
Vkc4rJmGUoTXnKYqqvYtuF0qqK1XKYSU...

🌳 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: NDA_Hillier20250824.txt
Position in tree: 0
55c21a3289f152632472081498f61151b6cf69b7e8bf3baca0c71f61acc63ae1
Leaf 2: FredHillier_NDA_20250823.txt
Position in tree: 1
55c21a3289f152632472081498f61151b6cf69b7e8bf3baca0c71f61acc63ae1

✅ 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:
8039c62f147caca386aa79817d1e2f9ad3ef61cd36898632833b0ea0dcb84f46
💡 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