DeGuild-MG-CS-Token-contracts

There are 3 main parts

1. DeGuild contract
2. Magic shop contract
3. Certificate manager contract

Together, these contracts support each other and be independent at the same time.

Instructions and CLI

Our setup API and testing network

    module.exports = {
    solidity: '0.8.4',
    networks: {
        rinkeby: {
        url: `https://eth-rinkeby.alchemyapi.io/v2/${ALCHEMY_API_KEY}`,
        accounts: [`0x${RINKEBY_PRIVATE_KEY}`],
        },
    },
    etherscan: {
        // Your API key for Etherscan
        // Obtain one at https://etherscan.io/
        apiKey: ETHERSCAN_API_KEY,
    },
    };

Our .env file setup

    RINKEBY_PRIVATE_KEY=6
    ALCHEMY_API_KEY=X
    ETHERSCAN_API_KEY=W

To compile the code and retrieve the bytecodes and ABIs

    yarn hardhat compile

To deploy contract

    yarn hardhat run scripts/deployX.js --network rinkeby

To verify

    yarn hardhat verify --contract contracts/MagicShop/MagicShop.sol:MagicShop --network rinkeby 0xFAb4628f67B89bccbcd913E1c946F91f4ABF4034

We have shortcuts for contract deployments and verifications

    yarn deployD - Deploy DeGuildPlus Contract
    yarn deployM - Deploy MagicShopPlus Contract
    yarn deployC - Deploy CertificateManager Contract
    yarn verifyD {contract address} - Verify address with DeGuildPlus
    yarn verifyM {contract address} - Verify address with MagicShop
    yarn verifyC {contract address} - Verify address with CertificateManager