> For the complete documentation index, see [llms.txt](https://suzuna.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suzuna.gitbook.io/whitepaper/the-problem.md). # The Problem ### Understanding a wallet should not require reading the blockchain manually. Every BNB Chain wallet can accumulate a large amount of activity over time. Transactions, token transfers, contract interactions, and balance changes create a detailed on-chain record. The challenge is not access to the data. The challenge is understanding it. #### Raw Data Requires Interpretation Blockchain explorers provide the underlying transaction records, but users still need to determine what each transaction means, which assets moved, which contracts were involved, and how different activities relate to one another. For users without technical blockchain knowledge, this can make even simple questions difficult to answer. #### Activity Is Spread Across Transactions A wallet's recent behavior is rarely represented by a single transaction. Understanding what happened may require looking across multiple transactions, token transfers, contract interactions, and balance changes. Manually connecting these events can be time-consuming. #### Blockchain Data Is Technical Wallet addresses, transaction hashes, contract addresses, token movements, and on-chain events are useful for verification, but they are not naturally written for human conversation. Users often need an explanation of the activity rather than another list of raw records. #### The User Experience Gap The blockchain already provides the underlying information. What is missing is a simpler way to interact with that information. SUZUNA addresses this gap by allowing users to ask natural-language questions about a BNB Chain wallet and receive an AI-generated explanation based on relevant on-chain activity. The goal is not to replace blockchain data. **The goal is to make that data easier to understand.** --- # 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://suzuna.gitbook.io/whitepaper/the-problem.md?ask=&goal= ``` `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.