Nexus is invitation-only. Prospective clients request access at mm.r3s1x.com/register. Invited 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 checked by automated tests on every deployment. Separately from scope, users may be given view-only roles.
Execution and trading modules exist. They are opt-in and hard-off by default: they are not enabled for a project that has not opted in, and nothing trades until the operator arms them.
Nexus lists 44 venues, centralised and decentralised. Connections are arranged with the operator. 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. Nexus holds no private keys and takes no custody of funds.
Detect. Several independent detectors watch different observables: on-chain transfer flow, exchange sell pressure, relay and sybil cluster topology, and order-book depletion.
Verify. Detections are combined into a confluence verdict. An alarm needs at least two independent observables to agree. A single signal is never an alarm and never 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. Provided liquidity is measured against the mandate, and an absorption score shows how much selling the book can take.
Alerts are delivered over three channels: Telegram, email and web push. Every 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 holds no private keys and takes no custody of funds; centralised venues are connected with read-only API keys that carry no withdrawal permission (see Connecting a venue).
Does Nexus trade for me?
Not by default. Execution and trading modules are opt-in and hard-off, and nothing trades until the operator arms them (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, and that isolation is checked by automated tests on every deployment (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 and order and trade history fetched with the read-only keys, public on-chain data, and user account data (email and a hashed password). 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.