Cardano BuildersFund

Proof of Control

Prove wallet control — by signature, never custody

A design preview for proving control of a wallet by signing a short, harmless message (CIP-30 signData). It is not implemented: no ADA moves, no transaction is signed, and no private key is ever requested.

Proof-of-control design preview only. No transaction signing, no ADA moved, no payment, and no signData call. This describes intended design.

Why proof-of-control matters

To attribute activity to a wallet — a builder’s identity, a contributor’s record — without custody, the holder proves they control the wallet by signing a message. A signature authorizes nothing on-chain and moves no funds. It proves control of the key at signing time; it does not prove ownership of funds, identity, or intent to pay. See the wallet foundation.

Future challenge preview

The shape of the message a wallet would sign. Illustrative demo values — no real challenge is issued and nothing is signed.

Demo challenge

Preview only
domain
cardano.builders
network
preprod (demo)
timestamp
2026-01-01T00:00:00Z (demo)
nonce
demo-nonce-0000 (single-use, illustrative)
purpose
Prove wallet control
contextId
demo-1 (optional)

Future verification steps

The planned flow from challenge to recorded proof. None of it runs today.

  1. 1

    Request a challenge

    The server would issue a single-use message + nonce bound to the address. Not implemented.

  2. 2

    Sign the message

    The wallet would sign the message via CIP-30 signData — a signature, never a transaction. Not implemented.

  3. 3

    Verify the signature

    The server would verify the signature against the address and consume the nonce. Not implemented.

  4. 4

    Record the proof

    The proof would be recorded (Wallet + AuditLog) only after DB activation. Not implemented.

Preview only — nothing here is live

  • No ADA is moved and no transaction is signed.
  • Proof is a message signature only — it authorizes nothing on-chain.
  • No seed phrase or private key is ever requested — never share one.
  • signData is not called; this is a design preview only.
  • No database write happens; Prisma is not used in any app route.

Design preview only. See infrastructure readiness and status & roadmap. Nothing here is legal, tax, or financial advice.