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
Copy file name to clipboardExpand all lines: pages/lessons/fundamentals/wolovim-part-1.mdx
+33-2Lines changed: 33 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,15 @@ icons:
15
15
16
16
So, you’ve heard about this [Ethereum](https://ethereum.org/) thing and are ready to venture down the rabbit hole? This post will quickly cover some blockchain basics, then get you interacting with a simulated Ethereum node – reading block data, checking account balances, and sending transactions. Along the way, we’ll highlight the differences between traditional ways of building apps and this new decentralized paradigm.
This post aspires to be accessible to a wide range of developers. Python tools will be involved, but they are just a vehicle for the ideas – no problem if you are not a Python developer. I will, however, be making just a few assumptions about what you already know, so we can quickly move on the Ethereum-specific bits.
@@ -30,7 +39,7 @@ Again, if any of these are untrue, or you don’t plan to reproduce the code in
30
39
31
40
### **Blockchains, briefly**
32
41
33
-
There are many ways to describe Ethereum, but at its heart is a blockchain. Blockchains are made up of a series of blocks, so let’s start there. In the simplest terms, each block on the Ethereum blockchain is just some metadata and a list of transactions. In JSON format, that looks something like this:
42
+
There are many ways to describe Ethereum, but at its heart is a blockchain. Blockchains are made up of a series of blocks, so let’s start there. In the simplest terms, each block on the Ethereum blockchain is some metadata and a list of transactions. In JSON format, that looks something like this:
In this walkthrough, we’ll just be working within a Python interpreter. We won't be creating any directories, files, classes or functions.
@@ -125,7 +143,7 @@ This will print out some information about the versions of Python and IPython yo
125
143
In [1]:
126
144
```
127
145
128
-
You’re looking at an interactive Python shell now. Essentially, its a sandbox to play in. If you’ve made it this far, its time to import Web.py:
146
+
You’re looking at an interactive Python shell now. Essentially, its a sandbox to play in. If you’ve made it this far, its time to import web3.py:
129
147
130
148
```python
131
149
In [1]: from web3 import Web3
@@ -180,6 +198,17 @@ That simulated node is called [**eth-tester**](https://github.com/ethereum/eth-
180
198
In [4]: w3 = Web3(Web3.EthereumTesterProvider())
181
199
```
182
200
201
+
Before we move on, does all that make sense? Test yourself:
202
+
203
+
<SideDrawerbuttonText="Check-in 2"title="TODO">
204
+
<Questionquestion="eth-intro-1/1-intro/Q1" />
205
+
<Questionquestion="eth-intro-1/1-intro/Q2" />
206
+
<Questionquestion="eth-intro-1/1-intro/Q3" />
207
+
<Questionquestion="eth-intro-1/1-intro/Q4" />
208
+
<Questionquestion="eth-intro-1/1-intro/Q5" />
209
+
</SideDrawer>
210
+
<br/>
211
+
183
212
Now you’re ready to surf the chain! That’s not a thing people say. I just made that up. Let’s take a quick tour.
184
213
185
214
### **The quick tour**
@@ -294,6 +323,8 @@ The latter looks good! The balance went from 1,000,000 to 1,000,003 ether. But w
294
323
**Note**: On the public network, transaction fees are variable based on network demand and how quickly you'd like a transaction to be processed.
295
324
</Callout>
296
325
326
+
<Quizquiz="eth-intro-1-quiz" />
327
+
297
328
### **And breathe**
298
329
299
330
We’ve been at this for a while, so this seems as good a place as any to take a break. The rabbit hole continues on, and we’ll continue exploring in part two of this series. Some concepts to come: a deeper look into accounts, smart contracts, tooling and how to stake out on your own as an Ethereum developer. Have follow-up questions? Requests for new content? Let me know on [Twitter](https://twitter.com/wolovim).
0 commit comments