Skip to content

Commit d5f94c4

Browse files
committed
clean up lesson 1 quiz content
1 parent f50a20e commit d5f94c4

File tree

3 files changed

+30
-30
lines changed

3 files changed

+30
-30
lines changed

pages/lessons/projects/1.mdx

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -18,21 +18,15 @@ smart contract on either Jupiter, or Earth, and although you may be grounded to
1818
the latter, you are going to deploy yours on a **blockchain**. Not a real
1919
blockchain, well not at first. Hang on!
2020

21-
22-
23-
<SideDrawer buttonText="wee Q" title="7i7o Rocks">
21+
<SideDrawer buttonText="Warm-up questions" title="Warm-up questions">
2422
<Question question="question-1" />
25-
</SideDrawer>
26-
<br/>
27-
28-
<SideDrawer buttonText="ano'wee Q for the road" title="John n Maeve rock too">
2923
<Question question="question-2" />
3024
</SideDrawer>
3125
<br/>
3226
<br/>
3327
And now let's check if we were right :)
3428

35-
<SideDrawer buttonText="A what chain?!!">
29+
<SideDrawer buttonText="A what chain?!">
3630
A blockchain has quite a few layers to let function, but it basically gives us a place to do computation, and store information. So in one sense it functions as a database. Think about this. To get access to all of the information on a traditional database you need permission from a higher authority, right? Access to information on a public blockchain is permission**less**. Not only can we read the information on it, but anyone can also write information to it. And that’s where we come in and get this all started with our *smart contract*. And what is also different to a traditional database is that once the information goes onto this blockchain, it stays there forever, and ever, and ever….thanks to cryptography!!
3731

3832
But what is the information that is kept on this chain? Wait. Why a chain? Well
@@ -139,16 +133,21 @@ benefits to this decentralised model as we’ll continue to see.
139133
</SideDrawer>
140134

141135
## What are we going to do?
142-
By the end of this lesson we’ll have learned a lot. A simple breakdown of the steps to get there is:
143-
- Set up our work environment
144-
- Create a Smart Contract
145-
- Learn basic Solidity concepts
146-
- Define variables
147-
- Create a function
148-
- Learn about events on the blockchain
149-
- Deploy our Smart Contract in Remix
150-
- At the end of the project, we’re really going to test your knowledge with a quiz, so take in whatever you can.
151-
- We might even have some questions along the way for fun to expand your already amazing mind!!
136+
137+
By the end of this lesson we’ll have learned a lot. A simple breakdown of the
138+
steps to get there is:
139+
140+
- Set up our work environment
141+
- Create a Smart Contract
142+
- Learn basic Solidity concepts
143+
- Define variables
144+
- Create a function
145+
- Learn about events on the blockchain
146+
- Deploy our Smart Contract in Remix
147+
148+
At the end of the project, we’re really going to test your knowledge with a
149+
quiz, so take in whatever you can. We might even have some questions along the
150+
way for fun to expand your already amazing mind!
152151

153152
## Let’s get this party started!
154153

@@ -671,12 +670,12 @@ instance below.
671670

672671
Open the dropdown under ‘Deployed Contracts’, to see our function tabs:
673672

674-
- the blue ones are our “**view**” functions that doesn’t modify our state
675-
- the orange one lets us trigger the setMessage function which will change the
676-
state. Be sure to click on the little drop down menu on the right. From here
677-
on, we can interact with our contract. Feel free to test the functions. Click
678-
on the getMessage and messageCount tabs before and after setting a new
679-
message. modify data on our contract.
673+
- the blue ones are our “**view**” functions that doesn’t modify our state
674+
- the orange one lets us trigger the setMessage function which will change the
675+
state. Be sure to click on the little drop down menu on the right. From here
676+
on, we can interact with our contract. Feel free to test the functions.
677+
Click on the getMessage and messageCount tabs before and after setting a new
678+
message. modify data on our contract.
680679

681680
![Available Interactive Options once Contract is Deployed](/assets/lessons/1/img_7.png)
682681

@@ -704,13 +703,14 @@ If you look closely, inside the “logs” part, our smart contract predicted a
704703
What if you try out setting the message to `gm` and look at the logs again. Can
705704
you see the magical spell that is being cast here?
706705

707-
{/* ![Wizard Wooshing on Successful Lesson](/assets/lessons/1/img_10.png) */}
708706
![Genie Girl holds Ethereum Crystal Ball](/assets/lessons/1/img_11.png)
709707

710708
Before you go ahead and tell us: **what your future in web3 is**, have a check
711709
on what you didn’t know a little while ago, and what you know now!
712710

713711
<Quiz quiz="quiz-1"/>
712+
<br />
714713

715-
Now, go to the community in **developerdao.peeranha.io** to share your new Open Sourcerer
716-
powers!
714+
Now, go to the community in
715+
[developerdao.peeranha.io](https://developerdao.peeranha.io) to share your new
716+
Open Sourcerer powers!

utils/questions/question-1.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"question": "True or False: In order to access and information to a public blockchain you need to have permission from the owner",
2+
"question": "True or False: In order to access information on a public blockchain you need to have permission from the owner.",
33
"options": [
44
{
55
"answer": "True"

utils/questions/question-2.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22
"question": "Which statement is true?",
33
"options": [
44
{
5-
"answer": "It’s important to test your code rigorously because once deployed it resides on the Blockchain forever",
5+
"answer": "It’s important to test your code rigorously, because once deployed it resides on the Blockchain forever.",
66
"correct": true
77
},
88
{
9-
"answer": "The great thing about the blockchain is if you need to make corrections to buggy code you can just upload fixes which will automatically overwrite previous versions seamlessly"
9+
"answer": "The great thing about the blockchain is if you need to make corrections to buggy code, you can just upload fixes, which will automatically overwrite previous versions seamlessly."
1010
}
1111
]
1212
}

0 commit comments

Comments
 (0)