MONEYMAKERBOT • DOCS

System Documentation

Technical overview of the private AI trading infrastructure, capital flow, custody structure, reward settlement, and operational access model.

This documentation explains the user-facing structure and operational flow of the system without exposing proprietary execution logic, venue relationships, or confidential routing details.

01

Overview

This system is a private, invitation-only trading infrastructure designed for controlled USDC strategy execution across multiple venue types.

Each approved participant receives a dedicated personal vault. Capital is routed through an operator-managed treasury layer and then distributed to external execution environments through a controlled trading wallet.

The system combines onchain custody and settlement with offchain execution, monitoring, and strategy coordination.

02

Why Personal Vaults

Each approved wallet is assigned a personal vault on first deposit.

This structure provides a clear separation between participant-level deposited capital, operator-managed allocation flow, and treasury-level execution routing.

A personal vault is used as the participant’s default custody layer before capital is allocated into the broader execution framework.

This model improves operational clarity and creates a cleaner capital lifecycle for deposits, returns, and withdrawals.

03

Capital Flow

The system uses a structured capital path: Personal Vault → Trading Treasury → Trading Wallet → External Venues.

At a high level, the participant deposits USDC into a personal vault, capital is routed from the vault into the Trading Treasury, treasury capital is forwarded to a dedicated Trading Wallet, the Trading Wallet distributes capital across external execution venues, and capital and strategy results are consolidated back through the treasury layer.

Returned funds become available for participant withdrawal once settlement conditions are met.

This structure is designed to support operator-managed routing while preserving a clean internal accounting model.

Architecture Flow

Personal Vault → Trading Treasury → Trading Wallet → External Venues

External Venues → Trading Treasury → Personal Vault (withdraw settlement path)

04

Strategy Framework

The strategy framework focuses on short-horizon, execution-sensitive market opportunities across multiple venue types.

Without exposing proprietary parameters, the system is designed to identify and act on conditions such as cross-venue price dislocations, short-term spread inefficiencies, liquidity and order-book response patterns, funding-rate opportunities, basis and arbitrage conditions, and execution windows created by temporary market imbalance.

The framework is optimized for fast signal evaluation, controlled capital deployment, and venue-aware execution.

05

Venue Coverage

The execution framework is designed to operate across both decentralized and centralized venues.

This broader venue coverage allows the system to observe and respond to market conditions beyond a single execution layer. In practice, this expands the opportunity set available to the strategy engine and supports cross-venue positioning and capital routing.

For confidentiality and security reasons, the exact venue list, routing logic, and execution relationships are not disclosed publicly.

The venue layer includes centralized access across multiple regions, including Asia-facing liquidity environments.

06

AI Strategy Layer

The system uses an AI-assisted strategy layer to aggregate venue data, rank opportunity sets, and support capital routing decisions.

At a high level, the AI layer is designed to process incoming market data across multiple execution environments, identify actionable inefficiencies, adapt routing and allocation priorities, optimize execution timing and capital distribution, and support automated strategy coordination under operator-defined controls.

The exact model structure, training process, routing logic, and signal thresholds remain confidential.

07

Rewards and Settlement

Claimable reward values are computed offchain and authorized through the system backend.

Because the execution layer spans both onchain and offchain environments, a portion of the accounting logic is handled outside the blockchain execution layer.

The backend aggregates the required execution and accounting inputs, computes the current claimable amount for each participant, and produces an authorization payload for settlement.

Reward claims are then settled onchain only for amounts that have been authorized by the backend signing layer.

The frontend does not invent or locally define claimable values.

Settlement Integrity

Backend Computation → Signed Authorization → Onchain Verification + Settlement

The smart contract verifies signatures; it does not pull backend data directly.

08

Withdrawals

The withdrawal flow depends on current treasury liquidity state.

  • Withdraw Available: If sufficient liquidity is currently available for settlement, the participant will see Withdraw Available and can complete the withdrawal immediately.
  • Request Withdraw: If sufficient liquidity is not currently available, the participant will see Request Withdraw. In that case, the participant submits a withdrawal request, capital is returned through the treasury settlement flow, the requested amount is made available for release, and the participant can complete the withdrawal after the return window is completed.

Target Timing

The target return window is up to 24 hours.

09

Access Model

This system operates as a private, invitation-only environment.

Access is restricted to approved wallets only. All user actions are controlled through whitelist-based access permissions and backend authorization logic where applicable.

This is not a public retail interface and is not intended for unrestricted onboarding.

10

Confidentiality and Operational Boundaries

To preserve execution quality, routing integrity, and internal strategy performance, a set of execution details remains intentionally undisclosed.

  • exact venue relationships
  • exact strategy parameters
  • exact execution rules
  • exact routing logic
  • exact signal thresholds
  • exact capital distribution rules

Disclosure Boundary

The public documentation is intended to explain system structure and user-facing behavior without exposing proprietary operational logic.