Interface: Drop
Information related to a specific drop.
Properties
config
Optional config: DropConfig
All drops regardless of their type can have a suite of configurations such as how many uses each key has or how often a key can be used.
Defined in
depositPerUse
depositPerUse: string
How much $yoctoNEAR will be transferred anytime a key is used that is part of this drop.
Defined in
dropId
dropId: string
Drop ID for this specific drop.
Defined in
fc
Optional fc: FCData
For Function-Call drops, important information needs to be stored such as which methods, the attached deposit, args etc.
Defined in
ft
Optional ft: FTData
For Fungible Token drops, important information such as the amount of tokens to transfer, or contract need to be stored.
Defined in
metadata
Optional metadata: string
Any extra information about the drop can be stored as metadata. This is up to the drop creator and can be stringified JSON, or any other string.
Defined in
nextKeyId
nextKeyId: number
What is the next unique ID that will be given to the next access key added to this drop.
Defined in
nft
Optional nft: NFTData
For NFT drops, important information such as the token IDs, or contract need to be stored.
Defined in
ownerId
ownerId: string
Which account created this drop.
Defined in
registeredUses
registeredUses: number
How many key uses are registered for this drop? This is only applicable to simple drops with lazy registrations, FT drops, and NFT drops.
Defined in
requiredGas
requiredGas: string
In order to use an access key that's part of this drop, how much Gas needs to be attached to the call?
Defined in
simple
Optional simple: SimpleData
For simple drops, there are specific, optional configurations.