This page is written by the strategy itself. Nothing is added by hand, nothing is removed after the fact, and each entry is cryptographically chained to the one before it — so if history were edited, the chain would break and you could tell.
| Received (UTC) | Event | Instrument |
|---|---|---|
| 2026-11-01 03:40:01 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-10-29 21:17:03 | EXIT · TRAILING STOP short, tranche 2 buy | ETHUSDT.P 5 |
| 2026-10-29 20:43:15 | EXIT · TARGET short, tranche 1 buy | ETHUSDT.P 5 |
| 2026-10-25 08:00:06 | SHORT ENTRY sell | ETHUSDT.P 5 |
| 2026-10-21 23:05:36 | EXIT · TRAILING STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-10-21 13:06:36 | EXIT · TARGET long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-10-20 05:25:00 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-10-16 10:43:36 | EXIT · STOP short, tranche 2 buy | ETHUSDT.P 5 |
| 2026-10-15 15:04:54 | EXIT · STOP short, tranche 1 buy | ETHUSDT.P 5 |
| 2026-10-15 10:00:18 | SHORT ENTRY sell | ETHUSDT.P 5 |
| 2026-10-13 00:52:27 | EXIT · STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-10-12 23:02:20 | EXIT · STOP long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-10-10 16:15:07 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-10-08 19:39:39 | EXIT · TRAILING STOP short, tranche 2 buy | ETHUSDT.P 5 |
| 2026-09-21 20:18:46 | EXIT · STOP short, tranche 1 buy | ETHUSDT.P 5 |
| 2026-09-21 11:45:07 | SHORT ENTRY sell | ETHUSDT.P 5 |
| 2026-09-21 01:51:33 | EXIT · TRAILING STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-09-21 00:13:06 | EXIT · TARGET long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-09-18 16:00:11 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-09-18 13:44:08 | EXIT · STOP short, tranche 2 buy | ETHUSDT.P 5 |
| 2026-09-18 05:08:50 | EXIT · STOP short, tranche 1 buy | ETHUSDT.P 5 |
| 2026-09-17 05:00:05 | SHORT ENTRY sell | ETHUSDT.P 5 |
| 2026-09-14 20:16:20 | EXIT · STOP short, tranche 2 buy | ETHUSDT.P 5 |
| 2026-09-14 08:25:07 | EXIT · STOP short, tranche 1 buy | ETHUSDT.P 5 |
| 2026-09-13 10:40:01 | SHORT ENTRY sell | ETHUSDT.P 5 |
| 2026-09-11 14:08:50 | EXIT · TRAILING STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-09-10 12:46:56 | EXIT · STOP long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-09-05 18:50:02 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-09-02 09:33:13 | EXIT · STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-09-01 16:36:58 | EXIT · STOP long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-08-31 17:05:03 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-08-27 10:25:18 | EXIT · TRAILING STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-08-27 08:30:23 | EXIT · TARGET long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-08-24 00:30:06 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-08-19 20:52:04 | EXIT · TRAILING STOP long, tranche 2 sell | ETHUSDT.P 5 |
| 2026-08-19 20:50:15 | EXIT · TARGET long, tranche 1 sell | ETHUSDT.P 5 |
| 2026-08-19 17:20:05 | LONG ENTRY buy | ETHUSDT.P 5 |
| 2026-08-19 14:52:48 | EXIT · STOP short, tranche 2 buy | ETHUSDT.P 5 |
What this page proves, and what it doesn't. It shows the signals the strategy produced and when this server received them. It does not show returns, and a signal is not a recommendation to trade.
How to read an exit. Each position leaves in two tranches, so one entry produces two exit rows. The label says which condition closed that tranche — target, stop, or trailing stop — not whether the position made money. A trailing stop usually closes a winner and a stop usually closes a loser, but the size of either is not shown here and should not be inferred.
Where the record starts. Tracking began while a position was already open, so the oldest row — 19 August 2026, 14:52 UTC — is an exit with no matching entry above it. Nothing was removed: that entry happened before this log existed.
Known gaps: none. A gap is a stretch where the alert feeding this page was not running, so fills the strategy produced never arrived. They cannot be filled in afterwards — writing a row later would either break the chain or, worse, keep it green while lying — so any gap is declared here with its dates and cause. Long quiet stretches without a gap are normal: one position can stay open for weeks.
The chain check recomputes every hash in the browser from the raw log. It proves the record is internally consistent — that entries were not edited or reordered after being written. It is not an external timestamp authority.
Past performance does not guarantee future results. Selepro Veltus is a research and education tool. Nothing here is investment advice.
← Back to Selepro · Documentation · BTC live log · Market state