FORKLOCKOpen demo
00Cryptographic execution infrastructure

COMMIT FIRST.
VERIFY EXECUTION.

Define transaction conditions before execution. Verify what actually happened afterward. Build applications where execution claims can be checked, not blindly trusted.

// protocol status
// execution claims require evidence
// demo environment / no network calls
01PRE-EXECUTION COMMITMENTS
02EXECUTION CONSTRAINTS
03POST-EXECUTION VERIFICATION
01The execution lifecycle

Conditions are defined before the transaction exists.

01

DEFINE

The application defines intended transaction parameters.

02

COMMIT

Canonicalize and hash the conditions with SHA-256.

03

EXECUTE

Submit for execution. Simulation is only an estimate.

04

VERIFY

Compare evidence against the committed policy.

02Working browser demonstration

FORKLOCK
COMMITMENT LAB

Create a deterministic commitment from transaction conditions. The browser Web Crypto API computes the actual SHA-256 digest.

LOCAL DEMO / NO SIGNATURE REQUEST
Canonical payload

Generate a commitment to inspect
the canonical representation.

A hash proves integrity when compared against the original data. It does not prove that inputs were honest, that conditions were enforced, or that execution succeeded.

03Integrity test

CHANGE ONE PARAMETER.
BREAK THE COMMITMENT.

Recompute the digest after editing a committed value. One byte of change creates a completely different result.

Input

1.00 SOL

Minimum output
Max slippage

0.5%

04Execution verification dashboard

EVIDENCE, NOT ASSUMPTION.

A simulated report makes the boundary clear: this interface does not inspect a live chain or mark unknown conditions as passed.

DEMO DATA
Commitment ID

FL-DEMO-7A2C91F4

Transaction signature

Not available

Committed input

1.00 SOL

Minimum expected output

100 USDC

Actual observed output

Not verified

Target program

Not configured

Execution slot

Not available

Verification status

INCONCLUSIVE

Condition checklist
Committed parameters matchPASS
Transaction signature is validNOT VERIFIED
Transaction execution succeededNOT VERIFIED
Target program matches policyNOT VERIFIED
Actual output satisfies minimumNOT VERIFIED
Required conditions satisfiedNOT VERIFIED
05Developer documentation

OVERVIEW

FORKLOCK separates intent, execution, and evidence. A cryptographic commitment binds a canonical representation to a digest; it does not enforce conditions by itself. Enforcement must come from the transaction, target program, or another trusted or verifiable mechanism.

DEFINE CONDITIONS
→ CANONICALIZE PARAMETERS
→ CREATE COMMITMENT
→ EXECUTE TRANSACTION
→ COLLECT EXECUTION EVIDENCE
→ VERIFY CONDITIONS
→ PRODUCE REPORT
06Threat model and limitations

WHAT THE MODEL
DOES NOT CLAIM.

01Parameters changed after a commitment is created.
02Simulation diverges from actual execution as state changes.
03Incorrect verification logic or incomplete evidence.
04Unexpected instructions or stale state assumptions.
05A hash does not prove the original input was truthful.
06A commitment alone cannot prevent front-running or reordering.
07A valid signature does not prove the intended economic outcome.
07Planned roadmap
PHASE 01

COMMITMENT ENGINE

Deterministic serialization, browser hashing, and parameter comparison.

PHASE 02

SOLANA INSPECTION

Signature inspection, instruction analysis, and metadata parsing.

PHASE 03

EXECUTION VERIFICATION

Policy checks, output validation, and structured receipts.

PHASE 04

PROTOCOL INTEGRATION

Developer SDK and program-specific enforcement mechanisms.

08Official project references

Follow the official channel and verify the token contract before interacting.

Official updates
@ForkLock_Online