> For the complete documentation index, see [llms.txt](https://circular-protocol.gitbook.io/hyper-code-ide-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circular-protocol.gitbook.io/hyper-code-ide-guide/lesson-2-smart-contracts/markdown.md).

# Introduction to Smart Contracts

Now that you’re familiar with the IDE, it’s time to create your first smart contract. In this tutorial, we’ll write, debug, and deploy the contract. You’ll need a development wallet, which can also serve as the owner’s wallet unless you’re working on external projects. Ensure it has enough balance for deployment and transactions.

On the Sandbox blockchain, you’ll receive free coins for testing. This tutorial focuses on understanding the project structure and debugging tools in Hyper Code IDE, laying the foundation for more advanced smart contract development in future guides.


---

# 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://circular-protocol.gitbook.io/hyper-code-ide-guide/lesson-2-smart-contracts/markdown.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.