Stellar Non-Fungible
stellar-non-fungibleGenerate a Stellar non-fungible token contract per SEP-50, with configurable features like minting, burning, and access control. Receive the source code as Markdown.
Instructions
Make a non-fungible token per the Non-Fungible Token Standard, compatible with SEP-50, similar to ERC-721.
Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| info | No | Metadata about the contract and author | |
| name | Yes | The name of the contract | |
| votes | No | Whether to enable vote checkpoints and delegation for governance. | |
| access | No | The type of access control to provision. Ownable is a simple mechanism with a single account authorized for all privileged actions. Roles is a flexible mechanism with a separate role for each privileged action. A role can have many authorized accounts. | |
| symbol | Yes | The short symbol for the token | |
| burnable | No | Whether token holders will be able to destroy their tokens | |
| mintable | No | Whether privileged accounts will be able to create more supply or emit more tokens | |
| pausable | No | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. | |
| tokenUri | No | The metadata URI returned by the token contract for every NFT. | |
| enumerable | No | Whether the NFTs are enumerable (can be iterated over). | |
| sequential | No | Whether the IDs of the minted NFTs will be sequential. | |
| consecutive | No | To batch mint NFTs instead of minting them individually (sequential minting is mandatory). | |
| upgradeable | No | Whether the contract can be upgraded. | |
| explicitImplementations | No | Whether the contract should use explicit trait implementations instead of using the default ones provided by the library. |