SMART CONTRACTS
← Contract catalogPrivilegeNFT
Represent individually identified assets or access credentials.
Role and use
Use a distinct tokenId for each equipment identity or individual membership.
Integration considerationsDefine metadata storage, transfer rules and expiry or ownership changes. Match SDK operations to the deployed implementation.
Key SDK operations
These operations are exposed by PrivilegeNFTHelper in @hazbase/kit@0.9.0. The signatures below are type definitions; see the SDK reference for parameter structures and the complete interface.
typescript
import { PrivilegeNFTHelper } from '@hazbase/kit';mint
typescript
async mint(
to: Address,
id: bigint | number,
uri: string,
tier: number,
exp: bigint | number,
rType: bigint | number
): Promise<TransactionReceipt>ownerOf
typescript
async ownerOf(id: bigint | number): Promise<Address>tokenURI
typescript
async tokenURI(id: bigint | number): Promise<string>safeTransferFrom
typescript
async safeTransferFrom(
from: Address,
to: Address,
tokenId: bigint | number,
data: BytesLike = "0x"
): Promise<TransactionReceipt>Related contracts
Put it into practice
Physical assets & inventory
See the data model, processing sequence and SDK code for an application-level implementation.
Read the implementation patternSpecification and source
The Solidity source is pinned to the revision below. Match it with the SDK version and your network’s implementation address and ABI.
privilege-nft/contracts/PrivilegeNFT.solSource revision: b53a5b5