Jackfa
02 / PLAN LOCK

Before the move.
On the record.

A timestamped commitment to the plan you actually made. Entry and exit are locked separately, then revealed as the trade plays out.

STATUS / IN DEVELOPMENT · ROADMAP
LOCK / 0001
ENTRY HASH0x ▪▪▪▪ ▪▪▪▪ ▪▪▪▪
EXIT HASH0x ▪▪▪▪ ▪▪▪▪ ▪▪▪▪
OWNER SIGNEDEXPIRY ≤ 30 DAYS
01 / THE LOCK

The plan is hashed.
The owner signs.

01

Canonical form

Entry and exit are each written in one fixed form, so the same rule always produces the same hash.

02

Salt & hash

Each side gets its own random salt, and a salted hash is computed for entry and for exit separately.

03

Owner signs

Your signature covers you as owner, both hashes, the expiry, and the moment of the lock.

04

Timestamp & hold

The lock is timestamped and added to the record. The rules and their salts stay private until the reveal.

02 / REVEAL TIMELINE

Private until
it matters.

01FIRE / RECORD EVENT

The entry is revealed.

When the plan fires, its entry rule and salt are revealed so they can be checked against the lock. The exit stays private.

03 / PROOF, IN ORDER

Every event.
A trail you can check.

HOURLY PUBLISHED ROOT
SEQ 01FIRE
SEQ 02FILL
SEQ 03EXIT
SEQ 04RESULT
SEQ 05EXPIRE

A missing event shows.

Each event carries the plan ID, its sequence number, the event type, and its data. Events are grouped into hourly roots that are published, so any single event can be proven against its root.

A lock proves timing, not quality.

A lock does not show that a plan is any good, or reveal every account an author trades from. Jackfa still posts the events, and it must be able to read a locked rule in order to watch for it.

See how a lock is made.

Look at the lock fields, the event types, and every reveal state in the workspace.

Open plan lock