Optional
approachWhether the claim is expected to be automatically triggered by someone (not the user).
Optional
assignAlgorithm to determine the claim number order. Blank is just incrementing claim numbers.
Optional
balancesThe balances to set for the claim. Only used for claims for collections that have off-chain indexed balances and are assigning balances based on the claim.
Optional
categoriesThe categories of the claim
Unique claim ID.
Optional
collectionCollection ID that the claim is for (if applicable).
Optional
createdThe original creator of the claim
Optional
estimatedEstimated cost for the claim.
Optional
estimatedEstimated time to satisfy the claim's requirements.
Optional
lastLast updated timestamp for the claim.
Optional
listAddress list ID that the claim is for (if applicable).
Optional
manualIf manual distribution is enabled, we do not handle any distribution of claim codes. We leave that up to the claim creator.
Optional
metadataMetadata for the claim.
Claim plugins. These are the criteria that must pass for a user to claim the badge.
Optional
rewardsRewards for the claim.
Optional
satisfyCustom satisfaction logic
Optional
seedSeed code for the claim.
Optional
showIf true, the claim will be shown in search results
Optional
siwbbIs intended to be used for Sign In with BitBadges.
Optional
trackerThe tracker details for the claim.
The version of the claim.
Deep copies the object and returns a new instance.
Converts the object to a different NumberType equivalent.
Optional
options: ConvertOptionsCompares this object's fields to another object's fields for equality. Equality is determined by comparing the JSON representations of the objects.
If normalizeNumberTypes
is true, then all number types will be compared as strings (i.e. "1n" === "1" === 1). Else, they will be compared as their native types (i.e. 1n !== 1 !== "1").
Optional
normalizeNumberTypes: boolean
Whether the claim fetch includes private params