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

Your Title Goes Here

OCT21_232PM

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: OCT21_232PM
✓ Verified
OCT21_232PM • 2 artifacts • Nov 30, -0001
Collection Artifacts & Files ✓ 2 Files
Im-so-lonesome-in-my-saddle.txt, 9804.txt
Merkle Root Hash: 7f0a07842e3529a07848ab3118b6baf5fd5f2c3e1dd96584cec5222d22eb9db8
Digital Signature & Verification ✓ Verified
HV43r/YVHT68K+JCyQ0rIC20PObP+Ukb...

🌳 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: Im-so-lonesome-in-my-saddle.txt
Position in tree: 0
090e68a9d5c9918ef12e659cdd1d6d160641b8e18e01d850c990cf752fa6e7b4
Leaf 2: 9804.txt
Position in tree: 1
8bddf13b49e1ef61c326f1472287f24fd693e773927af5f042c1cc6d272a3bdd

✅ 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:
7f0a07842e3529a07848ab3118b6baf5fd5f2c3e1dd96584cec5222d22eb9db8
💡 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