> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/cookbook/clarity/address-utilities/create-a-random-burn-address.md).

# Create a random burn address

{% code fullWidth="false" expandable="true" %}

```clarity
(define-read-only (generate-burn-address (entropy (string-ascii 40)))
  (let (
    ;; Hash the entropy to create address bytes
    (hash-bytes (hash160 (unwrap-panic (to-consensus-buff? entropy))))
    ;; Use version byte for current network
    (version-byte (if is-in-mainnet 0x16 0x1a))
  )
    ;; Construct a valid principal that no one controls
    (principal-construct? version-byte hash-bytes)
  )
)

;; Example: Generate unique burn address
(generate-burn-address "BURN-2024-01-15-PROJECT-XYZ")
;; Returns: (ok SP1FJPSG7V4QMA7D4XVPZ3B2HQ8GY3EK8GC0NGNT3)
```

{% endcode %}

### Description

Generate burn addresses for permanently removing tokens from circulation

### Use Cases

* Token burning mechanisms
* Proof-of-burn implementations
* Creating unspendable addresses for protocol fees
* Deflationary token economics

### Key Concepts

* **No private key** - Generated from arbitrary data, not a key pair
* **Verifiable** - Anyone can verify tokens sent to these addresses
* **Unique** - Different entropy creates different addresses
* **Permanent** - Funds sent are irretrievably lost


---

# 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://docs.stacks.co/cookbook/clarity/address-utilities/create-a-random-burn-address.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.