🥥 Palm — Manual

🥥 Palm 🌴🇹🇭 is the Telegram workspace for domains, templates, logs, payouts and tools. Choose a platform, publish, connect a domain, and use PnL, LARP and Popup Studio from the bot. English and Russian.

This guide covers normal worker features only. The exact set of available sections can vary because individual capabilities may be enabled per account.

Quick start

  1. Open the bot with /start and choose your language.
  2. If you do not have access yet, press “Get access” and complete the application.
  3. After approval, press “Create flow”.
  4. Choose a platform, then a built-in or custom template.
  5. Set the visitor-facing site name and log destination. For key-extraction platforms, also choose split timing.
  6. Open the live link and test the page before sending traffic.
  7. Track events, funnel performance, and Launch Score from the flow card.

Access and application

On the first launch, the bot asks for a language and opens the guest screen. Press “Get access”, then complete three stages:

You can attach proof screenshots to the stages. Up to 5 images are accepted in total, and the traffic-source stage can be skipped when the current form allows it. Review your answers before submitting. The application then enters review and the decision arrives in the same chat.

You cannot submit a duplicate application while one is pending. If access is rejected or closed, the bot shows the current status and the next available action.

Home screen

After approval, the main sections become available:

If a button is missing or the bot says a feature is unavailable, the capability is restricted for the current account. Contact support if you believe it should be enabled.

Creating a flow

Creation is a guided sequence. The bot keeps the current wizard context, and /cancel safely stops an unfinished flow.

1. Platform

Choose one of the available platforms: Axiom, Polymarket, Padre, Fomo, or Phantom. The platform determines the built-in template catalog and the bookmark used in the published flow.

2. Template

Choose a built-in template from the market or press the custom-upload button. For a built-in template, first open its preview, check desktop and mobile appearance, and then lock your selection.

3. Site name

This is the name visitors see. Enter it manually or use the automatic option to derive it from the domain. You can rename the flow inside the bot later without changing its visitor-facing name.

4. Event destination

Choose your private bot chat or an available group. For a group, follow the add-bot flow and grant only the requested permissions. Make sure the correct group appears in the selector before continuing.

5. Split timing

This step is available only for Axiom, Padre, and Fomo, where a verified log contains the key required for a later split. Choose “Automatic split” when an eligible wallet log should start processing immediately, or “Delayed drain” when you want to start it manually. In Delayed drain mode, the operation is stored safely first and the bot shows a “Drain now” button. You can change the mode later in Flow settings.

Polymarket and Phantom perform a direct transfer during the client operation, so delaying a later drain is technically impossible. The bot skips this step and does not show a Delayed drain setting for those flows.

6. Domain and publication

Connect your own domain or launch immediately on a generated vercel.app address. For a custom domain, the bot shows the exact DNS records required for the selected setup.

Custom templates

Custom upload is available at the same step as the built-in templates. The bot accepts one Telegram document in .html or .zip format.

Single HTML file

Minimal button example:

<button class="bookmarklet">Open</button>

Static ZIP

Remote scripts, modules, and media are not loaded. Standard Google Fonts stylesheets from fonts.googleapis.com and their font files from fonts.gstatic.com are allowed; download every other external resource and include it in the archive.

JavaScript is checked separately. Dynamic code execution, network or communication APIs, cookies or browser storage access, navigation control, and other unsafe runtime capabilities are rejected. CSS is also validated: @import and executable constructs are not supported.

What happens after upload

The system validates the structure and content, binds the selected bookmark to .bookmarklet, adds only the required project data, and publishes the resulting static site. It does not inject a drag popup, click popup, or any other template interface. If you need those elements, implement them inside the template; existing template interactions are preserved. At rest the link has only the inert href="#"; the deployment adapter exposes the executable bookmarklet only during dragstart and restores the inert value after the drag. Ordinary clicks remain controlled by the template.

When validation fails, the bot shows an error category and, when available, the exact file, path, reference, and reason. Fix the reported location and upload the document again.

Domains and DNS

For a custom domain, follow the records shown by the bot. Depending on the domain, they can be:

DNS changes are not instant. Do not keep changing records while verification is in progress. Wait for propagation and use the retry action. You can continue with the generated address and attach the domain later from flow settings.

After publishing, open the URL, confirm that the page loads, and test the .bookmarklet button. Never send traffic to an unverified page.

Managing flows

The “Flows” section shows only your projects. Each card includes the URL, platform, template, event count, and quick actions.

Primary actions

Flow settings

You can:

Pausing notifications does not remove events. Activity is still recorded and remains available in logs.

Advanced actions

Deletion is irreversible. Export anything you may need first.

Logs and notifications

The bot can report consecutive stages of page activity and bookmark execution. Messages include only the safe information required to operate the flow.

Each flow can send events to your private chat or to a selected group. Account settings control general notifications, while an individual flow can be paused separately.

Financial and required system messages can arrive independently of normal notification settings. They prevent you from missing a payout, wallet issue, or important status change.

Delayed drain

Delayed drain is available only on Axiom, Padre, and Fomo flows because those platforms can provide the key required for a later split. It is not shown for direct-transfer Polymarket and Phantom flows.

When Delayed drain is enabled for a supported flow, receiving an eligible wallet log does not start the split automatically. The bot sends a separate “Delayed drain ready” card with two actions:

The same dashboard is available under “Account” → “Profit” → “Delayed drains”. It shows operations that are waiting, running, completed, or require review. Every pending operation has its own start button. If you open the dashboard from a group notification, the bot sends the complete list to your private chat so other flows are not exposed in the group.

Press the button once and wait for the final status. Repeated presses cannot create a second transfer: the bot reports that the operation is already running or processed. If an operation says “Needs review”, do not run it again; contact support and include the flow ID.

Turning Delayed drain off affects only new logs. Previously stored pending operations remain in the dashboard until you start them. Change the mode under “Flows” → the required flow → “Settings”.

Analytics

Four entry points are available:

Launch Score helps expose weak points before scaling. The funnel shows where activity drops. Detailed analytics is useful for comparing platforms, templates, and time periods.

If there is not enough data yet, keep running controlled test traffic and return later. An empty report does not automatically mean an error.

Profit and payouts

“Account” shows worker status, Telegram ID, total and monthly profit, active flows, your current share, and shortened payout addresses. “Profit” provides a history of recorded amounts and statuses.

Your share and feature thresholds are shown directly in the bot and may differ between accounts. Always use the current profile values rather than old messages or screenshots.

Payout wallets

You can save two default public addresses:

These defaults are applied to every new flow. A flow can override them in its own settings. The bot validates the address format; enter only a public address for the correct network.

If the required wallet is missing at settlement time, the share is secured for manual payout. Add a valid address and wait for processing. Avoid opening duplicate requests for the same operation.

Statuses

History can show pending, confirmed, paid, or rejected operations. The operation card always contains the authoritative status and available actions.

Referral program

The referral section contains your personal invite link. It shows the current percentage, minimum withdrawal, invited operator count, available balance, pending amount, and total balance.

To withdraw:

  1. Open “Account” → “Profit” → “Referrals”.
  2. Check the available balance and current minimum.
  3. Choose SOL or EVM withdrawal.
  4. Verify the address and confirm the request.
  5. Follow the result in withdrawal history.

The entire available balance is requested. While the request is being reviewed, that amount is shown separately. Decisions and status changes arrive in the bot.

Account settings

Notifications

Required and financial alerts cannot be muted completely.

Interface and time

You can change the language and timezone. Available timezone choices include UTC, UTC+3, Bangkok, and Singapore. The timezone affects display only, not the actual event time.

New-flow defaults

Choose the default visitor language and notification mode. These values apply to new projects; existing flows keep their individual settings.

Privacy and security

Sensitive previews can be hidden or shown, and login alerts can be enabled. Do not forward operational messages, protected-tool links, or financial details to other people.

Tools

The available tool set depends on account access. Open each tool from Tools in the bot once per session; after sign-in the address bar stays on a clean path.

PnL Studio

https://coconutopalm.com/pnl/ — protected web tool for PnL visuals. Use the bot button to start a session; bookmarks can point at this URL.

Popup Studio

https://coconutopalm.com/worker/ — popup settings for your domains. Does not alter popup interactions already implemented by an uploaded template unless you choose a corresponding action.

Balance Checker

Checks 1 to 3 public EVM or Solana addresses and reports token and protocol positions. Some providers can return partial results; the response indicates this when it happens.

LARP Tools

https://coconutopalm.com/larp/ — ZIPs for Axiom, Polymarket, Fomo. The portal includes screenshot examples (Fomo profile, token page, Wallet Larp panel).

On-site panel: Ctrl+G on axiom.trade, polymarket.com, and fomo.family (no floating FAB). In Telegram, an example album is sent after 👻 Fake Phantom.

Fomo: Ctrl+G → whale handle → Save → visit /profile/TheirHandle once for cache → reload your profile.

Fake Phantom (demo wallet)

Open Access catalog → iPhone bookmarks + Extension Methods → Fake Phantom, or tap 👻 Fake Phantom under protected tools. The bot sends step-by-step Phantom import instructions for the shared demo key (separate profile, training and screenshots only — no real funds).

Template Market and rates

The market lets you preview built-in templates by platform. The overview also provides current SOL and ETH rates. When a live source is temporarily unavailable, the bot can show a verified cached value.

Support

Press “Support” or use /support. A useful request includes:

A request can contain text, photos, video, documents, or audio; one album supports up to 10 attachments. You can have up to 5 open tickets, and history keeps up to 500 records. From a ticket you can reply, view attachments, close it, or reopen it. Support replies arrive as bot notifications.

Never send seed phrases, private keys, passwords, or two-factor authentication codes.

Worker commands

All primary operations are also available through buttons. If a command is unavailable for your account, the bot explains the restriction or next step.

Troubleshooting

A feature is unavailable

Confirm that your application is approved. If the account is active but a button is missing, the capability may be disabled or require the displayed profit level. Check the section screen and contact support when needed.

The domain does not connect

Compare every NS, A, or CNAME record with the bot instructions. Remove conflicting records, wait for DNS propagation, and retry verification. Use the generated address until the custom domain is ready.

No events arrive

Open the live URL yourself, verify that the page loads, check the destination group, and confirm that notifications are not paused. Run one controlled test. If the event is present in logs but there was no alert, review notification settings.

A template is rejected

Read “Validation details” in the bot: it identifies the file, path or reference, and reason. For a single HTML file, remove local dependencies. For ZIP, verify the root, index.html, relative paths, supported file types, and a rendered .bookmarklet control.

A payout address is invalid

Check the network and paste the complete public address without spaces. A SOL address cannot be used as an EVM address, or vice versa.

A protected link does not open

Return to the bot and open the tool again. These links are short-lived and intended for the current user only.

If the issue remains, submit one detailed support request with reproduction information.

Important rules

Updated: September 20, 2026.