Security & access
The safest trading system is one that cannot move money.
BaseArbBot.ai is deliberately built without a custody or execution surface. What remains to protect is access to the terminal and the integrity of the data it produces — and both are governed tightly.
Controls
Access and data controls in force.
Mandatory two-factor authentication
Time-based one-time codes are required for terminal access; enrolment is enforced before the platform can be used.
Recovery without weakening
Single-use recovery codes are stored only as hashes and every use is written to the activity ledger.
Device trust governance
Trusted devices expire, are listed with their expiry, and can be revoked individually at any time.
Rate limiting and lockout
Repeated failed verification attempts trigger a challenge and then a timed lockout, with the reason surfaced to the operator.
Security activity ledger
Sign-ins and verification events are recorded with address and client details, searchable, filterable and exportable.
Server-held credentials
Venue keys and network credentials live server-side only and are never exposed to the browser.
Closed registration
There is no public sign-up. Access is provisioned to authorised operators only.
No custody surface
The platform cannot hold, move, deposit or withdraw funds, which removes the highest-value attack target entirely.
Architecture
Separation is the control, not a preference.
Market data, analysis and any future execution capability are isolated from one another so that adding execution later cannot silently widen today's risk surface.
Data plane
Read-only adapters that fetch prices. No credentials with trading permission are used.
Analysis plane
Deterministic cost and simulation logic with invariant checks and recorded provenance.
Execution plane
Not connected. Any future capability would be a separate, independently governed service.