-
Notifications
You must be signed in to change notification settings - Fork 11
api.procedures.types.CreateNftCollectionParams
api/procedures/types.CreateNftCollectionParams
• collectionKeys: CollectionKeyInput
[]
The required metadata values each NFT in the collection will have
Note
Images — Most Polymesh networks (mainnet, testnet, etc.) have global metadata keys registered to help standardize displaying images
If imageUri
is specified as a collection key, then each token will need to be issued with an image URI.
• Optional
documents: AssetDocument
[]
Links to off chain documents related to the NftCollection
• Optional
fundingRound: string
A optional field that can be used to provide information about the funding state of the asset
• Optional
name: string
The collection name. defaults to ticker
• nftType: string
| BigNumber
Throws
if provided string that does not have a custom type
Throws
if provided a BigNumber that does not correspond to a custom type
• Optional
securityIdentifiers: SecurityIdentifier
[]
array of domestic or international alphanumeric security identifiers for the Asset (e.g. ISIN, CUSIP, FIGI)
• ticker: string
The primary identifier for the collection. The ticker must either be free, or the signer has appropriate permissions if reserved
Entities
- Account
- Asset
- Authorization Request
- Checkpoint
- Checkpoint Schedule
- Corporate Action
- Corporate Action Base
- Custom Permission Group
- Default Portfolio
- Default Trusted Claim Issuer
- Dividend Distribution
- Entity
- Identity
- Instruction
- Known Permission Group
- Metadata Entry
- Multi Sig Proposal
- Numbered Portfolio
- Offering
- Permission Group
- Portfolio
- Subsidies
- Subsidy
- Ticker Reservation
- Venue
- Authorizations
- Types