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

Your Title Goes Here

NEW_PF

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: NEW_PF
✓ Verified
NEW_PF • 3 artifacts • Oct 26, 2025
Collection Artifacts & Files ✓ 3 Files
NEW_PORT_Portfolio_20251021.txt, what-is-x509.txt, NDA_Hillier20250824.txt
Merkle Root Hash: 8af81f3d8ec30b06b3431c9efe70b90de5786804313072030e8001e0a3b417e4
Digital Signature & Verification ✓ Verified
Z8sM1eAwuj/nnr3HFm4OUwTZ53sbsm2x...

🌳 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: NEW_PORT_Portfolio_20251021.txt
Position in tree: 0
a0f148616f118ff8ed4695650ad9eab744e6e26efdbfa4b87f02dc857bd8af5a
Leaf 2: what-is-x509.txt
Position in tree: 1
5c450a6e26a7f2f4520a5b4579737da5252278d177b3184230d8a2ff1d54dffd
Leaf 3: NDA_Hillier20250824.txt
Position in tree: 2
55c21a3289f152632472081498f61151b6cf69b7e8bf3baca0c71f61acc63ae1

🔗 Level 1: Intermediate Nodes

Pairs of hashes from the level below are combined and hashed together to create this level. (Odd number detected: last hash is duplicated for pairing)

Node 1 = hash(Left1 + Right2)
Left input:
a0f148616f118ff8ed4695650ad9eab744e6e26efdbfa4b87f02dc857bd8af5a...
Right input:
5c450a6e26a7f2f4520a5b4579737da5252278d177b3184230d8a2ff1d54dffd...
Result (SHA-256):
df63c8d737609653e8f4060e22cb7c12e92da6cfc338dfd0803aca44bff493a3
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
55c21a3289f152632472081498f61151b6cf69b7e8bf3baca0c71f61acc63ae1...
Right input:
55c21a3289f152632472081498f61151b6cf69b7e8bf3baca0c71f61acc63ae1...
Result (SHA-256):
8039c62f147caca386aa79817d1e2f9ad3ef61cd36898632833b0ea0dcb84f46

✅ 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:
8af81f3d8ec30b06b3431c9efe70b90de5786804313072030e8001e0a3b417e4
💡 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