---
title: "Badge"
path: "/contents/tech/core-concepts/badges"
version: "1.0.0"
author: "Hydrate"
createdAt: "2026-05-03T09:53:56.225Z"
updatedAt: "2026-05-03T09:53:56.225Z"
---

# Badge

<Infobox>
| Core Primitive |
| Core Primitive |
| `scrypto, radix-engine` |
| [radixdlt-scrypto](https://github.com/radixdlt/radixdlt-scrypto) |
</Infobox>

## Introduction

A **badge** is not a distinct engine type — it is the convention of using a [resource](/contents/tech/core-concepts/asset-oriented-programming) (typically non-fungible) as an authorization token rather than a value-bearing asset. Holding the badge in a [vault](/contents/tech/core-concepts/buckets-proofs-and-vaults), or presenting a [proof](/contents/tech/core-concepts/buckets-proofs-and-vaults) of it during a transaction, satisfies [access rules](/contents/tech/core-concepts/access-rules-and-auth-zones) that gate privileged operations — minting more of a resource, upgrading a component, withdrawing from treasury vaults. Because badges are themselves resources, they cannot be forged, duplicated, or silently transferred.

## External Links

- [Authorization patterns (scrypto)](https://github.com/radixdlt/radixdlt-scrypto/tree/main/scrypto/src/component)

- [Radix Docs: Badges](https://docs.radixdlt.com/docs/badges)