​
The problem

A track record published after the outcome is known is not evidence of anything. Any vendor can select windows, drop losers, and present what remains. The only structural fix is to commit to a claim before the outcome exists to influence it.

​
How it works

1

Canonicalise

The call payload is serialised into a canonical byte format — field order, encoding, and number formatting all fixed, so the same logical claim always produces the same bytes.
2

Hash and commit

The canonical payload is hashed and the hash is committed on-chain before the outcome exists.
3

Bind once

When the outcome is known, an oracle verifier binds the realized result to that hash — exactly once. No edits, no deletes, no do-overs.
4

Recompute independently

Anyone can recompute the hash from the published payload and check it against the chain. You do not have to trust the vendor’s arithmetic; you can redo it.

​
Current status: not deployed

The AlphaLedger contract is not deployed. No signal has ever been anchored.Today every signal is hashed with the canonical format and queued. anchor_status reads queued and anchor_tx is null.A signal is anchored when a transaction exists, not when a status field says so — the status is written by the process that queued it, the tx hash by the process that got a receipt. Check anchor_tx.
This is stated plainly because the alternative — a “verifiable on-chain track record” headline over a system with nothing on chain — is precisely the kind of claim this feature exists to make impossible.

​
Why the queue is still worth something

The hash format is a byte-for-byte port of the on-chain canonical encoding, with cross-language parity vectors in the test suite and a Node cross-check in the suite run. Signals queued today will verify against the contract once it is deployed, without rehashing.
Two implementation traps found porting the canonical payload to Python, worth knowing if you reimplement it:
  • json.dumps(..., ensure_ascii=True) silently breaks the hash on any non-ASCII content. The canonical form requires UTF-8 passthrough.
  • Python’s standard library has no keccak256. SHA-3 is not the same function; substituting it produces plausible-looking hashes that never match.

​
What verification proves

Re-verification establishes that the published bundle hashes to the recorded value, and that the reasoning cited only what it was shown. It cannot establish that the evidence was true when collected. See Verify a signal.

​
Access

Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.