> For the complete documentation index, see [llms.txt](https://docs.vibeswap.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vibeswap.net/product/vibe.md).

# Vibe

Vibe is the game section of Vibeswap.

The first game is Vibe Blocks, a 2048-style ranked game with onchain leaderboard tracking.

## Vibe Blocks

Players start a ranked run by paying the game entry fee in zkLTC. The game is played in the browser, and the final score is submitted onchain when the run ends.

## Leaderboards

Vibe Blocks currently has two leaderboard types:

* Best Score: the highest single run by wallet.
* Total Score: the accumulated score across ranked runs.

This structure allows both high-skill single runs and consistent seasonal activity to matter.

## Future Games

Future Vibe games may include risk/reward and online mechanics, including a Minesweeper-style game mode with zkLTC rewards for successful runs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.vibeswap.net/product/vibe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.