Note: These demos are designed for desktop browsers. Some features may not work on mobile devices.
Demo 5 — Environment-Derived Component

Two fragments provided.
Third from display.

Real implementation with environmental component. Unlike stored fragments, this demo uses two provided fragments plus a third derived from your display environment itself. Try to steal this fragment - you can't. It exists only as a computation based on system properties, making this a truly unstealable component. Only with all three fragments can the data be reconstructed.

Environment Check
Your Display Environment

The third fragment is only valid on a 1024×768 display. Other resolutions generate different fragments that won't reconstruct the data.

🗺
Current Display

Detecting...

🔒
Fragment Status

Checking environment...

🗗
Data Access

Unknown

Fragment Collection
Component Assembly

We have two fragments ready. The third fragment is calculated from your display environment. All three are needed to reconstruct the data.

🔑 Fragment 1 (Server Component)
S1 = "8f3a7b9c2d5e1f4a6b8c0d7e3f9a2b5c6"

This fragment is stored on the server in production. For this demo, it's simulated locally in the browser.

📱 Simulated in-browser
🔑 Fragment 2 (Browser Component)
S2 = "d1e4f7a9b0c3d6e8f1a4b7c0d3e6f9a2b"

This fragment is stored in browser storage. It's the second piece needed for reconstruction.

Fragment 3 (Environment Component)

Calculated from your display environment - only works on 1024×768

Fragment 1
8f3a7b9c2d5e1f4a6b8c0d7e3f9a2b5c6
+
Fragment 2
d1e4f7a9b0c3d6e8f1a4b7c0d3e6f9a2b
+
Fragment 3
calculating...
=
Result
incomplete without all fragments

🔍 Real Environmental Component

Unlike traditional security fragments, the third component in this demo is actually computed from your display properties - it's never stored anywhere and cannot be stolen. This demonstrates the core innovation of environmental-derived security components.