Proof without exposure.

Every important agreement eventually becomes a question. NightSign answers it — without exposing the document behind it.

LOCAL SHA-256 RECEIPTSNO ACCOUNTS TO VERIFYNO FIELD PLACEMENT. EVER.BUILT FOR MIDNIGHT

Signing should come with a receipt.

The whole record stays private. Only the proof comes out.

NightSign doesn’t publish the interview, the answers, or the attachments. It records the fingerprint and the few facts anyone needs to verify — nothing else leaves the room.

What really happened · stays with you
InterviewerAlex Hernandez
ParticipantRamona
Q1 · scope of work“We agreed the engagement covers…”
Q2 · fees“Retainer of $—, billed monthly…”
Q7 · confidential“Client’s account numbers are…”
Attachmentsnotes.pdf · call-audio.m4a · photos
Internal comments3 private notes
Contactphone · email · address
What NightSign proves · leaves the room
PacketInterview-001
ParticipantRamona
Version1.2
AcknowledgedAug 8, 2026
Receipt IDNS-2026-0808-4F2A
Integrity verifiedPublic check availableIndependently verifiable

See how a NightSign acknowledgment works

nightsign · packet
CONSULTING AGREEMENT
You'll be asked to acknowledge
— I reviewed this agreement
— I understand this creates a verifiable receipt

DAY · WHERE READING AND SIGNING HAPPEN

Ink on paper. Like it always was.

Signatures started as black ink on white paper — clear terms, plain sight, no clutter. NightSign keeps the paper and upgrades the proof. Anywhere you read or commit, the surface is paper. The dark is reserved for what we show you, never for what you must read.

NO SETUP

No box dragging

Packets declare what must be acknowledged. Senders never place signature fields; signers never hunt for them. The document is the interface.

HONEST PROOF

Receipts that tell the truth

Every receipt states exactly what it proves — and just as clearly, what it doesn't. No inflated claims, no fine-print surprises.

OPEN VERIFY

Verify in seconds

Paste a receipt ID or hash. No account, no upload of private content. Anyone you hand a receipt to can check it.

PACKET→ACKNOWLEDGE→RECEIPT→VERIFYfour steps · no accounts · no clutter

Today

Built for today's workflows.

Organizations already need to prove who acknowledged what. NightSign produces independently verifiable receipts while keeping the underlying documents private.

Tomorrow

Ready for tomorrow's workflows.

The same receipt model can extend naturally to automated and agent-driven systems as organizations adopt AI-assisted workflows.

NIGHT · WHERE PRIVACY LIVES

Midnight inside.

A lets you prove a fact without exposing the document behind it. What you choose to disclose steps into the light. Everything else stays in the dark — provable, but private. That is the layer NightSign is building on the Midnight Network — demo-proven on a standalone Midnight network, with production anchoring our next chapter.

  • Prove an agreement was signed without revealing its contents
  • Disclose single facts — a date, a version, a party — not the whole record
  • Selective disclosure enforced by cryptography, not by policy promises

AGREEMENT · PRIVATE RECORD

This agreement was signed · version v1.2PROVEN · NOT REVEALED

ROADMAP CONCEPT — ZK SELECTIVE DISCLOSURE ON MIDNIGHT

Your next agreement, in black and white.

Quick to send. Effortless to sign. Provable for as long as you keep the receipt.

V0 BOUNDARY — this demo proves local packet acknowledgment and receipt verification. It does not yet prove legal identity, notarization, wallet ownership, persistence, or Midnight anchoring.

Cora

NightSign orientation helper

START
Home

This is NightSign — signing turned into proof. Read on paper, acknowledge what matters, and walk away with a receipt anyone can verify in seconds.

Ask from here. Cora can explain what this NightSign page is for, what matters on it, and what the next step is.