You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<SideDrawerbuttonText="ano'wee Q for the road"title="John n Maeve rock too">
29
23
<Questionquestion="question-2" />
30
24
</SideDrawer>
31
25
<br/>
32
26
<br/>
33
27
And now let's check if we were right :)
34
28
35
-
<SideDrawerbuttonText="A what chain?!!">
29
+
<SideDrawerbuttonText="A what chain?!">
36
30
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!!
37
31
38
32
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.
139
133
</SideDrawer>
140
134
141
135
## 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!
152
151
153
152
## Let’s get this party started!
154
153
@@ -671,12 +670,12 @@ instance below.
671
670
672
671
Open the dropdown under ‘Deployed Contracts’, to see our function tabs:
673
672
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.
680
679
681
680

682
681
@@ -704,13 +703,14 @@ If you look closely, inside the “logs” part, our smart contract predicted a
704
703
What if you try out setting the message to `gm` and look at the logs again. Can
705
704
you see the magical spell that is being cast here?
706
705
707
-
{/*  */}
Copy file name to clipboardExpand all lines: utils/questions/question-2.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,11 @@
2
2
"question": "Which statement is true?",
3
3
"options": [
4
4
{
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.",
6
6
"correct": true
7
7
},
8
8
{
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."
0 commit comments