cairo-erc721
Generate ERC-721 compliant non-fungible token contracts with customizable features like burnable, pausable, and mintable options. Returns contract code in Markdown format without saving to disk.
Instructions
Make a non-fungible token per the ERC-721 standard.
Returns the source code of the generated contract, formatted in a Markdown code block. Does not write to disk.
Input Schema
Name | Required | Description | Default |
---|---|---|---|
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. | |
appName | No | Required when votes is enabled, for hashing and signing typed structured data. Name for domain separator implementing SNIP12Metadata trait. Prevents two applications from producing the same hash. | |
appVersion | No | Required when votes is enabled, for hashing and signing typed structured data. Version for domain separator implementing SNIP12Metadata trait. Prevents two versions of the same application from producing the same hash. | |
baseUri | No | A base uri for the non-fungible token. | |
burnable | No | Whether token holders will be able to destroy their tokens | |
enumerable | No | Whether to allow on-chain enumeration of all tokens or those owned by an account. Increases gas cost of transfers. | |
info | No | Metadata about the contract and author | |
mintable | No | Whether privileged accounts will be able to create more supply or emit more tokens | |
name | Yes | The name of the contract | |
pausable | No | Whether privileged accounts will be able to pause specifically marked functionality. Useful for emergency response. | |
royaltyInfo | No | Provides information for how much royalty is owed and to whom, based on a sale price. Follows ERC-2981 standard. | |
symbol | Yes | The short symbol for the token | |
upgradeable | No | Whether the smart contract is upgradeable. | |
votes | No | Whether to keep track of individual units for voting in on-chain governance. Voting durations can be expressed as block numbers or timestamps. |