The proof layer
A record channels can't
quietly rewrite.
The planned proof layer will hash-stamp each message when the engine reads it, then attach the action taken. The aim is a record that is public, tamper-evident and difficult to rewrite.
How the planned chain works
Each record contains a fingerprint of the record before it. Rewrite history anywhere and every fingerprint after it breaks. A later edit would be visible because every following fingerprint would stop matching.
#0847 · entry_signalprev 9f2a…c41e
↓
#0848 · breakeven_setprev 3b7d…0847
↓
#0849 · ignoredprev e551…0848
✓ Simulation · 849 demo records · no breaks
Channel scorecards
The record, not the marketing
What the chain says about the channels it watches. Demo data shaped like real output — the point is what gets measured.
GS
Aurum Prime Signals
Signal quality: poor
What the chain sees: results posted to the channel claim 89% wins; the ledger of what was actually posted matches 31%. Luxury-content posts outnumber trade records 6:1.
BM
Northern Gold Desk
Under review
What the chain sees: pip targets quoted in "$1.00 per pip" terms don't reconcile with the channel's own promotional risk-reward math. Not proven either way — flagged until it reconciles.
GT
Helios Gold Std
Chain-verified
What the chain sees: a fictional example of what a good channel earns: every claim it made, the ledger confirms. This badge has to be earned — and it can be lost the week the numbers slip.
* "Win rate" here is the share of acted-on signals whose TP1 was reached before SL, measured on the ledger record. It is not a profit figure and not advice.
The copy engine
Copy the signal, not the gamble
The engine runs on your MetaTrader account, with your risk rules. It never holds funds, never executes for anyone but you, and refuses anything ambiguous.
Your copy setup — preview
Every rule below is enforced before an order is ever placed.
Risk per trade1.0% of account, always
Stop lossRequired — no SL, no trade
Daily loss circuit breaker-3% → engine stops for the day
Spread check before orderOn
Ambiguous messageLogged for review, never traded
Every action this setup takes lands on your ledger. The same records that build the channel scorecards above.
One system
Copy with rules.
Prove what happened.
The copy engine and the ledger are not separate features. The record exists because every automated decision should be inspectable.