> For the complete documentation index, see [llms.txt](https://docs.superteamde.fun/superteam-germany-guilds/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/security-and-best-practices.md).

# Security & Best Practices

Security and reliability references every Solana builder should review before shipping.

If you only read one section before shipping something public, read this one.

## Essential Reading

* [Program Security](https://solana.com/developers/courses/program-security)
* [Verified Builds](https://solana.com/developers/guides/advanced/verified-builds)
* [Anchor Verifiable Builds](https://www.anchor-lang.com/docs/references/verifiable-builds)
* [Fees](https://solana.com/docs/core/fees)
* [PDA Accounts](https://solana.com/docs/core/pda/pda-accounts)
* [CPIs with PDA signers](https://solana.com/docs/core/cpi/cpi-with-pda)

## Practical Advice

* do not treat a hackathon submission as an excuse to ignore security basics
* use the simplest possible architecture that still solves the problem
* understand signer checks, account ownership, and PDA behavior before mainnet thinking
* verify that your deployed code matches your source if the project continues after the hackathon

## For Teams

Before submitting:

* confirm judges can access your repo and any docs
* document what is onchain and what is offchain
* explain why you chose Solana-specific design decisions


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.superteamde.fun/superteam-germany-guilds/build-on-solana/security-and-best-practices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.