Access to Nexus is approval-gated. Prospective clients request access at mm.r3s1x.com/register; the account stays pending until the operator approves it. The operator may also issue invitation links. Users sign in at mm.r3s1x.com/login.
Three terms are used throughout this guide. The operator is the party that runs Nexus under the brand r3s1x.eth · OL. You means a client: a token issuer or foundation whose project Nexus covers. The desk is the signed-in Nexus workspace.
There are two login scopes. Operator staff logins see the whole desk. A client login is scoped to its own project only: it is designed to be sealed from every other client's data, and that isolation is covered by an automated test suite (a scoped probe login that must be refused on every other client's endpoint) which the operator runs against the live desk before each release. Separately from scope, users may be given view-only roles.
Execution and trading modules exist but ship disabled. Nothing trades unless the operator explicitly enables a module on the server and configures it for a project under a written mandate. They are not part of a standard client engagement.
Nexus covers 44 venues on its public coverage list, centralised and decentralised; exchange-key connections are currently supported for 23 centralised venues. Clients can add their own venue keys from the desk, or ask the operator to do it. What a connection involves depends on the kind of venue.
Key permissions and restrictions are set at the exchange and are governed by the exchange's own documentation and controls. Management of keys at the exchange remains your responsibility, and Nexus does not verify a key's permissions. Nexus never asks for, stores or uses a client's private keys or seed phrases, and takes no custody of client funds. On-chain coverage is configured per project by the operator (currently Arbitrum).
Detect. Four independent detectors watch different observables: coordinated slicing on the DEX tape, distributed iceberg selling on exchanges, one-directional venue flow imbalance, and on-chain relay chains through fresh wallets. Book depth then shows whether the line is holding.
Verify. Detections are combined into a confluence verdict. A dump verdict needs at least two independent observables to agree. A single detector produces an event, delivered and labelled as such, never a verdict; a detector that cannot measure is reported as blind, never as an all-clear.
Escalate. A verified verdict reaches you on your phone, by Telegram, email and web push. Each alert carries clickable evidence: the address, the transaction and the funder.
Absorb. An absorption read shows how much selling the pooled order books can take before a 2, 5 or 10 percent drop, and whether the market makers are holding the line during an active event. Provided depth and volume are tracked against market depth and the contracted minimums.
Alerts are delivered in the desk itself and over Telegram, email and web push to the desk's alert channels; client-specific Telegram routing is set up by the operator at onboarding, and webhook delivery can be enabled. Every event alert is interactive and links to the address, the transaction or the venue it concerns. The operator also receives a nightly digest.
Scheduled institutional reporting is built into Nexus: reports are produced and delivered on a schedule. Verified findings are escalated as they are verified, on the channels described above.
Is Nexus custodial?
No. Nexus never asks for or stores a client's private keys and takes no custody of client funds; centralised venues are connected with read-only API keys that carry no withdrawal permission, created and controlled by you at the exchange (see Connecting a venue).
Does Nexus trade for me?
Not by default. The execution modules ship disabled and nothing trades unless the operator explicitly enables them on the server for your project under a written mandate (see The desk at a glance). Nexus does not provide investment advice and gives no guarantee of trading results.
Can another client see my data?
A client login is scoped to its own project and designed to be sealed from every other client's data; that isolation is covered by an automated test suite the operator runs against the live desk before each release (see Getting access). Use of Nexus is subject to the Terms.
What happens if a venue key is revoked?
A key revoked at the exchange no longer works, so Nexus can no longer fetch data through it. Reconnecting the venue is arranged with the operator through /contact.
What data does Nexus store?
Account balances, open orders, fills and deposit/withdrawal history fetched with the read-only keys (the keys themselves are stored encrypted), daily balance snapshots, public on-chain data, and user account data: username, email, a salted password hash, and an optional two-factor secret or passkey. Sessions use cookies. Nexus does not sell data. The Privacy Policy has the full statement.
Can access be suspended?
Yes. The operator may suspend access, and the service is provided as-is; see the Terms.
How do I contact the operator?
Through the contact page at /contact. Access requests go through mm.r3s1x.com/register.