Badge

Introduction

A badge is not a distinct engine type — it is the convention of using a resource (typically non-fungible) as an authorization token rather than a value-bearing asset. Holding the badge in a vault, or presenting a proof of it during a transaction, satisfies access rules 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)
• Radix Docs: Badges