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

Your Title Goes Here

1104am

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: 1104am
✓ Verified
1104am • 3 artifacts • Nov 30, -0001
Collection Artifacts & Files ✓ 3 Files
539pm-zzxxcerr45_VerificationReport.txt, 449PM-TRYY_VerificationReport_2025-.txt, 434pm-2xz_VerificationReport_2025-0.txt
Merkle Root Hash: 520a37934403fd65c69afdb96810c110d6207c78e083ebb746edd4d55ccb2c8f
Digital Signature & Verification ✓ Verified
hnfm32idaAmRT+eC7nyS7E5iPex8aFyH...

🌳 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: 539pm-zzxxcerr45_VerificationReport.txt
Position in tree: 0
cc5b37e91acd030f5c75c083d564906aa3c9efa416963fdcf2e0d59907d6e5a3
Leaf 2: 449PM-TRYY_VerificationReport_2025-.txt
Position in tree: 1
ef321ac19155963e4a2caecdcd6035c592c9f93573bf99c0f52793431a319bec
Leaf 3: 434pm-2xz_VerificationReport_2025-0.txt
Position in tree: 2
464d1eaee3bee8d2cea62c27e2bbebec19837d22a682be3301a5c91ee6628696

🔗 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:
cc5b37e91acd030f5c75c083d564906aa3c9efa416963fdcf2e0d59907d6e5a3...
Right input:
ef321ac19155963e4a2caecdcd6035c592c9f93573bf99c0f52793431a319bec...
Result (SHA-256):
940aefcc712f628ea65c4c4b9bdfc107a834d1f60f8cdea1a0789455bef5a3c1
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
464d1eaee3bee8d2cea62c27e2bbebec19837d22a682be3301a5c91ee6628696...
Right input:
464d1eaee3bee8d2cea62c27e2bbebec19837d22a682be3301a5c91ee6628696...
Result (SHA-256):
4e0bba643c224860b17d6a9e1a56e35421296bf73411c37f1ea889760d224941

✅ 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:
520a37934403fd65c69afdb96810c110d6207c78e083ebb746edd4d55ccb2c8f
💡 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