> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-script-new/introduction-to-basic-script-syntax.md).

# Introduction to Basic Script Syntax

Every time a Bitcoin transaction is verified on the network, a small program runs — one made up of logical instructions, data, and rules. This program is **Bitcoin Script**: the native scripting language that governs how coins are locked and unlocked in every transaction. Before you can write or read any Script, you need to understand its grammar — the rules that define what is allowed and how the evaluation engine processes each instruction.

This course introduces you to the foundational syntax of Bitcoin Script. You will learn how data is represented and handled, what rules govern how scripts are formed, and how the **stack-based evaluation model** processes instructions one step at a time. Think of this as learning the alphabet and grammar of a programming language before writing your first sentence.

{% embed url="<https://youtu.be/9rBxiOxewHk>" %}


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-script-new/introduction-to-basic-script-syntax.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.