> 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/miner-identification-and-digital-signatures.md).
# Miner Identification and Digital Signatures
When a **transaction** is created, it is sent to the **mining nodes** on the network. These nodes check whether the transaction is valid and then compete to include it in a new block. Mining means solving a **complex computational puzzle**, which requires significant resources.
A **block** is simply a group of validated transactions that are timestamped together. Once a node finds the solution, it shares the block with the rest of the network.
***
### How Consensus Works
* Multiple nodes (also called **miners**) compete to mine each block.
* They are highly connected to reduce communication delays.
* When a node finds the solution, it broadcasts its block.
* Other nodes verify the **Proof of Work** and the transactions inside.
If the block is valid, it is added to the blockchain. Other miners then confirm acceptance by building new blocks on top of it, linking them through **hash-based dependencies**.
This process is known as the **consensus mechanism**. It combines competition with cooperation.
***
### Miner Rewards
The winning miner includes a special transaction called the **coinbase transaction**. This allows the miner to pay themselves the reward.
* **Block rewards**: Newly created coins.
* **Transaction fees**: Paid by users who sent transactions.
***
### Identifying Miners
Because blocks are validated and confirmed publicly, **miners can be identified**. Currently, there are two main ways:
1. **Coinbase identity data** – Miners may add identity information to their coinbase transaction. However, this can be spoofed and isn’t always reliable.
2. **MinerID protocol** – A cryptographic system that provides miners with a **verifiable digital identity**.
***
### The MinerID Protocol
The **MinerID protocol** gives each miner a **unique cryptographic identifier**. It uses **ECDSA (secp256k1)**, the same algorithm used for Bitcoin’s digital signatures.
* A miner generates a **public/private key pair**.
* The **public key** acts as the miner’s identifier.
* The **private key** is used to sign metadata in the coinbase transaction output of blocks they mine.
This allows the network to:
* Verify that a block really came from the miner claiming it.
* Prevent impersonation and malicious attacks.
* Strengthen overall **network security** through **message authentication**.
For more details, see the [MinerID documentation](https://github.com/bitcoin-sv-specs/brfc-minerid).
***
### FYI
Teranode will have new ways for miners to be identified as well.
***
### Key Takeaway
The **MinerID protocol** ensures that miners can be cryptographically verified, not just identified by untrusted text in a transaction. By combining **digital signatures** with the mining process, the BSV blockchain achieves both **security** and **accountability**.
---
# 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/miner-identification-and-digital-signatures.md?ask=&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.
