Help / Vault Architecture & Safety

Vault Architecture, Routing & Safety

Mojomaxi is non-custodial Solana automation software. The TradingView Webhooks Bot and the Rebalance Bot both run on the same on-chain vault program, with one isolated vault per strategy set and guarded backend coordination around execution.

What Mojomaxi is

  • A Next.js and Solana app for non-custodial automation.
  • Supports TradingView webhook strategies and rebalance basket strategies.
  • Uses one vault model across both bot types for cleaner isolation and more consistent safety assumptions.
  • Uses Jupiter-routed swaps, backend coordination, and on-chain enforcement together.

Shared vault model

  • Each strategy set gets its own vault account and vault authority model.
  • Funds live in strategy-specific token accounts tied to that vault.
  • The same per-set vault isolation applies to both Webhooks and Rebalance bots.
  • This reduces blast radius and makes strategy-level activity easier to audit.

Programs, fees & anchors

  • Vault Program ID: 2Nz2Ls8NfaLDR92yDg8NVwoU6jzumdTdJFWq2rLr3Nyp
  • Current protocol fee: 0.25% on executed swaps.
  • On-chain fee cap supported by the program: 1.00%.
  • Treasury wallet: 5mEqxr6McBRL5DGE9dJ2Td3viwhAmRpe4V7pqGTPMtvr

What non-custodial means here

Mojomaxi does not operate as a pooled user wallet or hosted exchange balance. Funds stay in vault-controlled token accounts tied to a specific strategy set.

The vault admin is the user. Under the current model, only the vault admin can withdraw. The relayer is authorized for execution flows only and is not a withdrawal destination.

Users should deposit through the Mojomaxi dashboard so balances, vault bookkeeping, and strategy state stay in sync.

Execution model

Mojomaxi coordinates work through backend routes, Redis-backed state, locks, and a relayer that submits automation transactions on Solana.

Webhook alerts and rebalance checks both flow into guarded execution paths. The relayer pays SOL gas under the current product model, while the program enforces permissions and invariants on-chain.

Execution is best-effort, not guaranteed. Route availability, liquidity, token support, slippage, and network conditions all matter at the moment a swap is attempted.

On-chain protections

  • Canonical ATA enforcement for expected token accounts.
  • Ownership, mint, treasury ATA, and account-shape validation.
  • Token-program checks for supported SPL Token and Token-2022 flows.
  • Slippage, overspend, and Jupiter CPI failure handling.
  • Allowlisted relayer checks through the global Config account.

Execution paths & cleanup

Mojomaxi uses Jupiter-routed CPI swap execution on-chain. The program supports both a standard PAS flow and an EC-PDA execution path with cleanup helpers.

In plain English, that means the system has dedicated paths for robust execution and post-swap cleanup when routes create temporary accounts or need extra bookkeeping.

This helps reduce stranded token-account clutter and makes heavier routes more operationally manageable.

Operational dependencies

  • Solana network health and finality.
  • Jupiter route availability and liquidity at execution time.
  • RPC providers and supporting infrastructure.
  • Mojomaxi backend routes, Redis-backed coordination, and relayer uptime.
  • Correct user configuration for tokens, cadence, signals, and funding.

What users should understand

Mojomaxi is non-custodial, but it is not risk-free. Users still choose the assets, the strategy logic, and the amount of capital placed into each vault.

The protocol fee is separate from market effects like spread and slippage. A running strategy may still skip, retry, or fail to execute if conditions are not acceptable at the time of the attempt.

Users should only run strategies they understand and should only fund vaults with assets they are prepared to manage under normal market volatility.

Transparency & verification

Power users can inspect the published IDL, public program addresses, transaction history, and relayer config. Mojomaxi surfaces activity in-app, while core on-chain state remains independently verifiable.

Need help reviewing vault behavior or execution details? Open a support ticket in Discord and include your wallet, set ID, and a concise description of what you observed.