Trade records
Original history, Ultra, new Santech V2 and older Perp paper fills. Historical signals and testnet records included.
OUR ACTIVITY
The whole picture.
Clearly recorded.
One combined view of the reviewed Santech records, with the original history included and every measure defined.
SANTECH / ONE VIEW
Our activity.
All connected.
Connecting to recordsWaiting for source update
In the last 7 days
A rolling 168-hour window across the reviewed sources.
Market assessments / 7 days
Ultra scan records. Repeated assessments can occur.
Users who’ve interacted
Unique Telegram accounts from historical and connected Santech records. Includes nonpaying users.
Combined records include generated signals and paper/legacy entries. They are not verified live executions or dollar turnover. Original Santech history is a dated snapshot; connected sources refresh each minute.
NEW SANTECH / ONGOING RECORDING
The next generation.
Every entry accounted for.
New Santech V2 trades are read directly from its exchange archive. As new fills are archived, the counts update automatically here and in the combined total.
Confirmed strategy entries
- in the last 7 days
Recorded testnet entries
- in the last 7 days
Waiting for the new Santech archive.
One entry per account, network and trade intent. Partial fills and updated receipts count once. - filled connection demonstrations excluded. Local paper trades are outside this exchange archive. The recorder must be running for new events to reach it.
Connecting to activity records.
Exact date windows appear after refresh.
THE WORK BEFORE A TRADE / LAST 7 DAYS
Every scan.
Including the ones we pass.
A scan can finish below the entry threshold. It still counts as research activity; it never becomes an executed trade just because it was scanned.
Below the current entry band
Kept in the assessment total. Not promoted into the profit calculator.
High-risk opt-in band
Requires the high-risk setting and the remaining account and execution checks.
Standard score band
A qualifying score is a starting condition, not proof of an order or fill.
— scans have a recorded trigger flag. Scores with missing values: —.
Last recorded scan will appear after refresh.
How scans become candidate trades +
The inspected Ultra scanner checks an absolute score of 85+ for the standard path, or 75+ with high-risk enabled. Account permissions, pair settings, membership, trade allocation, venue limits and a 48-hour per-user/per-asset cooldown can still prevent placement.
These score bands describe the current inspected rules. Historical rules may differ. Trigger flags, generated signals, stored trade records and exchange-confirmed fills are separate measures. No return is assigned to a scan without a complete trade outcome.
BEHIND THE TOTAL
Every source.
Accounted for.
The headline adds retained records. Order attempts and fills are not counted twice.
SOURCERETAINED RECORDSWHAT IS COUNTED
Original Santech—
Supplied current ledger plus older history, deduplicated by signal ID. Known tests and malformed rows excluded.
Ultra—
Distinct stored trade IDs. Known fixtures excluded. Paper and legacy entries remain mixed.
Older Perp paper—
Paper orders with fill evidence. Unfilled and cancelled attempts excluded.
New Santech V2 · mainnet-
Strategy entries with confirmed exchange fill evidence. Real funds; connection demonstrations excluded.
New Santech V2 · testnet-
Strategy entries on testnet. Virtual funds; connection demonstrations excluded.
New UltraAwaiting feed
Not included until its versioned trade ledger is connected and checked.
Combined trade records—
Historical signals and records, not verified live executions.
Original snapshot date will appear after refresh.
Counting and freshness rules +
History: original generated signals, Ultra trade IDs, older Perp paper orders with fills, and new Santech V2 confirmed strategy entries. Each source is deduplicated on its native record ID. Original IDs were checked against Ultra at import; no overlap was found. Backups of the same database are not added again.
Original Santech: the supplied ledger has 13,059 data rows (13,060 including its header). It contributes 12,996 valid signal IDs; 662 additional unique signals come from older local history. The combined 13,658 IDs are counted once. Known test markers and malformed rows are excluded. Signal timestamps run through 19 October 2026. This is a dated import, not a live bridge to the original PC. Its exact signal timestamps contribute to the rolling seven-day total.
Seven days: seven consecutive 24-hour windows ending at the server query. Ultra’s legacy timestamps are interpreted as UTC. Assessments are scan records and can repeat.
Perp: multiple fill rows for one order contribute one paper trade record. Unfilled attempts are separate. A paper fill is not a live execution.
New Santech V2: one strategy entry with a positive, dated exchange entry fill per network, account and intent. Partial fills, repeated receipts and archived updates do not add trades. Mainnet and testnet are labelled separately. Connection demonstrations, missing strategy purpose, ambiguous fill ownership and unfilled plans are excluded. Current retained history is included; there is no artificial reset to zero. New archive events appear on the next successful refresh.
New Ultra: a reserved, separate source. Its count and recording start remain unavailable until a real versioned ledger is connected and validated. Demo and research runs do not start the counter.
Users who’ve interacted: the supplied Gatekeeper export contains 184 unique Telegram accounts. Both uploads are identical and count once. All 36 historical trader accounts are already in that export. Connected Gatekeeper V2 and Ultra user records are unioned by Telegram ID; a returning user does not add another person. This includes nonpaying users. New accounts appear when a connected source records them; unconnected bots and unrecorded interactions are outside coverage.
Freshness: connected aggregates refresh each minute while visible. Missing live sources make the combined total unavailable. A successful query does not prove trading-engine health.
PERP / ORDER ATTEMPTS—
Attempts are excluded unless a fill exists.
PERP / FILL ROWS—
Reconciled by order ID before inclusion.
ULTRA / ASSESSMENT HISTORY—
Kept separate from trade records.
YOUR NEXT CHAPTER
Make the
connection.
Understand the products.
Choose your starting point.