> For the complete documentation index, see [llms.txt](https://0xkowloon.gitbook.io/anchor-for-evm-developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xkowloon.gitbook.io/anchor-for-evm-developers/anchor-for-evm-developers.md).

# Anchor for EVM Developers

I recently started learning how to write Solana programs and much to my surprise it is very different from writing smart contracts on EVM. There are many Solana tutorials out there but nothing that quickly bridges an EVM developer's knowledge to Solana,  so I created this guide.

This guide is inspired by [Solidity by Example](https://solidity-by-example.org/). It is light on texts and heavy on code. Experienced EVM developers should be able to just read the code and understand what's going on.

This is a WIP, feel free to DM me on Twitter @0xkowloon if I should be adding anything!


---

# 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://0xkowloon.gitbook.io/anchor-for-evm-developers/anchor-for-evm-developers.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.
