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

Your Title Goes Here

845PM

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: 845PM
✓ Verified
845PM • 4 artifacts • Oct 26, 2025
Collection Artifacts & Files ✓ 4 Files
public_key_smokeybacon.txt, 9802.txt, 9801.txt...
Merkle Root Hash: 2625e27d40f8f625444ef20b7e7ea489018a77d3ae5604d4c910b2c64813f84b
Digital Signature & Verification ✓ Verified
afE/HBQCYVsm6yIywktQJ9JZGMJ1gvkF...

🌳 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.txt
Position in tree: 0
5bd3b5b5720ff6c8d7d93f7d209ad7cb86de8b0a4f0d4a428fee1998dff74e61
Leaf 2: 9802.txt
Position in tree: 1
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b
Leaf 3: 9801.txt
Position in tree: 2
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b
Leaf 4: 8812.txt
Position in tree: 3
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b

🔗 Level 1: Intermediate Nodes

Pairs of hashes from the level below are combined and hashed together to create this level.

Node 1 = hash(Left1 + Right2)
Left input:
5bd3b5b5720ff6c8d7d93f7d209ad7cb86de8b0a4f0d4a428fee1998dff74e61...
Right input:
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b...
Result (SHA-256):
c3dfacc0b4ff4c0ca4c824e2a176cc7fb933605d86e34bed78addd6d578f37c7
Node 2 = hash(Left3 + Right4)
Left input:
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b...
Right input:
7cdae41979f5481ae50f2df7b2708e6fd2296d1ed5ac4213f381ade6125c6d6b...
Result (SHA-256):
ba1068bf79b4560cbb5e8bf6157e5123085acdefe0c89f1a6d44387f972d02c1

✅ 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:
2625e27d40f8f625444ef20b7e7ea489018a77d3ae5604d4c910b2c64813f84b
💡 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