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

Your Title Goes Here

SIX22-PM

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: SIX22-PM
✓ Verified
SIX22-PM • 4 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 4 Files
AI-Hashtag-Generator.txt, nginx-service.txt, tracing.txt...
Merkle Root Hash: 2a35d11774807cfdcaf04f18dc4b740ecf59e5c03442cbe635ba6a2b6fccbdf2
Digital Signature & Verification ✓ Verified
WbwV/xhMeHdu9xLqx1zhSfYVRUDq5en5...

🌳 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: AI-Hashtag-Generator.txt
Position in tree: 0
9121571d5ce70f4a9c80141a60ef7862972f66ac5a59fc879b265eb7729c5b8f
Leaf 2: nginx-service.txt
Position in tree: 1
52ed0753030f3955e55eba780e15d69a53b7d91bdab54f77666e4f1aabe60adf
Leaf 3: tracing.txt
Position in tree: 2
60228a0a1b714eaa708dd7e7b275adb2b7b39a35eed07176a073e5b8f6a0ad1c
Leaf 4: webserver.txt
Position in tree: 3
2627930da1ef663a2ca9dcd220973423d722e20cb8f9896d0800193ad385ad9b

🔗 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:
9121571d5ce70f4a9c80141a60ef7862972f66ac5a59fc879b265eb7729c5b8f...
Right input:
52ed0753030f3955e55eba780e15d69a53b7d91bdab54f77666e4f1aabe60adf...
Result (SHA-256):
7beac9f6e4dc998279bba1d4deefb7c2351eb9ffcf9607bd5573930ccdaa18e2
Node 2 = hash(Left3 + Right4)
Left input:
60228a0a1b714eaa708dd7e7b275adb2b7b39a35eed07176a073e5b8f6a0ad1c...
Right input:
2627930da1ef663a2ca9dcd220973423d722e20cb8f9896d0800193ad385ad9b...
Result (SHA-256):
cd4562c7f6d93593e510e791234b525e25605b3726c2c037e7714857568f4b6d

✅ 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:
2a35d11774807cfdcaf04f18dc4b740ecf59e5c03442cbe635ba6a2b6fccbdf2
💡 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/six22-pm
📁 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 AI-Hashtag-Generator.txt 9121571d5ce70f4a...9b265eb7729c5b8f 2024-12-13 02:15:05
2 nginx-service.txt 52ed0753030f3955...666e4f1aabe60adf 2024-12-16 03:40:53
3 tracing.txt 60228a0a1b714eaa...a073e5b8f6a0ad1c 2024-12-09 02:12:41
4 webserver.txt 2627930da1ef663a...0800193ad385ad9b 2024-11-28 13:15:47

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

2a35d11774807cfdcaf04f18dc4b740ecf59e5c03442cbe635ba6a2b6fccbdf2
🏷️ 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 AI-Hashtag-Generator.txt eaa9fc8dc082bded...2fca7bb4b194b636
2 nginx-service.txt e9f5d767bfd5137f...1d8d471bcf08932d
3 tracing.txt 05a9d91a179c793a...e83924d30489f440
4 webserver.txt e172428f1dce243d...cd84ea90a76bf0b0

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

12a18ec3c626168c25cfd6932e33416613ddd030643526bbe9ee8654a30fd7ca