Interface: DropConfig
Configurable options for any drop regardless of type.
Properties
dropRoot
Optional dropRoot: string
Override the global root account that all created sub-accounts will have (currently near or testnet). This allows users to drops that have a custom root.
For example, Fayyr could specify a root of fayyr.near By which all sub-accounts will then be ACCOUNT.fayyr.near.
It's important to note that this root account MUST have a smart contract deployed that has a method create_account.
Defined in
sale
Optional sale: PublicSaleConfig
Any information related to primary market sales for access keys added to this drop.
Defined in
time
Optional time: TimeConfig
Any information related to time-based configurations such as a starting date for keys etc.
Defined in
usage
Optional usage: UsageConfig
Any information related to how access keys are used such as which methods they can call or whether an empty drop should be automatically deleted etc.
Defined in
usesPerKey
Optional usesPerKey: number
How many uses can each key have before it's deleted. If this isn't specified, it defaults to 1 use per key.