搭建主网以太坊全节点钱包

编译完成之后在 build/bin 目录下会生成很多可执行文件， 就是其中一个.

When compiled, a lot of executables will be generated in the build/bin directory, which is one of them.

参数名称 | 参数说明 --syncmode | 同步模式，有三种"fast" ,"full","light". --networkid | 网络ID(整型, 1=Main, 2=Morden (弃用), 3=Ropsten, 4=Rinkeby) 这里我们使用默认值 1 表示同步主网的数据 --datadir | 钱包以及区块数据等存储目录，这个建议单独使用数据盘，不要指定系统盘的文件夹 --identity | 节点标识符 --rpc | 开启 RPC 服务 --rpcapi | 开放那些 API 给 JSONRPC 调用，默认 personal 工具是不开放的 --rpccorsdomain | RPC 调用跨域限制，号标识不限制 --rpcport | JSONRPC 服务监控的端口 --port | 同步服务端口 --rpcaddr | 可以调用 RPC 服务的IP地址，我这里只允许本地调用，不开放给其他用户，如果你想做成 Infura 那样作为公开的 API 的话，可以设置成 0.0.0.0

Parameter name Parameter description -- sync mode of synchronisation -- & & quot;, & & quot; & Full & & & & & Quot; & & & square;. --networkid network ID (integration, 1 = Main, 2 = Morden (discarded), 3 = Ropsten, 4 = Rinkeby) Here we use default value 1 to denote data from the synchronization main network -- dataddir wallet and block data storage catalogues, which suggests separate data disks, not to specify folders for the system disk --identity node identifier -- rpc turn on RPC services -- rpcapcappi Morden (disclosed) to open those API to JSONRPPCC, if you want to use an unopen user -- rpsdominRPC IP0 - you can use a non-syncryplvintintrint

表示在后台运行一个脚本，并将输出导入到 nohup.out 文档中

represents running a script in the backstage and importing the output into a nohup.out document

这里我再对同步模式做一个更加详细的解释

Here's a more detailed explanation of synchronization.

【 fast 】?启动快速区块同步模式，在同步到最新区块后，转化为正常区块同步模式. 这个是推荐选项，此方法可能会对历史数据有部分丢失， 但是不影响今后的使用
【full】从开始到结束，获取区块的header，获取区块的body，从创始块开始校验每一个元素，需要下载所有区块数据信息。 速度最慢，但是能获取到所有的历史数据, 这个是默认的选项。
【light】仅获取当前状态。验证元素需要向full节点发起相应的请求。

[fast]? Activate fast block synchronization mode and convert to normal block sync mode after synchronizing to the latest block. This is the recommended option, which may be partially lost to historical data, but does not affect the future use of
[full] from beginning to end, to get the header of the block, to get the body of the block, to check every element from the beginning of the original block, and to download all block data information. The slowest speed, but to obtain all historical data, is the default option.
[light] only obtains the current state.

如果想要关闭在后台运行的节点，可以使用以下脚本

If you want to close the node running in the backstage, use the following script

在节点启动之后，我们可以使用 命令去进入节点 javascript 终端

After the node starts, we can use the command to enter the node javascript terminal

这里的 data 为上面启动 geth 时指定的 datadir 目录。

Here's data for the datdir directory specified at the start of the geth above.

进入终端以后我们就可以输入命令去查看同步的状态，网络，区块信息等，比如如果我们想查看当前同步状态的话可以使用 命令：

When you enter the terminal, you can enter the command to view the synchronous state, the network, block information, etc., for example, if you want to see the current synchronous state, you can use the command:

这里有个坑就是，你会发现你每次执行 命令的时候 currentBlock 和 highestBlock 都只相差几百，以为马上就要同步完了，只有几百个区块了。 其实你还只是同步了一小部分。这个是正常现象，因为我们使用了 --fast 选项，所以开始只同步了区块头，它还要慢慢的去同步区块 Body.

There's a pit where you'll find that every time you execute an order, it's only a few hundred different, thinking that you're about to end up synchronizing, with only a few hundred blocks. You're still synchronizing. It's normal, because we use the --fast option, so we start synchronizing blocks, and it's slowly going to sync blocks.

另外在同步的过程中我们通过 eth.blockNumber 去查看当前区块号的话会显示为 0

Also, during the synchronisation process, if we go through Eth.blockNummer to see the current block number, it's shown as zero.

可以通过 net.peerCount 来看自己的这个节点连了多少个其它节点进行数据同步。

You can see how many other nodes your data are synchronised by this node on the net.peerCount.

如果是返回的是 0 的话，那么估计可能还没有开始同步，没有找到节点，如果长时间是 0 的话，那么就查一下你的网络是否通畅了。

If the return is 0, then probably it has not started synchronizing, nodes have not been found, and if it is 0 for a long time, check if your network is working.

如果你通过 返回的是 false 的，或者 返回的是大于 0 的整数的话，如下：

If you return by false, or return by an integer number greater than 0, as follows:

那么 Congratulations, 同步已经完成，你就可以开始调用钱包 API 转账了。

So Congratulations, synchronisation is complete and you can start calling the API transfer.

顺便说一下，我用的阿里云的香港主机，中产阶级配置，大概不到两天就同步完成了，区块的数据总共 140 GB, 速度还是可以的。

By the way, the Hong Kong mainframe, the middle class, that I used, was done in less than two days, and the data for the block was 140 GB, and the speed was still good.

至此，一个全节点的以太坊钱包就部署完成，Enjoy Coding.

So, a full node of Ether's wallet is deployed, Enjoy Coding.