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

# Legacy - Digital Signatures

{% embed url="<https://youtu.be/4JlmLePwlp0>" %}

### Introduction

Overall, there are three foundational concepts that, if understood well, can make the initial learning journey for the BSV blockchain (BSV) much easier. While the two other concepts are Hash Functions and Merkle Trees, the focus of this course is to cover the third concept - Digital Signatures.

As this is a beginner-level course, it assumes no knowledge of BSV. There are many well-proven Digital Signature Schemes such as RSA (based upon the name of its inventors Rivest-Shamir-Addlemen), Digital Standard Signature, ECDSA (Elliptic Curve Digital Signature Algorithm), used by enterprise products. For the scope of this course, our focus will only be on ECDSA as used in BSV. In order to build a solid conceptual understanding, the course will progress in the following order:\
\
Chapter 1 - What are Digital Signatures?\
Chapter 2 - ECDSA Pre-requisites\
Chapter 3 - ECDSA\
Chapter 4 - Bitcoin and Digital Signatures<br>


---

# 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/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.