OptionalapproachWhether the claim is expected to be automatically triggered by someone (not the user).
OptionalassignAlgorithm to determine the claim number order. Blank is just incrementing claim numbers.
OptionalbalancesThe 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.
OptionalcategoriesThe categories of the claim
Unique claim ID.
OptionalcollectionCollection ID that the claim is for (if applicable).
OptionalcreatedThe original creator of the claim
OptionalestimatedEstimated cost for the claim.
OptionalestimatedEstimated time to satisfy the claim's requirements.
OptionallastLast updated timestamp for the claim.
OptionallistAddress list ID that the claim is for (if applicable).
OptionalmanualIf manual distribution is enabled, we do not handle any distribution of claim codes. We leave that up to the claim creator.
OptionalmetadataMetadata for the claim.
Claim plugins. These are the criteria that must pass for a user to claim the badge.
OptionalrewardsRewards for the claim.
OptionalsatisfyCustom satisfaction logic
OptionalseedSeed code for the claim.
OptionalshowIf true, the claim will be shown in search results
OptionalsiwbbIs intended to be used for Sign In with BitBadges.
OptionaltrackerThe 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.
Compares 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").
OptionalnormalizeNumberTypes: boolean
Whether the claim fetch includes private params