🛡️ Security

Security principles at Fume are shared across products: restrict access to the minimum each party needs, make every sensitive action traceable, and keep data where it belongs. This page is the overview; product-specific detail lives in each section.

Tokenization Engine

The protocol is designed so that underlying liquidity stays in secure, segregated custody, and only interacts with the protocol at key moments — subscriptions, redemptions, and fee management. After a fund is deployed, only authorized parties can interact with its smart contract: the fund manager, and investors the manager has whitelisted. This drastically reduces the on-chain attack surface.

We engaged ChainSecurity, one of the leading smart contract auditors, to review the protocol — read the report.

For the full picture — implementation practices, testing, upgradability, and the catch-up mechanism — see Security & Risk Mitigation in the whitepaper.

AI agents

Agents act inside limits you set, and every action is logged and auditable, so your compliance team can trace each run. We monitor every run in production and handle the edge cases rather than leaving them to your team.

For funds whose data can't touch a public AI cloud, we deploy the same agents on open-source models entirely inside your own infrastructure — see Private & Local AI.

Authentication and data handling

There are no passwords on the Tokenization Engine. Users sign in with a one-time code sent to their email, powered by Privy (security details). Logging in gives a read-only view; any action that moves money or changes a fund requires wallet approval from the fund manager, and we recommend multi-signature solutions like Safe Wallet or Fireblocks for the governance wallet.

We store nothing on-chain that could be considered personal or sensitive data. That data lives on our servers, protected by industry-standard security and encryption. All wallets with important responsibilities on the Fume side are multisig smart wallets.