> For the complete documentation index, see [llms.txt](https://docs.bukprotocol.io/buk-protocol-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bukprotocol.io/buk-protocol-v2/buk-protocol-smart-contracts/buk-signature-verifier.md).

# BUK Signature verifier

## SignatureVerifier Contract

The `SignatureVerifier` contract is a Solidity smart contract designed to verify the signature of hashed messages using the ECDSA cryptographic algorithm. It provides a utility to ensure the authenticity of messages within the Buk Protocol.

### Overview

The contract is designed with the following key component:

* **Signature Verification**: Uses the ECDSA library from OpenZeppelin to verify the signature of hashed messages.

### Features

* **ECDSA Verification**: Provides a function to verify the signature of a hashed message using the ECDSA cryptographic algorithm.

### Functions

#### Public and External Functions:

* **generateAndVerify:** Generates a hash from the given parameters and verifies the signature of the hash using ECDSA.
* **verify**: Verifies the signature of a hashed message and returns the address of the signer.

### Interface: ISignatureVerifier

The contract also defines an interface `ISignatureVerifier` which outlines the expected structure and functions for the SignatureVerifier contract. The interface includes:

* **Functions**: Functions like **`verify`** and **`generateAndVerify`**

### License

This project is licensed under the MIT License.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bukprotocol.io/buk-protocol-v2/buk-protocol-smart-contracts/buk-signature-verifier.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.