Seqlense Monitoring watches on-chain wallets and order-book flow in the same place, and ties both to the person behind them. An alert names a client, not a hash.
Hosted in Europe · MAR / MiFID II order-record retention · Full audit trail
Surveillance tools flag an address or a customer id. Neither is a person. Seqlense resolves both onto one identity, so a wallet flagged on Monday and a trading client flagged on Thursday stop looking like two unrelated events.
Addresses across the chains the scanner covers, with their enrichment, their scan history and their recurring schedules.
The customer ids in your own order feed, kept verbatim. One person trading under a separate id per venue resolves to a single subject.
Their wallets, their client ids, every alert raised on any of them, and the notes your team left last time.
Splitting flow across two venues hides from any view keyed on the client id alone. It does not hide from the identity.
They read different data and answer to different rules. Their findings land in the same alert list, against the same subjects.
Scan a wallet on demand or on a schedule. Counterparty risk, behavioural patterns and a verdict you can archive.
Run across a whole organisation's order flow. Findings come back per client, per book and per pattern, not as one verdict.
A detector that lacks the data to judge reports it as not evaluable, and names the missing field.
No schema to conform to before you can try anything. Map your columns once, keep the profile, and reuse it for every file that venue sends.
The wizard reads your headers and proposes the match. Timezone and decimal separator are declared once for the file, not guessed per row.
A sample is validated and reported before anything is written. This is what stops eighty thousand rows landing with the wrong timezone.
A bad file is removed on its own, and the record that it happened is kept. No purging the workspace to fix one mistake.
Every event stores the line it came from, verbatim. It is the only thing that settles a dispute over an alert months later.
Event ids are derived from content, so replaying a file that timed out converges instead of double-counting.
Raising an alert is the easy half. What decides whether a tool is used is what happens when someone opens it three weeks later.
By subject type, by tag, by date range, by source. A link you send a colleague opens on exactly what you were looking at.
"Client verified, recurring false positive" belongs on the person, not on whichever alert happened to be open that day.
Deleted wallets and identities go to a trash. Duplicate identities merge. A bad import is undone without touching the rest.
An alert you cannot explain to a regulator is not worth raising.
MAR and MiFID II expect it, and the order table is that record. It carries no expiry, deliberately.
Who matched a client, who resolved an alert, who launched a scan, who removed an import, and when.
Alerts carry the thresholds applied and the coverage of each pattern, so a verdict can be re-read, not re-argued.
One tenancy key scopes every read and every write. Nothing crosses between organisations.
Not to start. Order data goes in as a CSV through the mapping wizard, and a wallet is scanned by pasting its address. An API is there when you want to automate it.
CSV exports, whatever the column names. You map them once per venue and the profile is reused. Both a final-state-per-order export and a full event log are accepted.
Yes, on a wallet: the free risk check runs without signing up. Order-book monitoring needs a workspace.
In Europe. Every query is scoped to your organisation, including the ones that resolve an identity.
Five years, with no automatic expiry, because that table is the order record MAR and MiFID II expect you to hold. Shortening it is your decision, not a storage default.
No. Matching a client id to an identity is always an analyst's judgement or an import from your own KYC base. Nothing is inferred by heuristic.
Start with a wallet in the free check, or bring one venue export and watch the first alerts land against named clients.
Schedule a demo, access technical documentation, or receive a customized compliance assessment.