> 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-primitives-digital-signatures/bsv-and-digital-signatures.md).

# BSV and Digital Signatures

This course introduces how the **BSV blockchain (BSV)** uses digital signatures, powered by the **Elliptic Curve Digital Signature Algorithm (ECDSA)** on the **secp256k1 curve**, to secure its network.

You will explore:

* How digital signatures protect **BSV transactions**, proving ownership and authorization.
* The role of **signed messages**, enabling users to prove authorship outside of the blockchain.
* How **miner identification** works as an optional way for miners to sign and verify their contributions.

By the end of the course, learners will:

* Understand how digital signatures function within the BSV system.
* Recognize the three key contexts where they are applied: transactions, messages, and miner identities.
* Appreciate why digital signatures are essential for **authenticity, integrity, and trust** in Bitcoin SV.

This course is designed for beginners. No prior knowledge of BSV or cryptography is required — only an interest in learning how trust is established and maintained in the BSV network.


---

# 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-primitives-digital-signatures/bsv-and-digital-signatures.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.