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

Your Title Goes Here

6666

Production Portfolio
Mr. Smokey Bacon
Creator Information

Mr. Smokey Bacon

✓ Verified
Creator Name:
Mr. Smokey Bacon
Creator Alias
smokeybacon
Creator Email
[email protected]
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: 6666
✓ Verified
6666 • 3 artifacts • Nov 30, -0001
Collection Artifacts & Files ✓ 3 Files
public_key_smokeybacon.txt, I-WANT-TO.txt, puddingify-1.txt
Merkle Root Hash: effa1543ae417d211155015bf7ae85f71e7fb498aef2d78281fbebf393fcb42c
Digital Signature & Verification ✓ Verified
Q1oCQtmr9c7MFOcV9PO1zg+FC2Z+ep+/...

🌳 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: I-WANT-TO.txt
Position in tree: 1
266b285486e624d5c5ef78dfe3e8b1e943723035db187ed09c29509bc3a67629
Leaf 3: puddingify-1.txt
Position in tree: 2
c376e04608be1506706cf999baab42ee715c55649e76b6ed318bbf71f27ea3c2

🔗 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:
5bd3b5b5720ff6c8d7d93f7d209ad7cb86de8b0a4f0d4a428fee1998dff74e61...
Right input:
266b285486e624d5c5ef78dfe3e8b1e943723035db187ed09c29509bc3a67629...
Result (SHA-256):
eeb37d2dd4dcb66190f2877baea26f8198320de5dce4b4f221b1ed0ed9be00a1
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
c376e04608be1506706cf999baab42ee715c55649e76b6ed318bbf71f27ea3c2...
Right input:
c376e04608be1506706cf999baab42ee715c55649e76b6ed318bbf71f27ea3c2...
Result (SHA-256):
197e53dd6f0dcd73a578bd83dd93d3bf62a6c25630d3350accd0f23e156f6cfe

✅ 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:
effa1543ae417d211155015bf7ae85f71e7fb498aef2d78281fbebf393fcb42c
💡 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
📁 Portfolio Metadata & Verification ✓ Available
Permalink:
https://puddingify.com/creator-profile/smokeybacon/portfolio/6666
📁 File Content Manifest ✓ Verified

SHA-256 hashes of each file's content. These prove the files haven't been tampered with.

# Filename Content Hash (SHA-256) Date Actions
1 public_key_smokeybacon.txt 5bd3b5b5720ff6c8...8fee1998dff74e61 2025-09-20 18:17:15
2 I-WANT-TO.txt 266b285486e624d5...9c29509bc3a67629 2025-10-20 12:51:48
3 puddingify-1.txt c376e04608be1506...318bbf71f27ea3c2 2025-05-18 11:21:21

🌳 File Content Manifest Hash (Merkle Root)

Purpose: Cryptographic proof that all file contents are unchanged

This Merkle root is computed from all file content hashes using a binary tree structure. Any change to any file will change this root hash.

effa1543ae417d211155015bf7ae85f71e7fb498aef2d78281fbebf393fcb42c
🏷️ Filename Manifest ⚠️ Modified
⚠️ WARNING: Filenames have been modified!

The current filenames do not match the original manifest hash stored in the database.

SHA-256 hashes of the filenames themselves. Independent verification of which files are included.

# Filename Filename Hash (SHA-256) Actions
1 public_key_smokeybacon.txt 58d2a5f90dab23a5...0c5c640917e5054c
2 I-WANT-TO.txt cf136ccda99b4cec...b8a2b9c79b8f603a
3 puddingify-1.txt 4ec3c59382f3c5ce...1b2531e2cb7576c2

🌳 Filename Manifest Hash

Purpose: Proves the list of filenames hasn't been altered

This is a SHA-256 hash of the JSON structure containing all filenames and their metadata. It serves as a tamper-evident seal for the manifest document itself.

05ea750528c3f4a0a28cbf229a99b6303a578726ff80e3eccfd12d0bb97c4a89