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

Your Title Goes Here

NEWCOLL-905AM

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: NEWCOLL-905AM
✓ Verified
NEWCOLL-905AM • 3 artifacts • Oct 16, 2025
Collection Artifacts & Files ✓ 3 Files
20250530-Gmail-Case-60053943.pdf, 5265163306.pdf, google-meeting-aug-6.txt
Merkle Root Hash: 7f51c3f65e7181b82027501b1cc7f4ea4b4f3d7e13e0357364598b1e95fee3f7
Digital Signature & Verification ✓ Verified
kSS36azW8CiS2Kr3K4rzgNSj4BpS3s7y...

🌳 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: 20250530-Gmail-Case-60053943.pdf
Position in tree: 0
95a53ece7e55954f6ed97f3ca58761b083f68745ecdc5df06bc8fb78caca8769
Leaf 2: 5265163306.pdf
Position in tree: 1
36e396f848715847bf5a6441b46d5e85ee55e0799c96a13703c9cf14f38e91ac
Leaf 3: google-meeting-aug-6.txt
Position in tree: 2
340d9ab6f21bb69be7a270b1ad365023a8cb8b0be4b5012810377724b37e47cf

🔗 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:
95a53ece7e55954f6ed97f3ca58761b083f68745ecdc5df06bc8fb78caca8769...
Right input:
36e396f848715847bf5a6441b46d5e85ee55e0799c96a13703c9cf14f38e91ac...
Result (SHA-256):
3807d0614db0f3cea1ffcc033105414b7c8fe8674aa19d7d964ea84f901c4ca4
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
340d9ab6f21bb69be7a270b1ad365023a8cb8b0be4b5012810377724b37e47cf...
Right input:
340d9ab6f21bb69be7a270b1ad365023a8cb8b0be4b5012810377724b37e47cf...
Result (SHA-256):
b25b8a9c5093b829c09b88f9b4e1ca3a92b7844ebc0ef2ecd549bf60c257f6ad

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