04 Auth
4.3 Summary
Fungible and non-fungible badges offer distinct advantages. Fungible badges are suitable for general authentication requirements where the specific badge is less important than whether someone possesses the badge. In contrast, non-fungible badges provide greater flexibility and granularity. For instance, if you need someone to have a specific badge for a particular authorized action, you can issue a non-fungible badge that specifies a unique
It's essential to understand that while badges are used for authentication, proving ownership of a badge should involve sending a "proof" of the badge rather than the badge itself. A proof is a temporary representation of the badge that confirms ownership without relinquishing the actual badge. This proof can then be used to authorize certain actions and is effectively invalidated at the end of the transaction, making it unusable for further purposes.
NonFungibleGlobalId. This not only requires the general non-fungible resource but also the specific individual non-fungible unit.It's essential to understand that while badges are used for authentication, proving ownership of a badge should involve sending a "proof" of the badge rather than the badge itself. A proof is a temporary representation of the badge that confirms ownership without relinquishing the actual badge. This proof can then be used to authorize certain actions and is effectively invalidated at the end of the transaction, making it unusable for further purposes.