> 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/elliptic-curve-digital-signature-algorithm-ecdsa.md).

# Elliptic Curve Digital Signature Algorithm (ECDSA)

This course introduces the **Elliptic Curve Digital Signature Algorithm (ECDSA)**, the signature scheme behind Bitcoin and many secure systems.

You will explore:

* The foundations of elliptic curve cryptography (ECC) and its key parameters (a, b, p, G, q)
* The three main steps of ECDSA: key generation, signing, and verification
* Why **ephemeral key randomness** is critical for security, and how deterministic keys (RFC 6979) strengthen reliability
* The **secp256k1 curve** used in Bitcoin and signature formats that balance efficiency with authentication

By the end of the course, learners will:

* Understand how ECDSA works in practice and why it is secure
* Recognize its role as the backbone of trust in blockchain and digital communication

This course is beginner-friendly and designed to give you a clear, step-by-step understanding of one of the most important cryptographic algorithms in use today.


---

# 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/elliptic-curve-digital-signature-algorithm-ecdsa.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.