Smart Contracts
Last updated
Last updated
TezoTrooperz Smart Contracts are deployed on Tezos Blockchain. This is true for the minting of our NFTs, but also for the game mechanics centered around our Token: $REBL.
Thanks to our partner Completium, the Smart Contracts are written in Archetype, a high-level programming language conceived for developing on the Tezos Blockchain. As all Smart Contracts on Tezos, they are then compiled into Michelson after being deployed on the Blockchain.
Metadata of the NFTs are stored on IPFS, a well-known decentralized storage system. Each NFT is linked to a unique IPFS link, providing the metadata along with pictures.
Our Smart Contract structure is complex, and designed to involve and enhanced with time:
FA2: This smart contract respects the TZIP-12 token standard protocol. We use it to instantiate our 7000 trooperz non-fungible tokens and list the different owners. After the minting phase, we will use it to reveal metadata.
We decided to split the business logic and storage for our whitelist, allowing us to update our system later.
- Whitelist business logic: We use it to verify all information concerning the whitelist when someone tries to mint during a period.
- Whitelist storage: We use it to store all data concerning users and their minting permissions (admin/whitelisted/blacklisted).
TokenData: When a user tries to mint, we are verifying several conditions before allowing the actions: number of mints during the period by the user, if the limit is reached, if the balance is enough...
Minter: This contract contains all the logic for the mint action. It's corresponding with the other contracts during each action. It is also the place where we set the price of tokens during a specific period.