Proviso
02 / PROOF OF CALL

Before the outcome.
On the record.

A timestamped commitment to the idea you actually made. Entry and exit are sealed separately, then disclosed as the thesis unfolds.

THESIS TRADING / PROVISO
RECORD / 0001
ENTRY HASH0x ▪▪▪▪ ▪▪▪▪ ▪▪▪▪
EXIT HASH0x ▪▪▪▪ ▪▪▪▪ ▪▪▪▪
OWNER SIGNEDEXPIRY ≤ 30 DAYS
01 / THE COMMITMENT

The device prepares.
The owner signs.

01

Canonicalize

Entry and exit each become a deterministic JSON representation using RFC 8785.

02

Salt & hash

The device generates two separate 32-byte salts and computes Keccak-256 commitments.

03

Sign the stamp

An EIP-712 signature covers the owner, hashes, expiry, nonce, and deadline.

04

Relay & retain

ThesisSeal records the stamp. Signed-at and stamped-at remain separate. The user keeps an encrypted export of specification and salts.

02 / DISCLOSURE TIMELINE

Privacy has
a defined horizon.

01FIRE / RECORD EVENT

The entry opens.

The executor is designed to reveal the entry within one minute. The exit commitment remains private.

03 / EVIDENCE, IN SEQUENCE

Small events.
A verifiable trail.

HOURLY MERKLE ROOT
SEQ 01FIRE
SEQ 02FILL
SEQ 03EXIT
SEQ 04PNL
SEQ 05EXPIRE

A gap should leave a trace.

Each event leaf includes the thesis ID, its sequence number, event kind, and data. Hourly roots and leaf counts are posted to StampRoots. The proof API is designed to connect an event to a committed root.

Timing is evidence, not quality.

A stamp does not prove that an idea is profitable or show every wallet a caller controls. Proviso remains the event poster. The evaluator must decrypt sealed rules inside an isolated environment to run them.

Inspect how a record is built.

Explore the commitment parameters, event types, and reveal states in the workspace.

Open Proof of Call