Credentials

How DEX connections work. Nothing stored by default. Optional encrypted storage for AI trading, monitoring, and Telegram.

How connections work

To trade on a DEX, you connect your wallet on the Trade page and sign a message to authorize a trading session. Once connected, you see a green dot next to the exchange name in the Accounts rail.

Nothing is stored server-side by default. Connections live in your browser. Most exchanges authorize a persistent signer key, so they reconnect automatically on your next visit. A few mint time-boxed sessions instead; the rail shows an amber dot and an extend prompt before one expires, and the backend cannot renew those for you.

Registering and funding accounts is covered in Funding & Transfers.

Optional: backend storage

If you want Guard Cloud mode to auto-close your positions 24/7, or to trade through MCP (AI assistant) or Telegram, we need access to your DEX credentials when no browser is open. You can optionally store them on the backend.

What gets stored:

The credentials needed to authenticate with each DEX (varies per exchange)
Encrypted with AES-256 before storage
Every access is audit-logged

What this unlocks:

Guard Cloud mode: auto-close on funding flip, TP/SL, alerts, even with the tab closed
AI trading via MCP. Ask Claude to open/close positions for you
The Telegram trading terminal: positions, balances, open/close/cancel from chat
Server-side executions that outlive your tab: backend TWAP and Find the Exit

How to store:

On the Trade page, click Manage on the compact Protection row at the top. The full DEX list slides out in place. Toggle the exchanges you want saved.
Or via the store_credentials MCP tool

Revoking credentials

You can delete stored credentials for any DEX at any time:

On the Trade page, click Manage on the Protection row and toggle the exchange off
Via revoke_credentials or revoke_all_credentials MCP tools

Once revoked, Guard Cloud mode, MCP, and Telegram lose access to that exchange immediately. Browser trading is unaffected since it uses its own session.

Which mode should I use?

Without stored credentials, you can only manage positions while the browser tab is open. In that setup, Guard runs in Browser mode: TP/SL, funding flip, and auto-close all fire tab-side.

With stored credentials, Guard Cloud mode handles monitoring 24/7: auto-close runs server-side, Telegram alerts fire whether or not you're watching, and the MCP assistant can manage positions for you. Setup takes 30 seconds and you can revoke anytime.

FAQ

Does ProFunding store my exchange credentials?

Not by default — connections live in your browser and most exchanges authorize a persistent signer key that reconnects automatically. Storing credentials on the backend is optional and only needed for Guard Cloud mode, MCP trading, or the Telegram terminal.

How are stored credentials protected?

They're encrypted with AES-256 before storage, and every access is audit-logged.

What can I do once I store credentials?

Guard Cloud mode can auto-close on funding flip, TP/SL, or alerts even with the tab closed; you can trade via MCP by asking an AI assistant; you get the Telegram trading terminal; and server-side jobs like TWAP and Find the Exit can run and outlive your tab.

How do I revoke stored credentials?

On the Trade page, click Manage on the Protection row and toggle the exchange off, or use the revoke_credentials / revoke_all_credentials MCP tools. Browser trading is unaffected since it uses its own session.