# Clanker

### Clanker V4 (high-level trigger model)

Clanker uses a two-path trigger model to avoid false negatives on official deploy flows:

* Standard path: trigger off launch sender when sender is a user target.
* Official deployer path: if sender is an official/trusted Clanker deployer, trigger authority shifts to the  token admin identity from the launch event.

This keeps targeting accurate for both direct creator launches and official deployer-mediated launches.

Then, depending on user settings:

* bot can wait for auction fee decay (with optional buffer), or
* target auction timing directly.

Auto-sell is applied per user profile after successful buy.

Auction behavior:

* If auction decay wait is enabled, bot waits auction decay time (+ buffer, if set) before buy.
* If decay wait is disabled, bot targets auction block timing and submits with auction round data.
* If auction attempts fail, fallback path can wait decay and retry without auction hook data.

Auto-sell:

* Per-user Clanker optional auto-sell settings are applied after successful buy.
* Delay is configurable.


---

# 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/clanker.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.