Security & Transparency
TokenOps/BEX uses a non-custodial wallet model. Users sign messages and transactions directly in their own wallet. TokenOps/BEX never receives, stores or controls private keys, seed phrases, wallet passwords or recovery credentials.
Open public GitHub transparency reference TokenOps on LinkedIn Automated trust score FAQ
Non-Custodial Model
Users review and approve actions inside Phantom, Solflare, MetaMask or another supported wallet interface.
TokenOps/BEX does not ask for private keys, seed phrases, wallet passwords, browser extension passwords or recovery words.
Payments are checked against blockchain transaction data before a payment-dependent action is considered complete.
What BEX Verifies
- Whether a submitted payment transaction exists on-chain.
- Whether the recipient, network, asset and amount match the payment intent.
- Whether a wallet signature proves control of a public wallet address for a specific action.
Security-relevant architecture is publicly documented in the BEX transparency repository. The repository is a public reference and not the full proprietary source code.
User Responsibility
Blockchain transactions can be irreversible. Users are responsible for reviewing wallet prompts, recipient context, network, asset and amount before signing. Third-party wallet providers and blockchain networks are outside TokenOps control.