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

Your Title Goes Here

12forty4

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: 12forty4
✓ Verified
12forty4 • 3 artifacts • Oct 15, 2025
Collection Artifacts & Files ✓ 3 Files
NDA_Hillier20250824.txt, 8810.txt_blockchain_certificate.pdf, 8804.txt_blockchain_certificate.pdf
Merkle Root Hash: f4849e2e79d45d0f9a2eeadfa98d4467b5d9c64615e4a1c903707c71927e3abd
Digital Signature & Verification ✓ Verified
jXCC2I2wuXu8YYH18mhwrWj8S1yTGOVT...

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

🔗 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:
e286bdba01b14f5da8d2630ea3fc72a228c98f30527f48c65f2a4d5bcd16c492...
Right input:
54bd847634cf98bb6d6e922d65aba0c832065500b4a19a763be7cd28058beb9c...
Result (SHA-256):
ad4e70261b6f9e7fdac2537f13d89022d8ec30934a63c25344535a5a7efd3da2
Node 2 = hash(Left3 + Right4) (duplicated for odd count)
Left input:
675236ff9998ba94bdb826e4430509175bb3c7f295196de90a7e0b28f4f202a8...
Right input:
675236ff9998ba94bdb826e4430509175bb3c7f295196de90a7e0b28f4f202a8...
Result (SHA-256):
4b6a5b3c1ebd840a5f5fb7476d0ca38214cd9ffc73aaf0f80048278bd6a6e702

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