Engineering Sandbox lab · privacy proofs

Hide the coloring, reveal it, shuffle it, then test whether the map logic still holds.

What can two revealed regions tell you without showing the whole coloring? Hide the map, select two neighboring states, then compare their colors. Shuffling changes color labels, not the partition. This illustrates selective disclosure, not a secure proof protocol.

Reveal the hidden classes Shuffle the visible palette Probe region logic without long prose
Try this first

Start by showing the colors once so you know the hidden partition exists, then hide them again and click a few states. The key move is comparing what you can infer from a local reveal versus what stays hidden until you ask for the full overlay.

Reveal the map Jump to the map

Manipulation checklist

  • 1
    Reveal. Show the hidden color classes once so you understand the secret partition.
  • 2
    Shuffle. Change the palette without changing the underlying region logic.
  • 3
    Select. Click regions to inspect local evidence while the rest of the map stays concealed.
  • 4
    Reset. Click the background to clear the current reveal and compare it with the default hidden state.

Why this format

The shell stays intentionally light here. The map is the concept, so the framing only clarifies the state transitions instead of trying to compete with the interaction.

Rounds tested 0
Illustrative confidence 0%
Selection No states selected

The partition starts hidden. Reveal it once, then hide it again before running local challenge rounds.

The displayed percentage is illustrative: 1 − 2−rounds assumes independent challenges with a one-half cheating success rate. This demo counts any pair, does not check adjacency or verify a cryptographic commitment, and does not establish those assumptions. Reset Rounds clears the counter, not the coloring. Continue from the Blockchain Combined Flow when you want the full local path from hashing to privacy.