# Doppler

#### UI controls

* Protocol toggle - Enable/Disable
* Set gwei
* Auto-sell enable/disable + delay prompt
* Launch isolation toggle for trusted hooks. If enabled, launches are filtered by trusted hook/initializer allowlists (support for user-set hooks can be added later).
* Fee/tax decay wait toggle - if on, waits for fee decay before sniping; if off, snipes after the launch tx block (block+1 behavior).

#### Triggering logic (how it works)

The Doppler triggering system is based on target matching + execution preferences:

* tx sender address matching against user targets
* lock beneficiary matching (when available)
* user-defined gwei and buy amount settings
* fee decay wait behavior
* protocol enable state per user

When matched, it evaluates launch filters, builds the pool key, and routes buys to matched users only.

#### Launch filtering and routing behavior

* If launch isolation is enabled, launches are only accepted when hook or initializer is trusted.
* If fee-decay waiting is enabled and tax schedule data is present, the bot waits until decay end before buying.
* If fee-decay waiting is disabled, it still avoids block 0 in this path by waiting until the next block after launch tx.
* For NOICE-paired launches, launchpad presence is required (*this is being reworked*).
* Auto-sell uses user preferences (enabled/disabled + delay) after successful buy submission.

#### Bankr integration (source of truth + 4 triggers)

Bankr trigger modes use Bankr API launch metadata (deployer + fee recipient, wallet + X handle) as source of truth for target matching.

Supported trigger modes:

* Any trigger - triggers if target matches deployer OR fee recipient.
* Self-deploy trigger - triggers only when deployer AND fee recipient are the same actor, and target matches that actor.
* Deployer-only trigger - triggers when target matches deployer in non-self-deploy launches.
* Fee-only trigger - triggers when target matches fee recipient in non-self-deploy launches.

Notes:

* Wallet and Twitter handle targets are both considered.
* In Bankr launches, beneficiary and Bankr trigger matches are merged into final matched users.
* Final execution is user-scoped: only matched, protocol-enabled users are included in the buy batch.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nano-5.gitbook.io/nano-docs/documentation/getting-started/publish-your-docs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.