Docs

1. Connect your wallet. Enter a name, symbol, description and image, then choose your launch settings.
2. With vanity enabled, your browser searches for a real mint address ending in the launch page’s suffix. Cancel if you do not want to continue; the search never falls back to a random address.
3. Approve the upload signature, review the cost and transaction, then approve in your wallet. A launch is complete only after verification on Solana.

This runs on mainnet and costs real SOL. Signing a metadata message is not the same as approving a token purchase.

1. Open a token to view its detail page.
2. Use the Solscan link to verify the transaction and mint address.

The list shows confirmed launches, not every token on pump.fun. An empty list means no launches are displayed here.

1. Enter a suffix and start the search. Uppercase and lowercase letters are different.
2. Track attempts and search speed, or cancel. Once an address is found, you can copy it and download the key file.
3. Select Launch on pump.fun to use this exact address. Add your token details and image, review the cost and approve the launch in your wallet.

0, O, I and l are not allowed. Longer suffixes can take a very long time. Finding a keypair alone does not create an on-chain token. The key stays in browser memory during the handoff; refreshing the launch page clears it. The key file is private and grants control over the address.

1. Search by a memecoin’s name, symbol or mint address, or choose from the available assets.
2. Select Pair to add or remove a token. Live prices and available pump.fun details appear in the list.
3. Open Bundle to give your basket target weights, live exposure and a rebalance rule.
4. Open Airdrop to see which of your selected tokens are available for distribution.

Your selections are saved in this browser. Pair does not buy assets or create a funded pool. Tokenized stocks are not ordinary exchange-listed shares; pairing grants no ownership or dividends in the companies.

1. Add assets from the live coin and stock lists — new assets get an equal share of 100%.
2. Set each asset’s target weight. Live exposure shows the basket’s current price-weighted split; missing prices show --, never estimates.
3. Pick a rebalance rule: manual, drift over 5% or 10%, or a weekly review reminder. Flagged rows have moved beyond the rule’s threshold.

The basket is saved in this browser only and never trades on its own — rebalancing is always a separate wallet-approved action. Holder rewards and fee distribution appear only where a protocol supports them and they can be verified on-chain.

1. Select tokens in Pair first. The sender must own the token being distributed and have SOL for fees.
2. Once COMMAND CENTER’s mint address is configured, holders are read from Solana. Choose a token and amount; the amount is allocated proportionally to recipients’ holdings. The sender’s own wallet is excluded.
3. Approve each batch of up to five recipients in your wallet. History shows distributions confirmed on-chain.

Selecting Pair does not trigger an automatic reward. Distribution requires funding and wallet approvals. If the COMMAND CENTER address is missing, holder checks and distribution are disabled.

1. Select a service such as OpenAI, Claude or Lovable and choose Pair. Your selections are saved in your browser.
2. Website opens the service’s own site. Partner status and credit distributions are shown separately.

Credit airdrops go to $MDESK holders above $25. A selection does not activate a subscription or grant credits.

1. Search or sort the list and select a token.
2. Choose buy or sell, an amount, slippage and a priority fee. Review the simulation and cost.
3. Approve the trade in your wallet. Confirmation is awaited on Solana.

Slippage is the permitted price deviation. An estimate is not a guaranteed final price. Transactions that fail the checks are stopped before signing.

1. Compare available prices, volumes and changes.
2. Open a token for details and available trading options.

The list refreshes regularly and is not a recommendation to buy. Missing values appear as --, not estimated prices.

1. Browse, search and compare assets with available market data.
2. Open an asset to learn more about its token and market.

Check the mint address, not just the name. Multiple tokens may use the same name or symbol.

1. Connect your wallet to read its holdings.
2. Compare balances and the market values the page can retrieve.

Connecting a wallet does not transfer tokens. Missing prices mean the valuation is incomplete.

1. View current status and the history of measured availability and response times.
2. Select ML-DSA, SLH-DSA or ML-KEM in the playground and run a test. Test keys are generated in your browser.
3. Try an altered message to see how signature verification responds.

Status history is based on recorded checks, not continuous monitoring. Periods without checks are gaps and do not count as measured uptime.

1. Read endpoints, inputs, responses and error codes for available API calls.
2. Use the cURL, JavaScript or Python examples for algorithms, health, signature verification and KEM encapsulation.

Signing with stored private keys, decapsulation, API keys and billing are unavailable. Never send private keys to public API endpoints.

1. ML-DSA-65 and SLH-DSA provide digital signatures. ML-KEM-768 is used for key establishment.
2. Choose a method and continue to the playground or technical API reference.

The guide explains cryptography; it does not measure a token’s investment quality.

1. Connect your wallet to view available information on Solana’s Devnet test network.
2. Create, back up or restore your ML-DSA-65 identity under My Vaults & Key. The key stays in your browser.
3. The subpages provide key management, activity and local signature tests.

Devnet is not mainnet. Local signing does not mean tokens have moved or been locked. Deposits and withdrawals are inactive. Nobody can restore your local key if its backup is lost.

1. View available market data for the agents. Connect opens the agent’s own platform, where connection happens separately.
2. Add bot: give it a name and website, optionally a token symbol or address, and it joins the directory. It is saved in this browser only and can be removed again.
3. For COMMAND CENTER’s agent, select a strategy and SOL budget, then run the analysis.
4. Open Trade on a proposal and review the trade before approving it in your wallet.

COMMAND CENTER’s agent does not move funds on its own. A custom bot is your own shortlist — it links to that bot’s site and is not integrated, partnered with or reviewed by COMMAND CENTER. External platforms have their own terms and permissions; a listed token does not mean an agent is connected to your wallet here.

1. Write the goal and set a SOL budget, then run the planner.
2. Read each step’s tab link, estimated cost and the risk list before doing anything.
3. Open a step to carry it out — every Solana action still needs your wallet approval.

The planner returns a plan only. It never builds or signs a transaction, and cost estimates are not guarantees.

1. Paste a mint address and run the check.
2. Read contract details, mint and freeze authority, creator, liquidity, pools and links from live data.
3. If your Bundle basket holds the same token, it appears as linked assets.

Missing data shows --, never an estimate. A passport records what is verifiable; it is not a judgement of quality.

1. Create a policy: maximum SOL per trade, allowed tokens, a daily limit and whether sells are permitted.
2. Activate one policy; Terminal then checks every trade against it.
3. Trades outside the rules stop before your wallet is asked to sign.

Policies are saved in this browser only. The daily limit counts SOL spent on buys during the day, so it can trigger before a real loss occurs.

1. Publish an app with a name, link, category and short description.
2. Install or remove apps from the store list.
3. Use the web3 shortcuts to launch, mint a CA, check a token identity or open the API.

Published apps are saved in this browser only, so other visitors do not see them yet. COMMAND CENTER NFT minting is disabled until a real collection exists.