Engineering Sandbox lab ยท signatures and trust

Generate keys, sign a message, then break trust with one edit.

This lab is easiest to read as a four-step workflow. First create an identity, then attach a signature to data, then mutate that data, and finally check whether the verification state still deserves to pass.

Generate a keypairSign a payloadMutate and verify
Try this first

Press Random to create a fresh keypair, then jump to the Signatures tab and sign a short message. The clearest moment in the demo is what happens after you change the signed message by a single character.

Generate keysOpen signatures

Manipulation checklist

  • 1
    Generate. Create a new private key and watch the public key update immediately.
  • 2
    Sign. Move to the signatures scene and attach a signature to a concrete message.
  • 3
    Mutate. Change the message after signing so you can test whether the old signature still deserves trust.
  • 4
    Verify. Use the verification views to see success and failure states side by side.

Flow hint

The tabs already separate the family into keys, signatures, transactions, and blockchain. The shell stays compact on purpose so the runtime can remain the teacher once you know which action to try next.

Public / Private Key Pairs

Continue the flow

This page only establishes the identity layer. The real pay-off happens when you carry the same keypair into message signing, transaction construction, and the blockchain view that consumes signed data.

Open signaturesOpen transaction flow

What to do next

  • 1
    Keep this keypair. The later tabs reuse the same identity.
  • 2
    Sign a message. Create a payload and attach proof that it came from this key.
  • 3
    Mutate and verify. Change the data and watch trust collapse immediately.