Every signal is committed before the result is known. When it
closes, the trade details and salt are revealed so the record can be
checked against the original hash.
How verification works
01
Open commitA hash is published before the trade result exists.
02
Close revealThe signal payload, outcome and salt are revealed at
close.
03
Public proofIf the recomputed hash matches, the signal was not edited after
the outcome.
Ledger Events
0
loaded from public view
Verified Reveals
0
hash confirmed
Approved Reveals
0
closed approved signals
Rejected Reveals
0
closed counterfactual signals
Ledger Events sealed commits and close reveals
This page reads from Supabase public views only. Raw operational tables
should remain protected by RLS. Trading involves significant risk of
loss. Ledger verification proves event integrity, not future
performance.