> For the complete documentation index, see [llms.txt](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-63-balance-check-using.md).

# Tutorial 63: Balance Check Using ==

{% hint style="info" %}
[**Book an audit with Zokyo**](https://www.zokyo.io/)
{% endhint %}

In Solidity smart contracts, performing checks on token balances is a common practice to ensure that transactions proceed as expected. However, developers often rely on exact balance comparisons using the `==` operator, which can introduce a significant vulnerability. This approach can be exploited by external actors who send tokens to the contract, leading to unexpected balance changes. When the contract checks for an exact balance match, it may fail due to these additional tokens, potentially causing a **Denial of Service (DoS)** situation where the contract becomes unusable.

This tutorial will explore how this vulnerability arises, its impact on smart contracts, and how developers can mitigate the risks associated with exact balance comparisons. By understanding these vulnerabilities, you can implement more secure balance-checking mechanisms to prevent attackers from locking critical contract functionality.


---

# 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://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-63-balance-check-using.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.