Setup and User Guide

Start Here: What ProfitBot Does

ProfitBot is a locally installed automation workspace for six meme coin markets—Solana, BSC, Base, Robinhood, Ethereum and Hyperliquid—and two prediction market services, Polymarket and Kalshi. Meme coin strategies use token discovery, market evidence, execution conditions and position limits. Prediction strategies use event contracts, reviewed probabilities, order books and settlement rules. They share account-level controls while keeping their settings and account requirements separate.

Begin by installing the correct package, obtaining a license, securing the account you will trade with and preparing one clearly named strategy. Then review the account, capital and execution state before enabling activity. A connected wallet, saved strategy or visible market does not by itself authorize a trade. The app checks the selected account, entitlement and risk conditions again when an action is requested.

Use this guide in order for initial setup, or use the section navigation to find a particular workflow. All money examples explain units or controls; they are not recommended allocations or promises of returns. You decide which markets to use and how much money you are prepared to lose.

Install the Correct Desktop Package

Open Download and choose the installer matching your operating system and processor. On macOS, confirm whether your computer uses Apple Silicon or an Intel processor and choose the matching available package. On Windows, use the supported 64-bit package. On Linux, x64 means an Intel or AMD processor; ARM64 means an ARM processor. A .deb package is intended for compatible Debian or Ubuntu systems, while AppImage is a portable format for compatible Linux distributions.

Use official download links and follow the platform's verification and installation instructions. Do not bypass an unexpected signature warning or install a copy sent by an unsolicited direct message. A download for the wrong architecture will not become compatible because you rename the file. Keep enough free disk space for the application, trading records and backups.

Install under an operating-system account that you control. Secure the device with a strong sign-in credential and restrict access by other users. On a VPS, secure remote access and confirm that the host and operating system meet the package requirements. Do not expose a remote desktop or wallet interface to unrestricted public access.

Choose Your License Duration

Visit License to choose a flexible plan for 30, 60, 90, 120, 150 or 180 days, or select Annual for a one-year license. Every paid plan includes all nine simultaneously active markets and unlimited named strategy drafts. There is no separate market-count selection or charge. The included markets are Solana, BSC, Base, Robinhood, Ethereum, Hyperliquid, Polymarket, Kalshi and OpenSea.

OpenSea is one of the nine included markets across its supported underlying networks. Before changing a market’s strategy or account connection, pause new entries and resolve any orders or positions that prevent a safe handoff. Simply viewing another market in the header does not stop the previous one. Multiple strategies in the same market still share that market’s account and risk obligations.

License prices are fixed in USD and payments settle in the same amount of USDC on Ethereum. Only the selected duration determines the paid-plan price; all nine markets are included in every plan. Supported Ethereum payment tokens can be converted through checkout. Gas and swap costs are additional; inspect the total amount required from your payment wallet before signing.

Register and Pay for a License

Enter the required email, review the Terms of Service, Privacy Policy and Refund Policy, and save your registration. Your email supports license administration and software updates. Registration also records your connection IP for security and fraud prevention. Saving this information prepares your account; it is not a payment and does not create a paid license.

Use Connect & Verify Payment Wallet to establish the payment account. In a browser, choose your compatible wallet and inspect the sign-in message. The ownership message should identify the service and its purpose. It does not authorize a transfer. In the desktop app, verification opens your browser wallet. Your Ethereum payment private key is not imported into the bot. Never paste a recovery phrase into the website or send one to support.

License payments settle in USDC on Ethereum. Confirm the selected duration, inclusion of all nine markets, Ethereum payment wallet, USDC amount and order expiry. An eligible affiliate referral splits the existing license price between the company and affiliate. For example, a $299 30-day license with a 10% commission sends 269.10 USDC to the company and 29.90 USDC to the affiliate. Customer-paid gas and swap costs are additional and must not reduce either recipient’s amount.

Inspect the transaction in your wallet before signing. Payment verification must confirm the intended transaction before the signed license is issued. If confirmation is delayed, keep the purchase reference and transaction signature and check the existing purchase. Do not send another payment merely because a page is still waiting. An expired quote should be refreshed instead of manually sending its old amount.

Activate and Manage Licensed Wallets

Use the License section in the app to review your entitlement and associated public trading wallet addresses. The payment wallet and the account used for trading can serve different purposes. Your verified Ethereum payment wallet identifies the license. Configure trading wallets in the desktop app, then link the EVM trading wallet to the active license from Trading Wallet. Pause markets before changing a binding. Public address settings do not import private keys or transfer assets.

Verify each address against the wallet you control. An EVM address has the same visual format on several networks, but a matching string does not establish the correct network balance or permission. Confirm the selected market before associating an address. Kalshi account credentials are configured through its account connection rather than treated as a Solana wallet address.

Do not edit local configuration files to transfer an entitlement. Use the account controls and ownership verification required for the change. A displayed license record should agree with its duration, scheduled periods and active capacity. If it does not, retain the reference and contact support before attempting more purchases or changing trading accounts.

Setup Your RPC Endpoints

ProfitBot uses your own RPC connections to read blockchain data and submit transactions. ProfitBot supplies neither endpoint. An Alchemy Pay As You Go plan is required; the free plan lacks capabilities the app needs. Create an Alchemy account and enable Pay As You Go before configuring your connections. Provider charges belong to your Alchemy account.

1. Obtain both endpoints for each network

In your Alchemy dashboard, select the correct network and copy its complete HTTPS RPC endpoint and WebSocket (WSS) endpoint. These are two separate URLs. Paste each exactly as provided; do not create the WSS address by editing the HTTPS address. Configure the networks you use: Solana, BSC, Base, Robinhood, Ethereum, Hyperliquid (HyperEVM) and Polymarket International (Polygon). OpenSea uses the RPC pair for its selected underlying chain. Kalshi and Polymarket U.S. use their venue API connections rather than an Alchemy RPC pair.

2. Enter your HTTPS and WSS URLs

Open Settings → Your RPC Endpoints and choose the network. The endpoint setup is also available in the License registration flow and under Trading Wallet for the selected market. Polymarket International also exposes its Polygon endpoint setup in the account connection settings. Paste the HTTPS URL into HTTPS RPC Endpoint and the WSS URL into WebSocket (WSS) Endpoint. Repeat for each network you intend to use.

3. Test, review and save

Select Test HTTPS & WSS. The app checks the selected network, the RPC methods it requires and the WebSocket connection, including a short-lived subscription test. Review any named chain, endpoint or method failures. A failed test can indicate the wrong network, an invalid URL, unavailable service or insufficient plan capabilities. Testing does not place a trade; transaction-submission checks use non-broadcast validation probes.

After both connections pass, select Review & Save Endpoints and approve the native confirmation. Saving independently checks both endpoints again and stores them encrypted on this computer. Editing either URL requires another successful test. Restart the app to apply saved endpoints, then check the connection status before enabling a strategy. Saving endpoints does not start trading. Configure each computer separately and never share endpoint URLs or API keys in screenshots, community posts or support messages.

4. View your compute-unit usage

For an optional usage display, create a separate Alchemy access key in Dashboard → Security with Usage read (ADMIN_USAGE_READ) permission only. Your RPC endpoint key cannot retrieve account usage totals. Open CU usage access (optional), enter the read-only Usage access key and use the same test, review and save workflow. Do not grant write permissions.

Alchemy account CU usage this month appears below the connection controls. It refreshes every 60 seconds while the panel is visible and shows when the data was checked, plus the provider data-through time when available. These are account-wide Alchemy totals, including usage outside ProfitBot; they are not per-market or ProfitBot-only totals. Without a valid read-only Usage access key, the display reports usage as unavailable rather than zero. Connection tests and ongoing health checks also consume your provider usage.

5. Understand connection warnings

A missing, invalid or rate-limited RPC connection shows a warning and pauses new entries for the affected network. Protective exits remain enabled using available customer RPC connections. This does not guarantee an exit can execute during a provider or network outage. Restore the required connections, review the test results and reconcile outstanding orders and positions before resuming new activity.

Understand the Header and Sidebar

The top bar shows your license countdown, the local engine status and the Emergency Stop button.

Use the sidebar to open Overview, Positions, Market Discovery, Trade History, Strategies, Risk Controls, Trading Wallet, License, Billing, Settings, Documentation, Affiliates and Support, followed by links to Community, Discord, Telegram and X. The navigation scrolls when the window is too short to show every item.

When you open Positions, Market Discovery, Trade History, Strategies, Risk Controls or Trading Wallet, the list of nine markets opens under that item: Solana, BSC, Base, Robinhood, Ethereum, Hyperliquid, Polymarket, Kalshi and OpenSea. The selected market is outlined in its color and appears in the page title. The six meme coin markets use the same strategy layout, Polymarket and Kalshi show prediction settings and their account profiles, and OpenSea has a separate NFT workspace that stays unavailable for trading until its integration is complete. Overview combines all nine markets.

The selected market scopes the account, strategy, discovery and reporting screens you are viewing. It does not bridge assets, convert currencies or silently enable another engine. ETH on Base is a Base balance; ETH on Ethereum is an Ethereum balance. The currency label alone is not an account identifier.

Set Up a Solana Trading Wallet

Select Solana and open Trading Wallet. Use the local wallet controls to establish the dedicated account you intend to use for automated meme coin positions. Read the application's file and confirmation prompts carefully. Keep the recovery information in a protected location separate from ordinary screenshots, shared folders and support messages.

Check the Solana trading address shown in the app against the trading wallet you intend to use. Your Ethereum license wallet is separate. Fund the account with an amount consistent with your capital plan and keep SOL available for transaction fees and required account operations. A token balance does not replace the native SOL needed to perform a transaction. Do not allocate the entire visible balance to positions.

Unlocking a wallet permits the local signing workflow subject to the app's controls; it does not enable a strategy automatically. Lock it when it is no longer needed. If you replace the wallet, verify the new address, recovery state and license association before requesting activity. An old wallet's positions do not transfer merely because the app displays a different account.

Set Up BSC, Base, Robinhood and Ethereum Wallets

Choose the relevant market first, then open Trading Wallet. Use Import Wallet From File for the supported local key-file workflow. The file contains the private key required by that wallet import; it is selected through the native application and is not pasted into the website. Confirm the public address after import and keep access to the source recovery material secure.

Use Unlock Wallet when a local operation requires it. The app displays whether the wallet is locked and whether recovery has been verified. For encrypted recovery, enter a strong recovery passphrase of at least 20 characters, use Export Encrypted Recovery and store the resulting file separately from its passphrase. Restore Encrypted Recovery requires the corresponding file and passphrase and leaves the wallet locked after restoration.

BSC uses BNB for network fees. Base, Robinhood and Ethereum use ETH on their respective networks. Assets on one network are not automatically available on another, even when the same address is used. Confirm the network and receiving address in any external funding or bridge interface before transferring money. ProfitBot's market selector does not perform that transfer.

An ERC-20 token allowance authorizes a particular spender to move a particular token under the network's rules. Review the router, amount and intended purpose when an approval is required. An allowance can remain after a position closes. Manage unwanted permissions through an appropriate account workflow; never treat an unfamiliar approval as a harmless sign-in message.

Connect Hyperliquid and Select the Trading Environment

Hyperliquid meme coin trading can involve HyperCore spot markets or HyperEVM token markets. These are different execution environments. HyperCore spot activity uses order books, spot asset identifiers, balances and account permissions. HyperEVM activity uses EVM contracts and HYPE for the relevant network operations. The HYPE label in the header is not a statement that every spot pair settles in HYPE.

Open Trading Wallet with Hyperliquid selected and review the account connection, selected market type and asset identifiers. Use the account permissions needed for the chosen workflow and keep the signing credential protected locally. An agent or trading authorization is not the same as ownership of every balance or permission to withdraw funds.

For spot strategies, review the quote asset, available balance, minimum order quantity, price precision and executable depth. An order's unfilled remainder continues to reserve capacity or capital until its status is resolved. Check both fills and remaining order quantity when deciding whether another position fits your limits. Hyperliquid's meme coin scope does not mean that the strategy is a leveraged perpetual-futures strategy.

Connect Polymarket International or U.S.

Choose Polymarket in the header. The Account Region buttons show Polymarket International and Polymarket US. International is the initial selection. Choose the service you are eligible to use before entering credentials or saving strategies. These services have separate accounts, market availability and authentication requirements; a credential from one should not be entered into the other.

Open Trading Wallet for the selected profile and use the account-connection fields and protected native prompts. Enter only the credential types requested for that profile. Follow the provider's own process for obtaining API access and review the permissions. Keep signer or wallet information consistent with the account that holds the positions and the public account identity displayed by the app.

Save the connection and review the authentication and wallet-verification results. A valid API credential is one prerequisite; a spendable balance, required permissions and an eligible contract are separate prerequisites. If verification reports a mismatch, resolve it before trading. Do not attempt to bypass a geographic or account restriction by changing the profile name.

Connect Kalshi Demo or Live Account

Choose Kalshi and use the visible Account Environment buttons. Demo and Live Account use distinct environments and credentials. Demo is useful for learning the provider's account workflow; its balances and outcomes are not actual-money performance. Changing to Live Account requires the correct credentials and a fresh account review.

Open Trading Wallet for the selected environment. Supply the requested API key identifier and protected signing credential through the app's connection workflow. A key identifier alone does not complete authentication. Verify that the account returned by the provider is the one you intend to use and that it has the relevant permissions and funds.

Keep environment-specific strategy drafts separate. A successful connection to Demo does not establish a funded Live Account, and switching the environment does not move balances or positions. If credentials are replaced or revoked, reconnect and review account status before requesting new activity.

Read Overview, Discovery and Positions

Overview summarizes the selected scope's balance, exposure, realized profit and loss, position count and execution status. Overview combines available information across all nine markets. A combined USD figure requires current valuation evidence; an unavailable number is not a zero balance. Compare the timestamp and account scope when reviewing figures from different screens.

Market Discovery lists supported candidates and the evidence available for them. A discovered token is not an approved purchase. Eligibility, pool identity, liquidity, concentration, freshness and the selected strategy still matter. On Solana, the supported PumpSwap workflow follows verified finalized Pump.fun graduation. Earlier token creation or an unconfirmed migration does not establish that boundary.

Positions shows existing exposure, including states that still need reconciliation. Trade History records completed and attempted activity and its relevant identifiers. Keep pending or uncertain requests visible until the source confirms their outcome. A red or unavailable state should prompt investigation, not an assumption that nothing happened.

Build a Meme Coin Strategy

Select one of the six meme coin markets, open Strategies and choose Low, Moderate, High or Custom. Presets populate related values as a starting point. They are relative configurations, not a guarantee that a token is safe or that a strategy will be profitable. Edit a field to form your custom version and give it a descriptive name.

The editor groups settings into Markets, Entry, Capital, Execution, Exits and Limits. Review all six groups before saving. Markets controls which candidates qualify. Entry describes the observed conditions needed for consideration. Capital controls allocation and position capacity. Execution limits permitted prices and costs. Exits defines conditions for attempting to close exposure. Limits constrains repeated activity and account losses.

Save Draft stores the configuration. Duplicate creates a separate draft you can name and adjust. Archive removes a draft from active use without pretending that its historical activity did not happen. The saved revision identifies the settings behind a particular record. Unsaved edits are not a new saved revision and should not be assumed to alter an already bound strategy.

Check the unit printed beside every number. A reserve threshold in SOL is not the same monetary amount as the identical number in BNB or ETH. Position percentages refer to the allocation basis described by the capital control, while loss limits can refer to account equity. The reference below lists each field and the permitted range shown by the editor.

Allocate Capital and Preserve Exit Capacity

Decide the total amount available for the market and the maximum share that one position may use. Apply an aggregate exposure ceiling and a count limit for open plus pending positions. Pending orders consume room because they may still fill. An apparently empty position list does not make an unresolved submitted request safe to ignore.

Reserve enough native currency for operations and exits. Include transaction fees, approvals where needed, account creation where relevant and failed attempts. For an order-book market, also consider funds reserved by resting orders and the minimum trade sizes. A capital plan should not require a favorable trade to fund its own exit.

For example, if an allocation basis is $1,000 and a position ceiling is 2%, that ceiling is $20. A 10% total exposure ceiling allows no more than $100 on that same basis, subject to any tighter count, fee or balance control. Those figures illustrate the relationship between settings; they are not a recommendation. Check that the app's actual account valuation and units support the calculation you intend.

Configure Copy Trading and Optional AI

Copy-trading settings belong to the selected meme coin strategy. Specify supported source wallets, the permitted copy behavior and the limits shown in that section. Identify the source by its full public address, not a display name. A copied signal is still subject to your market eligibility, position, price, cost and loss limits.

Your copy can arrive later than the source trade, have a different price or size, or be rejected entirely. A source may close a position while you have an unresolved entry. Decide how your own exit rules apply before using the feature. Never assume that a source wallet's public gains describe your expected result or reveal every related account it controls.

The optional AI assistant in Strategies offers Grok Bot through xAI, Claude and ChatGPT. Select a provider, configure your own API connection in the protected local workflow and choose the model and budget controls offered for it. A consumer chat subscription is not necessarily API access. Provider usage can incur charges independently of the ProfitBot license.

Review each proposal before applying it. The AI does not replace independent risk checks, signed account permissions or license limits. If a provider request fails or exceeds its budget, inspect the status instead of repeatedly retrying without understanding the cost. Do not put private keys, recovery phrases or unrelated personal information into a prompt.

Build a Prediction Market Strategy

Select Polymarket or Kalshi and the correct account profile, then open Strategies. Give the draft a name, choose its market category and select Yes, No or Both where appropriate. Read each contract's full rules before treating a market as a candidate. Similar titles do not guarantee matching outcomes, deadlines or settlement sources.

Use the Probability Estimate Source buttons to choose a Manually Reviewed Estimate or a Reviewed External Model. A probability is your assessed chance of the defined outcome, not simply the contract's current price. For a manual review, save the strategy first, identify the market and outcome, enter a probability between 0% and 100% exclusive, explain your rationale, choose its validity period and acknowledge the review. Refresh or revoke an estimate when its basis changes.

The minimum edge setting compares the selected outcome's estimate with the permitted acquisition cost after the relevant fees and slippage. Book depth, spread, price bounds and estimate freshness constrain the entry. A forecast can be well explained and still wrong. Do not increase a stale estimate's validity merely to avoid reviewing new information.

Set capital in USD, a maximum position cost, aggregate open and pending exposure, and a correlated-event limit. Several contracts can depend on one underlying result. Resolution timing and an intended exit-before-resolution buffer belong in the exit plan, together with holding limits and loss controls. The prediction settings reference lists the exact units, including basis points of a $1 payout rather than a percentage return on the purchase price.

Review and Enable Activity

Before requesting activation, confirm the selected market, account, saved strategy revision, license term, available capacity, balances, gas or fee reserve and all applicable risk limits. Review the app's readiness and validation results. If a prerequisite is missing, resolve that condition; repeatedly pressing an activation control does not substitute for it.

Enabling a strategy is a separate decision from editing or saving it. Inspect the configuration that the confirmation identifies and verify that it belongs to the intended wallet and market. A valid entry signal can still be rejected because the quote changed, the account is locked, another order reserved capital or a shared limit was reached. Rejection is part of applying your rules consistently.

Supervise activity after activation. A local app depends on its device and network remaining available. Keep system sleep and remote-session behavior consistent with how you intend to operate, and maintain a way to reach your accounts if the app or provider is unavailable.

Exits, Emergency Stop and Market Handoffs

Stop Loss, Take Profit, Trailing Activation, Trailing Distance and Maximum Holding Time define conditions for an exit attempt. They do not guarantee liquidity or a particular realized price. A trailing rule starts only after its activation condition is reached; its distance is measured relative to the applicable peak. Review how a full take-profit target interacts with that activation threshold.

Emergency Stop blocks new entries and remains in effect until deliberately cleared. It is not a Sell All instruction. Sell All is a separate confirmed action that attempts to close applicable positions and reports each outcome. A paused engine can still have exposure, an unfilled order or an uncertain transaction that needs attention.

Before changing a market’s strategy or account connection, stop new activity, review its remaining positions and orders, and complete the required safe handoff. All nine markets are included in every paid plan; selecting a different workspace does not erase unresolved activity. If an exit or cancellation is unresolved, check its source record before resuming.

Handle Connection Loss and Uncertain Transactions

If the provider or network becomes unavailable, inspect the last verified account and transaction state. New actions should not rely on an old quote or stale balance. Reconnect and refresh the relevant records before deciding whether to continue. A restored internet connection alone does not prove that every earlier request failed or succeeded.

For a submitted transaction, preserve its signature or hash. For an order, preserve the order identifier and any recorded fills. Compare the chain or market outcome with the app's reconciliation view. Avoid manually submitting a duplicate while the original could still execute. A successful cancellation request also needs its final state reconciled against fills that may have occurred at the same time.

After restarting the app, verify the selected account, wallet lock state, active license, outstanding orders and positions. Resolve any discrepancy before starting additional exposure. If support is needed, include the public identifiers and error messages that explain the situation, while keeping secret credentials out of the request.

Read P&L, Export Invoices and Share a Result

Realized profit and loss depends on completed exposure and attributable costs. A market price displayed beside an open token balance is not realized cash proceeds. Check the reporting scope, period and currency basis. Missing valuation or fee information can prevent a trustworthy net figure from being calculated.

The P&L sharing feature generates a graphic only for an eligible verified positive net realized result. Choose the supported trade, market or time scope, review the graphic and caption, and decide whether to post. It includes the ProfitBot branding and the USD profit for the selected scope. A positive shared trade does not represent every trade in the account.

Approved affiliates can include their referral URL in the caption and the visible graphic. The text link opens the referral destination. X treats an uploaded image as media, so clicking the image opens its image viewer; it is not a second external link. Review the destination and any affiliate advertising disclosure before posting.

For payment records, sign in with the payer or relevant licensed wallet and open Billing. Select the verified purchase and download its PDF invoice. Its paid duration and amount are historical records and do not change because a later service credit extends a license. If a record is missing, use the original transaction reference when contacting support.

Extend a License

The countdown in the upper-right corner shows the remaining license time. Its visual urgency increases as expiration approaches, and the extension action opens the license screen when the remaining period is short. Check the actual dates as well as the color, especially if a later period has already been scheduled.

Select the duration for the next paid period. It can be shorter or longer, subject to the options shown, and all nine markets remain included. Review when the new period begins and how it affects activity at the boundary. A renewal does not erase orders or automatically make an unsafe account handoff complete.

An extension is a new USDC payment with its own order. It is not an undisclosed recurring charge. If a license expires, new entries can be blocked while existing positions still require management. Arrange the extension and any necessary account handoffs before that boundary if continuous authorized operation matters to your plan.

Apply for the Affiliate Program

Open Affiliates, connect the Ethereum wallet that will receive USDC commissions and complete the application. Name, email and an explanation of how you will promote ProfitBot are required. Discord, X, Instagram, TikTok, YouTube and a website are optional. Choose a referral name containing 3–15 letters or numbers and check that it is available.

Sign the application ownership message when you are satisfied with the application. This is not an on-chain transaction and has no gas fee. Your application remains pending until manually approved; a pending account cannot earn commissions.

An approval email contains your referral URL and basic account information. An approved dashboard shows the current commission rate, eligible referrals and direct Ethereum USDC payments. The default rate is 10%, with higher rates possible when authorized. A denial email communicates the outcome; a new application should explain materially changed promotion plans rather than disguise the earlier identity.

Share the correct referral link and disclose the affiliate relationship. Eligible referral storage lasts up to 60 days, but browser choices and purchase eligibility affect attribution. The customer's signed license transaction pays the affiliate portion directly to the registered wallet. Verify that receiving address and keep its recovery information secure.

Contact Support and Maintain Your Workspace

Use the website support widget or the Contact page. At the top of the widget, choose No under Current Licensed User? to send a general inquiry, or Yes to verify a wallet and open licensed user chat. The default No view shows the message form. Licensed chat requires an active entitlement associated with the verified wallet.

Describe the selected market, account environment, action attempted, time of the problem and relevant error or public transaction identifier. AI-assisted support can help explain the interface, but it can make mistakes and does not provide financial advice. Do not grant remote control or send secrets in response to an unsolicited message claiming to be support.

Keep secure backups of the local records and recovery material you need. Confirm that a recovery file can be used with the proper passphrase before relying on it, and keep the passphrase separate. Do not assume that a general project backup includes an operating-system keychain or credentials held by another provider. When replacing a device, review account permissions and lock or revoke access that is no longer needed.

Before installing an update or moving to another computer, inspect open positions and outstanding orders and plan the interruption. Afterward, verify the version, account identities, license status, strategy revisions and reconciliation state. Return to the FAQ for common license questions or Contact for a problem that remains unresolved.

Security Setup Checklist

Complete these checks before connecting credentials or funding a trading wallet. Repeat the relevant checks after an update, device change or security incident.

• Download ProfitBot only through the official Download page. Verify the platform, processor and available signature or notarization information. Do not bypass an unexpected security warning or install a copy sent in an unsolicited message.
• Keep your operating system, browser, wallet software and ProfitBot updated. Use appropriate malware protection and avoid untrusted software, extensions and attachments on a trading device.
• Protect your operating-system account with a strong sign-in credential and restrict other users. Lock unattended sessions. On a VPS, secure remote access, enable additional authentication where supported, and do not expose desktop or control interfaces to unrestricted public access.
• Independently open the official website to verify unexpected support, payment or account messages. Inspect the destination, network, amounts, permissions and purpose before approving a wallet message or transaction. Support does not need your private key, recovery phrase or API secret.
• Use the minimum permissions required by each integration, review contract approvals, and disable withdrawals where the provider supports a separate withdrawal permission. A trading credential can still cause trading losses without withdrawal authority.
• Protect encrypted recovery files and backups. Keep their passphrases separately and verify recovery before relying on a backup. Do not put credentials in screenshots, community posts or support messages.

See Permissions by Integration and Credential Recovery and Revocation. These precautions reduce exposure; they do not guarantee security or prevent trading losses.

Permissions by Integration

Grant only the access needed for the workflow you choose. Permission names and availability depend on the provider and account type; check the provider’s current official controls. Where separate read, trade, transfer, withdrawal or administration permissions exist, use necessary read/trade access and disable unnecessary withdrawal, transfer and administration privileges. A provider may require read/write access for order submission without offering a separate trade-only label.

Solana

Use a dedicated trading wallet you control and the RPC access required for chain reads and authorized transaction submission. Keep only the assets and SOL needed for your intended activity and fees. A Solana private key is signing authority, not an exchange API key with a withdrawal-disable switch.

BSC

Use a dedicated BSC trading wallet, the required BSC RPC connection and only contract approvals needed for the selected tokens and trading routes. Keep BNB available for applicable fees. Do not grant unrelated token spending permissions or assume that an allowance limits all actions a compromised private key could sign.

Base

Use a dedicated Base wallet and the required Base RPC connection. Review each token approval and spender, and approve only what the selected workflow requires. Keep the appropriate native asset for fees. An API-key withdrawal setting does not restrict the underlying wallet key.

Robinhood

For the supported Robinhood chain workflow, use the selected chain’s wallet and RPC configuration. This is not permission to access an unrelated brokerage account. Review the network, spender, token approvals and funds exposed to that wallet before enabling activity.

Ethereum

Use a dedicated Ethereum trading wallet and the required Ethereum RPC connection. Review the chain, destination, spender and token allowance before signing. Keep ETH for applicable fees and avoid unnecessary contract approvals. The Ethereum wallet used for licensing need not be imported as a trading wallet.

Hyperliquid

Distinguish HyperCore spot account/agent access from HyperEVM wallet signing. For HyperCore, use a dedicated provider-approved trading agent where supported and keep the account’s master credential separate. Review the agent’s actual authority and revoke it through the provider when no longer needed. For HyperEVM, use the required wallet, RPC access and contract approvals; the normal EVM private key is not inherently trade-only.

Polymarket

Use credentials for the exact International or U.S. profile and account you intend to connect. International CLOB API authentication is distinct from wallet signing and any required on-chain approvals; protect each separately and review the actual signer, funding account and spender. For the U.S. profile, grant only the account-reading and order permissions required by its connection process. Disable unnecessary transfer or withdrawal permissions where the chosen service exposes them; do not assume that both regional services have identical permission controls.

Kalshi

Use a dedicated API key for the selected demo or live environment. Account reads need read access; placing and canceling orders requires the provider’s applicable write access. Retain only required account permissions and restrictions, and do not grant unrelated administrative or withdrawal capabilities where separately configurable. Keep the private signing key local and revoke the API key through Kalshi if compromised.

OpenSea

Use the API access needed for supported market data and order workflows. An API key alone is different from the wallet authority needed to sign orders, transactions or token approvals. Review the selected chain, collection, token, spender and marketplace approvals. Avoid unrelated approvals and revoke unused permissions with the appropriate wallet or provider controls.

RPC and Optional AI Providers

Use dedicated project credentials where available. RPC access should cover the chain reads, subscriptions and transaction submission required by the app, without unrelated account-administration privileges. The optional RPC usage display needs only its separate read-only usage permission. Optional AI access should permit the selected inference service with appropriate usage limits; do not supply trading private keys or wallet recovery phrases to a model or prompt.

Wallet Keys and Trade-Only Permissions

Ordinary blockchain private keys generally allow their holder to sign transactions for the associated wallet. They do not universally offer a trade-only setting or a withdrawal-disable checkbox. Restricting one application’s interface does not remove the underlying authority of a copied or stolen private key.

Exchange API keys, delegated trading agents, token allowances and ordinary wallet keys are different forms of authority. A withdrawal-disabled API key may still place losing trades. A token allowance restricts a particular spender’s approved access, not every transaction the wallet key can sign. A delegated agent’s limits depend on the provider’s actual rules.

Use dedicated trading wallets, limit the funds exposed, review each approval and signature, and keep unused credentials and permissions revoked. Do not treat local encryption or a trade-only label as a guarantee against loss.

Credential Recovery and Revocation

Keep encrypted recovery files in a protected backup location and keep the passphrase separately. Verify that a recovery file belongs to the intended wallet and can be recovered through the official local workflow before relying on it. Do not send the file or passphrase to support, and do not place an unencrypted key in a general backup, shared folder or message. An ordinary application backup may not contain the operating-system keychain or everything needed to recover credentials.

Before replacing a device, review open positions, outstanding orders and pending transactions. Stop new activity where appropriate and plan the interruption; closing or uninstalling the app does not automatically cancel orders held by a market. Restore only on a trusted device, verify the account and wallet identities, and reconcile activity before resuming.

If a device or credential may be compromised, stop relying on that device. From a trusted device, revoke or rotate the affected API keys and delegated agents through the issuing provider, review active sessions and contract approvals, and change affected account credentials. If a blockchain private key or recovery phrase is exposed, deleting it from the app does not revoke it: secure remaining assets using a new uncompromised wallet when it is safe to do so and review approvals and outstanding obligations. Transfers and cancellations may incur costs, fail or remain pending; verify their actual outcomes.

After recovery or replacement, remove obsolete access and protect or securely dispose of old recovery material according to your backup plan. Never assume that reinstalling ProfitBot, changing an app passphrase or removing a local file invalidates a secret already copied by someone else.

Meme Coin Settings Reference

These ranges are the accepted input bounds. They are not suggested risk levels. Capital and execution controls may impose tighter limits for your account. SOL labels change to the selected network’s native unit; HyperCore spot filters use their specified quote asset. One basis point of a $1 payout is $0.0001, so 100 basis points is $0.01.

Prediction Settings Reference

These ranges are the accepted input bounds. They are not suggested risk levels. Capital and execution controls may impose tighter limits for your account. SOL labels change to the selected network’s native unit; HyperCore spot filters use their specified quote asset. One basis point of a $1 payout is $0.0001, so 100 basis points is $0.01.