Quantum Finance never holds your private keys, your seed phrase, or your wallet credentials. The funds you trade with live in a smart contract on BNB Chain — not on a Quantum server — and you retain the ability to withdraw at any time. This page explains how the wallet layer, the vault contract, and the trading engine connect, and what “non-custodial” means in practice for you as a trader.Documentation Index
Fetch the complete documentation index at: https://quantumfinance.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Your wallet: non-custodial from the start
When you log into Quantum Finance with Google, Web3Auth creates a non-custodial wallet on your behalf. Web3Auth’s architecture splits your private key into shares using threshold cryptography — no single party, including Quantum Finance, ever has access to your complete key. Your Google account controls one share; you can always recover your wallet as long as you can log in with the same Google account. This wallet is a standard BNB Chain EOA (externally owned account). You can import it into MetaMask or any other BNB-compatible wallet using the private key export option in Web3Auth if you ever want to manage it outside of Quantum.The TradingVault smart contract
When you switch to real mode and deposit BNB, your funds go into the TradingVault — a smart contract deployed on BNB Chain. The contract is the authoritative record of your balance and profit. Quantum Finance reads and interacts with it, but does not control it in the way a custodial platform controls a user’s account balance. The vault exposes the following key functions:getUserInfo with your wallet address at any time — directly via BscScan or a Web3 provider — to verify your balance independently from the Quantum UI.
The vault flow
Deposit BNB
From the Trading tab, enter a deposit amount and confirm the transaction. Your BNB is sent to the TradingVault contract via the
deposit() function. The transaction is signed by your Web3Auth wallet.Engine trades on your behalf
When you start the engine in real mode, it executes buy and sell swaps through PancakeSwap using your vault balance as collateral. The vault contract’s
executeBuyTrade and executeSellTrade functions handle the on-chain swap logic, including a 1% slippage tolerance calculated dynamically from the PancakeSwap router.Profits accumulate in the vault
Profitable trades result in token (USDT or USDC) flowing back into the vault under your address. You can see your accumulated profit via
getUserInfo. Profitable trades also emit a ProfitDistributed event on-chain, which the Quantum UI reads to display your on-chain profit figure.On-chain transparency
Every trade executed in real mode produces an on-chain event. The relevant contract events are:| Event | When it fires |
|---|---|
Deposited | You deposit BNB into the vault |
Withdrawn | You withdraw BNB from the vault |
TradeExecuted | The engine executes a buy or sell swap |
ProfitDistributed | A trade closes and profit is split between you and the Quantum treasury |
EmergencyWithdraw | An emergency withdrawal is triggered |
The current deployment runs on BNB Smart Chain Testnet (Chain ID: 97). When Quantum Finance moves to mainnet, the contract address and chain ID will be updated in the app configuration and announced in the documentation.
No platform risk on your deposits
Because the vault is a smart contract — not a custodial account — your BNB balance is not commingled with other users’ funds in a platform-controlled wallet. The contract tracks each user’s balance individually. If Quantum Finance’s servers went offline, your funds would remain in the contract and you could withdraw them directly by callingwithdraw() via any BNB Chain interface.