# Nano Bot Overview

### Existing solutions (performance and cost)

Depending on the protocol, and how much users are willing to spend on gas, Nano can snipe at block 0 for launches.\
It can also buy via Clanker auctions, wait for fee decay on Clanker and Bankr before triggering swaps, and execute block-0 flows for Flaunch and Klik.

### Performance and premium positioning

Apart from what Flashblocks enables, one of Nano’s core differences is how it is built.\
Nano is built purely in Rust, a low-level systems language (like C/C++), which gives negligible processing overhead in critical paths.

In many cases, event decoding is measured in nanoseconds, and in heavier parallel paths in microseconds.\
Single-event decode paths are typically around 280 to 480 nanoseconds, while multi-event decode paths can range around 12 to 100 microseconds before execution.

Each user can run single-wallet or multi-wallet mode.\
Even with multiple users active, parallel task execution is isolated per user and per protocol, so one user’s in-flight triggers do not block others.

### Beta feedback

Beta testing happened during the February Molt Meta phase before the standalone version was created.\
Users who relied on Fargram’s built-in sniper during that period were able to produce profitable outcomes.

### Readiness for next-gen Base / Azul

Current infrastructure includes two high-end desktop systems and multiple nodes prepared to adapt to upcoming Base updates, including Flashblocks-aligned changes.

### UX direction

Telegram is the current primary surface and is being polished first.\
The web experience will follow immediately after the Telegram version reaches target quality.

<br>


---

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