feat: add 3/4 and 4/4 of checkpoint question sets

Author: elPiablo

src/pages/lessons/projects/6.mdx

@@ -510,7 +510,7 @@ Let's break down our changes in the code:
 
 - Added an `import` before our contract definition
 - Inherited `AccessControl` in our contract definition
-- Created a `bytes32 public constant` variable for the minter role
+- Created a `bytes32 public constant` variable for the minter role. The irreversible `keccak256` hash ensures security and prevents unintended changes to the role. As a fixed-size of 32 bytes, it is efficiently storable, and will incur minimal gas consumption.
 - Inside our `constructor`:
   - Granted the `DEFAULT_ADMIN_ROLE` to the contract deployer to be able to grant
     roles to others. Our contract inherits this by default from Access Control as the starting point for all admin roles.
@@ -621,7 +621,7 @@ to ask our community for help by explaining your error, the console output and
 your configuration (OS, version, Foundry and Solidity version, etc.)
 
 
-{/* <SideDrawer
+<SideDrawer
   buttonText="Checkpoint Questions"
   title="Defining permissions for use of our contract"
 >
@@ -630,7 +630,7 @@ your configuration (OS, version, Foundry and Solidity version, etc.)
   <Question question="lesson-6/4-define-roles/Q3" />
   <Question question="lesson-6/4-define-roles/Q4" />
   <Question question="lesson-6/4-define-roles/Q5" />
-</SideDrawer> */}
+</SideDrawer>
 
 ### Register your house in the Real Estate Register
 
@@ -802,7 +802,7 @@ the tool tells us the address of the deployed contract:
 `0xec870005029ED5595F146f6AAAe699b442065b72`.
 
 
-{/* <SideDrawer
+<SideDrawer
   buttonText="Checkpoint Questions"
   title="Deploying with Foundry"
 >
@@ -811,7 +811,7 @@ the tool tells us the address of the deployed contract:
   <Question question="lesson-6/5-deployment/Q3" />
   <Question question="lesson-6/5-deployment/Q4" />
   <Question question="lesson-6/5-deployment/Q5" />
-</SideDrawer> */}
+</SideDrawer>
 
 ## Querying the Block Explorer
 

src/utils/questions/lesson-6/4-define-roles/Q1.json

@@ -0,0 +1,12 @@
+{
+  "question": "We created an `address` variable to store our `MINTER_ROLE`.",
+  "options": [
+    {
+      "answer": "False",
+      "correct": true
+    },
+    {
+      "answer": "True"
+    }
+  ]
+}

src/utils/questions/lesson-6/4-define-roles/Q2.json

@@ -0,0 +1,18 @@
+{
+  "question": "In the constructor, which role is granted to give the contract deployer operational control?",
+  "options": [
+    {
+      "answer": "`DEPLOYER_ROLE`"
+    },
+    {
+      "answer": "`DEFAULT_ADMIN_ROLE`",
+      "correct": true
+    },
+    {
+      "answer": "`TOKEN_ADMIN_ROLE`"
+    },
+    {
+      "answer": "`CONTRACT_OWNER_ADMIN`"
+    }
+  ]
+}

src/utils/questions/lesson-6/4-define-roles/Q3.json

@@ -0,0 +1,18 @@
+{
+  "question": "What happens if an address without the `MINTER_ROLE` tries to call the `mint()` function?",
+  "options": [
+    {
+      "answer": "The function will execute without any issue"
+    },
+    {
+      "answer": "The contract will self-destruct"
+    },
+    {
+      "answer": "The contract will mint tokens to that address"
+    },
+    {
+      "answer": "The transaction will revert, and the function will not execute",
+      "correct": true
+    }
+  ]
+}

src/utils/questions/lesson-6/4-define-roles/Q4.json

@@ -0,0 +1,18 @@
+{
+  "question": "Why do we use the keccak256 hash for the MINTER_ROLE variable?",
+  "options": [
+    {
+      "answer": "To fetch and display gas consumption for the role"
+    },
+    {
+      "answer": "To fetch the total supply of tokens minted"
+    },
+    {
+      "answer": " To prevent unintended changes to the role",
+      "correct": true
+    },
+    {
+      "answer": "To allow burning tokens"
+    }
+  ]
+}

src/utils/questions/lesson-6/4-define-roles/Q5.json

@@ -0,0 +1,12 @@
+{
+  "question": "After running `forge build` on our coded contract for the first time, the compiler will compile:",
+  "options": [
+    {
+      "answer": "MyToken.sol"
+    },
+    {
+      "answer": "multiple files",
+      "correct": true
+    }
+  ]
+}

src/utils/questions/lesson-6/5-deployment/Q1.json

@@ -0,0 +1,15 @@
+{
+  "question": "What is the purpose of the `cast` command?",
+  "options": [
+    {
+      "answer": "To deploy the contract"
+    },
+    {
+      "answer": "To audition for a web3 AMA"
+    },
+    {
+      "answer": "To convert values to wei",
+      "correct": true
+    }
+  ]
+}

src/utils/questions/lesson-6/5-deployment/Q2.json

@@ -0,0 +1,15 @@
+{
+  "question": "Where can you find the address of the deployed contract after deployment?",
+  "options": [
+    {
+      "answer": "In the `.env` file"
+    },
+    {
+      "answer": "In the `cast` output"
+    },
+    {
+      "answer": "In the deployment command",
+      "correct": true
+    }
+  ]
+}

src/utils/questions/lesson-6/5-deployment/Q3.json

@@ -0,0 +1,18 @@
+{
+  "question": "What does the `.env` file in our project contain?",
+  "options": [
+    {
+      "answer": "Solidity code snippets"
+    },
+    {
+      "answer": "URL for Etherscan"
+    },
+    {
+      "answer": "Environment variables",
+      "correct": true
+    },
+    {
+      "answer": "All of the above"
+    }
+  ]
+}

src/utils/questions/lesson-6/5-deployment/Q4.json

@@ -0,0 +1,18 @@
+{
+  "question": "How can you load values from the `.env` file into environment variables in a bash-compatible shell?",
+  "options": [
+    {
+      "answer": "`loadenv`"
+    },
+    {
+      "answer": "You can't"
+    },
+    {
+      "answer": "`export $(grep -v '^#' .env | xargs)`",
+      "correct": true
+    },
+    {
+      "answer": "`source.env`"
+    }
+  ]
+}