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

Your Title Goes Here

SEVEN13

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: SEVEN13
✓ Verified
SEVEN13 • 4 artifacts • Oct 24, 2025
Collection Artifacts & Files ✓ 4 Files
8811.txt, ab551.txt, ab547.txt...
Merkle Root Hash: b2e9a36f30955d2f97e93f8c1152af4880290fd7bf443dc36bf448f1f8d98dee
Digital Signature & Verification ✓ Verified
qFkeJ4KRMMQ2GqoNDvT54V570ZRmRtnx...

🌳 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: 8811.txt
Position in tree: 0
e77454db32ef97333ee1caa0c03c5b1fe80ec55881f2d327784638f44af95a68
Leaf 2: ab551.txt
Position in tree: 1
915a84b8b5ea488240cf7bfc9c87ac7f698d689fc6634a1681374e37903ed13a
Leaf 3: ab547.txt
Position in tree: 2
e76b699395a4f87e66c5d137cb447f4c3aac1af68cfa63d2988bf65f5ec20cc1
Leaf 4: I-WANT-TO.txt
Position in tree: 3
266b285486e624d5c5ef78dfe3e8b1e943723035db187ed09c29509bc3a67629

🔗 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:
e77454db32ef97333ee1caa0c03c5b1fe80ec55881f2d327784638f44af95a68...
Right input:
915a84b8b5ea488240cf7bfc9c87ac7f698d689fc6634a1681374e37903ed13a...
Result (SHA-256):
8c91e8c968ff6d67f049e600c4f9df9ccc02a35783838a005859d8983bad535c
Node 2 = hash(Left3 + Right4)
Left input:
e76b699395a4f87e66c5d137cb447f4c3aac1af68cfa63d2988bf65f5ec20cc1...
Right input:
266b285486e624d5c5ef78dfe3e8b1e943723035db187ed09c29509bc3a67629...
Result (SHA-256):
7d68eacc5e00a962ec5fcc2308f3dfe30b01bee76be6c244af4799b5e43851c6

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