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

Your Title Goes Here

ONE-30-two

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: ONE-30-two
✓ Verified
ONE-30-two • 3 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 3 Files
8810.txt_blockchain_certificate.pdf, 8804.txt_blockchain_certificate.pdf, 8802.txt_blockchain_certificate.pdf
Merkle Root Hash: 9fee59fc5becb9ef7b4986f714838076a974cc118c4666503c1ebe679327509c
Digital Signature & Verification ✓ Verified
ObHWqG+5Cw5UUU3L4PyYyCfhZuNx24Ju...

🌳 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: 8810.txt_blockchain_certificate.pdf
Position in tree: 0
54bd847634cf98bb6d6e922d65aba0c832065500b4a19a763be7cd28058beb9c
Leaf 2: 8804.txt_blockchain_certificate.pdf
Position in tree: 1
675236ff9998ba94bdb826e4430509175bb3c7f295196de90a7e0b28f4f202a8
Leaf 3: 8802.txt_blockchain_certificate.pdf
Position in tree: 2
97a8a8c46fbee237c0cabbe53efc220dbd619c07a294a1af24130c5472c87cdf

🔗 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:
54bd847634cf98bb6d6e922d65aba0c832065500b4a19a763be7cd28058beb9c...
Right input:
675236ff9998ba94bdb826e4430509175bb3c7f295196de90a7e0b28f4f202a8...
Result (SHA-256):
296862031f258916a38e9c994f8ef108be22e6ae6ac86e0514d76e8442d8f8ff
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
97a8a8c46fbee237c0cabbe53efc220dbd619c07a294a1af24130c5472c87cdf...
Right input:
97a8a8c46fbee237c0cabbe53efc220dbd619c07a294a1af24130c5472c87cdf...
Result (SHA-256):
8211ef8c87afa9ad857344924bdd6c5576a093751e45fdb61cfb4d3574967e17

✅ 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:
9fee59fc5becb9ef7b4986f714838076a974cc118c4666503c1ebe679327509c
💡 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/one-30-two
📁 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 8810.txt_blockchain_certificate.pdf 54bd847634cf98bb...3be7cd28058beb9c 2025-06-17 11:23:12
2 8804.txt_blockchain_certificate.pdf 675236ff9998ba94...0a7e0b28f4f202a8 2025-06-08 11:03:57
3 8802.txt_blockchain_certificate.pdf 97a8a8c46fbee237...24130c5472c87cdf 2025-06-10 10:26:36

🌳 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.

9fee59fc5becb9ef7b4986f714838076a974cc118c4666503c1ebe679327509c
🏷️ 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 8810.txt_blockchain_certificate.pdf 4b221f6fbf15448c...14accb1d8d911bcd
2 8804.txt_blockchain_certificate.pdf ad779f1c9b14118c...5e4246ab8485db16
3 8802.txt_blockchain_certificate.pdf 321c7c7b85dbf69a...7b5bda662c2133a4

🌳 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.

349fbfb38dfe3ed67a9cf081b41875ae88b063ef0825af9dd22d974cf03181df