1 · Pending
The client published the signal claim. The server has not replied yet (network race or queue). Initial pipeline state.
Desktop trading terminal · Backtest Lab · AutoMT profiles
Test, simulate and audit strategy profiles inside one desktop trading terminal.
Cipher Edge is the installed workspace for Backtest Lab, profiles.json packs, AutoMT planning, AI-gated alerts, Paper Mode execution and local review. Public proofs sit behind the official signal stream as a trust layer; the terminal is the product you use every day.
Windows 10/11 · 863 KB · offline installer (.msi)
Backtest Lab · strategy sweeps
profiles.json · import/export packs
AutoMT · multi-symbol planning
Local history · review and replay
Installed terminal
The value is in the terminal you run every day.
Cipher Edge is not just a public signal page. The customer installs a working desktop application for building strategy packs, importing approved profiles, running AutoMT scenarios and reviewing local decisions.
LAB
Build or import profiles
Use the Backtest Lab to generate approved strategy packs, or request a profiles.json file by email to import into your application.
Profiles become the shared contract between lab, GUIDE and runtime
MT
Run AutoMT plans
Turn approved profiles into a multi-symbol plan. The terminal handles symbols, timeframes, gates, cooldowns and Paper Mode execution from the same workspace.
Pairs list · strategy packs · risk caps · Paper Mode execution
LOG
Review local history
The user sees alerts, positions, decisions and outcomes inside the installed app. Public proofs validate Cipher Edge's official stream; local history explains what happened on that terminal.
Public proofs for provider reputation · local logs for user workflow
Trust layer
Public proofs exist to serve provider reputation.
The installed terminal is the product; the public verifier exists so customers can inspect the official Cipher Edge signal stream instead of relying on screenshots, edited posts or unverifiable win-rate claims.
01 Market gap
Backfilled "wins"
A signal published at 14:00 can be edited or "discovered" at 14:30, after price has moved. Without a cryptographic anchor proving when it was emitted, there is no serious way to validate the history.
02 Market gap
Cherry-picked screenshots
Showing 3 out of 10 trades is statistically irrelevant. Without a complete, ordered, time-anchored history, there is no track record — only a hand-picked best-of.
03 Market gap
"Trust me, bro"
Backtests live on the provider's server. Strategy parameters can change between yesterday and today and be "rediscovered" afterwards. You are asked to trust a black box.
Important boundary: public proofs validate the official Cipher Edge stream — not every local action a customer executes inside the desktop app. The customer extracts value through the terminal workflow; the verifier adds transparency about the provider behind it. The verifier runs in your browser: /proofs/ shows the math step by step.
Provider audit states
When we publish official signals, their audit state is visible.
These states belong to the official Cipher Edge signal stream and exist to assess provider integrity; they do not suggest that the customer's local machine is anchoring private actions on-chain. Five states keep the public stream clear and verifiable:
PROOFPENDING
PROOFAUDITED
PROOFREJECTED
PROOFROOTED
PROOFNO AUDIT
2 · Audited
The server re-ran the strategy on the same candle. Side, price and profile hash match. The canonical leaf is written to the local database. Two independent paths agree the signal is real — but it is not immutable yet.
2 · Rejected (alt)
The server re-evaluation diverged: different side · profile hash mismatch · missing or inconsistent candle. Click to see the exact rejection code. This is the most important state: it is the public admission that something did not match.
3 · Rooted
The daily Merkle root was built and this signal is one of the leaves. Anchored on Base L2 + Bitcoin OTS. Cryptographic finality — verifiable forever.
* · No audit
The signal does not contain required metadata (strategy, timeframe, profile hash, candle close). It is excluded from the audit pipeline and will not be published.
Why show these states:
provider transparency should be specific, not vague.
PENDING says: "we are processing".
AUDITED says: "two independent paths agree — but it is not final yet".
REJECTED exposes divergences and explains why.
ROOTED is finality for the official stream.
NO AUDIT clarifies that certain signals do not enter the pipeline.
Inside the app, the practical value remains the workflow: profiles, AutoMT, Paper Mode execution and local review. The verifier adds transparency about the provider — not about every private user action. The verifier runs in your browser: /proofs/ shows the math step by step.
PENDING says: "we are processing".
AUDITED says: "two independent paths agree — but it is not final yet".
REJECTED exposes divergences and explains why.
ROOTED is finality for the official stream.
NO AUDIT clarifies that certain signals do not enter the pipeline.
Inside the app, the practical value remains the workflow: profiles, AutoMT, Paper Mode execution and local review. The verifier adds transparency about the provider — not about every private user action. The verifier runs in your browser: /proofs/ shows the math step by step.
Provider public record
A public reputation layer, separate from the installed app.
Official Cipher Edge signals can be hashed, grouped into a Merkle root, anchored externally by Cipher Edge and verified directly in the customer's browser. Verification is client-side; public anchoring is operated by Cipher Edge. The page at /proofs/ provides transparency, while the desktop app remains the customer's product.
PUBLIC PROOF LAYER
Official signals leave a verifiable trail.
1 · Signal emitted
Strategy, side, price, timeframe and profile hash are frozen.
2 · Canonical hash
One deterministic payload becomes one unique
SHA-256.
3 · Merkle root
The day's official signals are committed into one public root.
4 · Chain witness
Cipher Edge anchors the root via Base L2 and Bitcoin OTS.
5 · Browser verify
The customer verifies the proof locally, without paying.
Merkle construction
sig_01
sig_02
sig_03
sig_04
root_8f3a...c21b
Public audit trail
2026-05-20
92 signals committed
Rooted
2026-05-21
Base L2 + Bitcoin witness
Verified
Any signal
Client-side Merkle path check
Replayable
Roots anchored
175+
one per UTC day since launch
Signals committed
2313+
cumulative, all directional alerts
Bitcoin confirmed
10
block-included OTS proofs
Pending upgrade
45
awaiting next Bitcoin block
Verify any published signal right now
The page lists each official signal ID. Click any row and the browser walks the Merkle path against the anchored root.
Open the verifier →
Honest disclosure: Verification is client-side, but public anchoring is operated by Cipher Edge for the official signal trail. OpenTimestamps batches submissions into Bitcoin transactions every few hours. Most recent roots show "Pending upgrade" until the next batch is mined — that's the OTS protocol, not a bug. Older roots (3+ days) show their Bitcoin block height. User-owned/private anchoring is an advanced option, not required to verify the public record.
What you get
A full trading workbench. Not just signals.
Cipher Edge ships as a desktop terminal: Backtest Lab, profile packs, Paper Mode execution, multi-exchange data, AI-gated alerts, AutoMT planning and position management. The public proof layer supports provider transparency, while the application is where the customer works.
🧪
Backtest Lab
Run reproducible backtests across 18+ strategies and 5 timeframes. Export approved configurations as a profiles.json pack that the live runtime consumes.
SUPERTREND · OB_FVG_BOS · TREND_FOLLOWING · MA_CROSSOVER · 14 others
🤖
AI Gate (learned model)
Bayesian gate per symbol with win-rate priors and EWMA. It handles cold-start, adapts to your history and supports tunable thresholds for AutoMT, scanner and symbol-specific contexts.
Adaptive flow: conservative · balanced · offensive — switches by market regime
🛡
Trade Gates
Three independent filters that complement the AI Gate. Configurable in Settings → Trade Gates.
Anti-chase · Time Stop · HTF confluence (optional)
⚙
Smart Position Management
Break-even, trailing stop, TP extension and time stop are applied by default and configurable per strategy. Defaults were calibrated with months of Paper Mode audit.
BE 0.6% · Trail 1.0% · TPx 3 · Time stop 240min/0.30%
🌐
Multi-exchange routing
One terminal, four venues. Symbol, candle, ticker and funding-rate normalization is handled by adapters dedicated to each exchange. Positions keep their lifecycle tied to the origin exchange, ensuring consistent replay even after you change the active venue.
Binance · Bybit · OKX · Bitget — USDT perpetuals
🔐
Local review + public trust
The terminal centers you on local analysis, alerts and positions. Public proofs validate the official Cipher Edge stream, allowing provider reputation to be assessed without additional costs.
Local workflow · public official stream · advanced anchoring (future)
BINANCE
BYBIT
OKX
BITGET
USDT-M Futures · WebSocket + REST
The terminal
The full cockpit. Built for traders who do their own thinking.
One window brings together market watch, chart, execution, position manager and bottom tabs for history, signals, radar, management, replay and settings. The proof badge is auxiliary context; the center is the control surface.
In action
When signals start flowing.
The terminal is the canvas. The real impact is in proof-backed alerts and reproducible Lab metrics.
This is the daily rhythm.
Proofs · metrics · flow
Personal assistant
CIPHER watches the terminal with you.
Native assistant for settings, diagnostics and workflow. It is not a chatbot pasted on top; it is part of the terminal, integrated into configuration and audit.
CIPHER / PERSONALIZED ASSISTANT
PERSONALIZED
A product-aware co-pilot focused only on the parts traders actually configure.
CIPHER explains settings, summarizes diagnostics, clarifies AI Gate behavior and helps keep the setup consistent before you save and reload. It is not a generic chatbot bolted onto the side: it is integrated into the terminal's real controls.
Settings
Explains what each value changes.
Alerts, AI Gate, AutoMT, risk caps, cooldowns and backtest timeframes stay understandable while you tune them. The assistant translates technical parameters into operational impact.
Diagnostics
Turns counters into decisions.
PASS/BLOCKED totals, block reasons and last-signal context are summarized in plain language. CIPHER helps you quickly understand why something passed or was blocked.
Workflow
Reminds you what applies when.
Export/import, save and reload steps are called out so configuration changes do not get lost. The assistant keeps the flow disciplined: adjust → save → reload → validate.
Audit
Keeps proof visible.
Signals, gates and proof states are treated as a continuous workflow: configure → emit → verify → review. Proof is not an extra; it is part of the operational cycle.
Provider proof loop
How the public official stream can be checked.
This is the provider-side audit trail, separate from the customer's local terminal workflow. The verifier on /proofs/ reproduces the public proof steps in the browser.
STEP 01
Signal emission
Strategy fires on a closed candle. We build a canonical leaf: lexicographic JSON of side, price, profile hash, candle close timestamp. Hash with SHA-256.
STEP 02
Daily Merkle root
At UTC midnight we combine the official signals of the day into a binary Merkle tree (RFC-6962 domain separation). The 32-byte root represents the entire published day in one hash.
STEP 03
Anchor on Base L2
Cipher Edge submits the official Merkle root as transaction calldata on Base L2. Block timestamp = proof that the root existed before that block. Public anchoring is operated by Cipher Edge; customers do not need to pay gas to verify it.
STEP 04
Bitcoin OTS
The same root is also submitted to OpenTimestamps public calendars. Hours later, when the next batch is mined, the root is permanently witnessed by Bitcoin's proof-of-work.
The crucial property: Once an official root is on-chain, the only way to "edit" any published signal in that day would be to find a SHA-256 pre-image collision — which we don't know how to do, and neither does anyone else. The public signal history becomes append-only forever.
Pricing
Pay for the software. Keep your custody.
Cipher Edge is not a broker, doesn't hold funds, and never connects to your exchange account without your explicit setup. The license unlocks the desktop package and profile delivery. Cancel any time — your local data stays yours.
Free trial
3 days
€0
Explore the terminal without a profiles.json. Check the interface, settings, public proofs and local workflow first.
- Terminal access without profiles.json
- Backtest Lab available
- Public verifier access
- Email activation
Weekly
7 days
€19.90€9.90
Short paid access with the Cipher Edge reference beta pack. Useful before committing to a longer plan.
- Full terminal + Backtest Lab
- All 4 exchanges
- Reference profiles.json beta pack
- Email support
Monthly
30 days
€59.90€29
The default for active beta users. Includes the terminal and the Cipher Edge reference profile pack.
- All weekly features
- Reference profiles.json beta pack
- Priority installation support
- Crypto payment discount available
Annual
365 days
€399€199
Best long-term value for a stable setup, beta pricing and occasional reference pack updates.
- All monthly features
- Annual license key
- Reserved beta-tester pricing
- Occasional reference pack updates
Beta licenses are currently handled by email. Crypto payment is available by request with a 10% discount. To avoid network mistakes, the wallet address is provided by email for each payment. Mail cipheredge.net@outlook.com for payment instructions and a license key. The included
profiles.json is a Cipher Edge reference beta pack for selected liquid pairs, not a custom pack per customer.
FAQ
Direct answers. No marketing softening.
Can you fake the proofs?
To fake a published official signal, we'd have to find a SHA-256 pre-image collision for a 64-character hash — which would also break Bitcoin and roughly every other thing built on cryptographic hashing in the last 25 years. To "fake" the chain anchor, we'd have to rewrite Base L2 history; same problem at network level. The only way to lie within the design is to not submit a signal in the first place — i.e. suppress an entry. Our defense against suppression is the publicly-listed signal counter on
/api/proof/roots: if it ever decreases, we've broken our own audit trail.
Why both Base L2 AND Bitcoin?
Two independent witnesses. Base is fast and cheap enough for Cipher Edge to operate the public anchoring layer for official roots. Bitcoin via OpenTimestamps is slow (10-min blocks, batched) but is the most defensible timestamping authority on Earth. If Base ever experienced a reorganization or contentious fork, Bitcoin still witnesses everything. Belt and suspenders.
Do you execute trades for me?
No. Cipher Edge runs a paper-trade simulator by default. To execute live trades you connect your own exchange API key (read-only initially, then enable trade scope after confirming behavior). We never hold funds, never have access to your withdrawal credentials, and the license server has no exchange integration whatsoever.
How is this different from TradingView / 3Commas / Cornix?
TradingView is a charting platform — no signal audit, no proof layer. 3Commas / Cornix are bot execution services — they hold API keys and route orders, but their signal sources are unverifiable third parties. Cipher Edge is closer to "TradingView + a cryptographic notary". You see the math, the backtest, the live signals, and the proof — all in one place — and you keep your own execution. We're not competing with execution bots; we're competing with the "trust me, here's a Discord screenshot" model that owns the signal-provider market today.
What if your servers go down?
The proof bundle for any published official signal can be downloaded as a self-contained
.zip (envelope.json + audit.json + receipt.ots). The CLI verifier (bin/verify-proof.ts) is <200 lines, uses only node:crypto + standard OpenTimestamps tools, and runs offline. As long as Base L2 and Bitcoin exist, you can verify our historical public signal trail forever — even if cipheredge.pt vanishes tomorrow.
Is the strategy code open source?
The proof layer is fully auditable by design — every byte of the canonical leaf format and Merkle algorithm is documented in
docs/PROOF_LAYER.md. The strategy engine itself ships as compiled JS in the desktop package; design partners get source access under a separate agreement. Long term, the canonical leaf schema and verifier will be permanently open so anyone can build a third-party auditor.
Why should I trust a young product?
You don't have to trust us — that's the whole point of the proof layer. You can verify any published official signal independently with a few seconds of browser CPU. What you do have to trust: that we keep emitting signals (not falsifying them). The on-chain history will show within weeks whether our hit-rate matches our claims. If it doesn't, you can prove that too.