Ethereum deployment node
warm tips: the above explanations are for reference only, without any suggestions. There are risks in entering the market, so investment should be cautious. Before making any investment, you should make sure that you fully understand the nature of the investment and the risks involved in the proct. After a detailed understanding and careful evaluation of the proct, you can judge whether to participate in the transaction
response time: December 2, 2020. Please refer to the official website of Ping An Bank for the latest business changes
[Ping An Bank I know] want to know more? Come and see "Ping An Bank I know" ~
https://b.pingan.com.cn/paim/iknow/index.html
Get qtum node
you can get qtum node program through one of the following four methods:
1. Download binary files directly
if you don't care about the source code of qtum, the most convenient way to deploy qtum node is to download the latest binary files from qtum release page (click to open). Currently supported platforms include Linux, windows and OSX. It is recommended to download the latest version. This tutorial takes the latest version of v0.14.13 as an example
(note that the version number of the latest version you see may be different, such as 0.14.13, other strings remain unchanged)
< UL >for Mac users, please download: qtum-0.14.13-osx64.tar.gz
for Linux users, please download: qtum-0.14.13-i686-pc-linux-gnu.tar.gz (32-bit) or qtum-0.14.13-x86_ 64-linux-gnu.tar.gz (64 bit)
for Windows users, please download: qtum-0.14.13-win32.zip (32 bit) or qtum-0.14.13-win64.zip (64 bit)
for raspberry pie users, please download: qtum-0.14.13-arm-linux-gnueabihf.tar.gz
after the compressed package is decompressed, & lt; Decompression path & gt/ Bin / contains qtumd and qtum cli, which are the qtum node executable files to be used in this tutorial
A: generally, there is only one account address, otherwise there will be an error! Blockchain itself is unique. If there are multiple account addresses on one node, it violates the fundamental principle of blockchain!
in front of the article: the video version is slightly different from the text version. If you want to see my affectionate interpretation, please see the video version (meow understands blockchain phase 22 | sharding: Ethereum is too slow, "disk" him!), The logic of thinking is strange. Please see the extended version
recently, Ethereum has shown an overwhelming positive trend e to the Constantinople upgrade, while Ethereum's upgrade road is like upgrading and fighting monsters, falling into rabbithole. No one knows how deep the hole is. Since it is a long way to go, it is of vital importance to make every step well and accurately. After overcoming this difficulty, Ethereum's next technical difficulty, sharding fragmentation, has been put on the table again. This issue of "meow understands blockchain" will take you into sharding, the magic weapon that makes Ethereum fast
what is sharding
slicing technology is not a new concept. At first, it is an optimization scheme for large central database. Specifically, it divides the data in large database into many shards according to certain rules, and then stores these data in different servers to rece the data access pressure of each server, So as to improve the performance of the whole database system
let's take a small popular example:
for example, meituan, Didi taxi and other software that we often use can be divided according to the "city". Because the data of different cities do not need to communicate, the data of different cities can be stored in different databases, so that the database server can be deployed to the nearest node from the corresponding city, Can also improve the speed of access, why not do it
from the above examples, we should have a preliminary understanding of the concept of fragmentation. What about fragmentation in blockchain scenarios
taking Ethereum fragmentation as an example, in the original single chain system, the overall performance of the public chain depends on the performance of a single node. After fragmentation, each node only needs to undertake the work of the whole network, and each fragmentation works in parallel. According to vitalik, each shard is like a separate galaxy, and each fragmentation is like an independent universe, In this way, the efficiency will be improved naturally! Originally, the total network TPS of Ethereum chain was about 20. Now, if it is increased to 100 pieces, the total network TPS can be increased to 2000. Similarly, the total network capacity will be increased to 100 times of the original
"each node only needs to undertake part of the work of the whole network", which will lead to several major problems. 1. How to determine which piece of work this node is responsible for? 2. Which transactions should be classified into which segments? 3. Does each node only need to store its own transaction information (ledger)
according to the implementation of the above problems, we can divide the fragmentation into three types: network fragmentation, transaction fragmentation and state fragmentation
Network fragmentation: how to divide the nodes of the whole network into different partitions
transaction segmentation: how to divide the whole network transactions into different segments
State fragmentation: how to make each node only maintain the account book in its own fragmentation without affecting the security of the whole system
the difference and connection between main chain and fragmentation chain
we have understood the types of fragmentation, so what's the difference between main chain and shard chain
turn left | turn right
the realization of Ethereum fragmentation is a long process. Even vitalik himself said that it will be graally realized by stages. We'd better look forward to whether fragmentation can move from theory to practice
try to set your TCP / IP protocol to automatic acquisition state. Method: right click Network Neighborhood - properties - right click & quot; Local connection & quot; Properties - double click & quot; Internet Protocol TCP / IP & quot- IPX is the bottom layer protocol of NetWare. It is only responsible for the movement of data in the network. It does not guarantee the success of data transmission, nor does it provide error correction