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

Your Title Goes Here

1forty3

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: 1forty3
✓ Verified
1forty3 • 3 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 3 Files
add_filter-to-functions_php.txt, blockchain-technology-the-detection-of-AI.txt, CODE-BREAKDOWN.txt
Merkle Root Hash: b74154727dc8014ee76140f6f304154b5b073901cd83477b2779892a4270a517
Digital Signature & Verification ✓ Verified
bEHSm4N6txivJ4EJFlzh96Itx44GJ7/H...

🌳 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: add_filter-to-functions_php.txt
Position in tree: 0
3b3f787b11717fcdd8ba50eb208f3bf550aa8fe44d633ff9c721a4056f376bb1
Leaf 2: blockchain-technology-the-detection-of-AI.txt
Position in tree: 1
7bdc9e1b0b40c8ce0e2705a6c7a7550489ee60bd9fb767def0f49efe344108d4
Leaf 3: CODE-BREAKDOWN.txt
Position in tree: 2
3254288280eb39752b0e00d54688a1574aff5502a79a49da999280e869cc97d4

🔗 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:
3b3f787b11717fcdd8ba50eb208f3bf550aa8fe44d633ff9c721a4056f376bb1...
Right input:
7bdc9e1b0b40c8ce0e2705a6c7a7550489ee60bd9fb767def0f49efe344108d4...
Result (SHA-256):
4da49bc3126c4b503bc0362b62ab0293f0822fb8fa1b665009c4c196bc711661
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
3254288280eb39752b0e00d54688a1574aff5502a79a49da999280e869cc97d4...
Right input:
3254288280eb39752b0e00d54688a1574aff5502a79a49da999280e869cc97d4...
Result (SHA-256):
f5caec37a3c81547e2e79849e3b0898cb6676fd6d8d10cfb1addd4e9cb028140

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