From b5cf6ec07cee052689040aea043c1ab9b1b0acd9 Mon Sep 17 00:00:00 2001 From: Yu Date: Wed, 17 Nov 2021 16:59:48 +0800 Subject: [PATCH 1/2] update en exit --- docs/guide/Using-venus-Shared-Modules.md | 4 +- docs/master/Incubation_exit_guide.md | 111 +++++++++++++++-------- 2 files changed, 78 insertions(+), 37 deletions(-) diff --git a/docs/guide/Using-venus-Shared-Modules.md b/docs/guide/Using-venus-Shared-Modules.md index 76b18eccc..534bf996c 100644 --- a/docs/guide/Using-venus-Shared-Modules.md +++ b/docs/guide/Using-venus-Shared-Modules.md @@ -698,7 +698,7 @@ Wait till lotus-miner to finish up existing sealing jobs and make sure you have ./lotus-convert -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=2 ``` -### More on lotus-convert +:::tip lotus-convert is a utility tool for migrating from lotus to venus. @@ -714,6 +714,8 @@ lotus-convert is a utility tool for migrating from lotus to venus. ./lotus-convert -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=2 ``` +::: + ## Questions? Find us on [Slack](https://filecoinproject.slack.com/archives/CEHHJNJS3)! \ No newline at end of file diff --git a/docs/master/Incubation_exit_guide.md b/docs/master/Incubation_exit_guide.md index b1754869c..abc58c3ff 100644 --- a/docs/master/Incubation_exit_guide.md +++ b/docs/master/Incubation_exit_guide.md @@ -1,18 +1,22 @@ ## Incubation Exit Guide -After each phase of the incubator is over, miners face the problem of withdrawing. Currently there are lotus and venus implementations of Filecoin mainnet. Therefore, the exit options available to miners are： +There are couple options for storage providers to exit incubation program either voluntarily or after each phase ends. -- Access to venus chain services built by other operators or participate in the second phase of the incubator; -- Access the venus chain service built by yourself; -- Switch back to lotus. +- Join a hosted chain service (venus shared modules) by third party. +- Deploy a chain service (venus shared modules) by yourself. +- Switch back to Lotus. -The above is the optional exit plan for miners at the current stage. Here we explain how to access the venus chain service built by yourself and switch back to the lotus plan one by one. +We will go through option 2 and 3 in this documentation. -### Switch back to your own venus +:::warning -- Build the chain service layer, refer to the document [Chain service construction](./Chain_service_construction.md) +Make sure you go through the documentation carefully before carry out the exit. Find us on Slack if you have questions. -- Modify the `venus-wallet` configuration (`~/.venus_wallet/config.toml`) to point to the local chain service. +::: + +### Deploy a chain service + +Refer to this [document](https://venus.filecoin.io/guide/How-To-Deploy-MingPool.html) to first deploy your own venus chain service. Modify configuration file (`~/.venus_wallet/config.toml`) of `venus-wallet` to point to the newly deployed chain service. ```toml [APIRegisterHub] @@ -21,7 +25,7 @@ Token = "" SupportAccounts = [""] ``` -- Modify the configuration of `venus-sealer` (`~/.venussealer/config.toml`) to point to the local chain service. +Modify the configuration file of `venus-sealer` (`~/.venussealer/config.toml`) to point to the newly deployed chain service. ```toml [Node] @@ -40,69 +44,104 @@ SupportAccounts = [""] Token = ``` -- Restart `venus-walle` --> `venus-sealer`. - -[Reference documents](../guide/Using-venus-Shared-Modules.md) +Restart `venus-walle` and `venus-sealer`. ### Switch back to lotus -- To build a lotus synchronization node, the current chain data is already very large, it is recommended to import the data from the snapshot. +Refer to Lotus [documentation](https://docs.filecoin.io/mine/lotus/#protocol-labs-example-architecture) to build and deploy a Lotus node. Sync the node from a snapshot. + ```bash -nohup ./lotus daemon --import-snapshot=https://fil-chain-snapshots-fallback.s3.amazonaws.com/mainnet/minimal_finality_stateroots_latest.car > lotus.log 2>&1 & +$ nohup ./lotus daemon --import-snapshot=https://fil-chain-snapshots-fallback.s3.amazonaws.com/mainnet/minimal_finality_stateroots_latest.car > lotus.log 2>&1 & ``` -You can also download the snapshot to the local first, and then `--import-snapshot` points to the local path. +Import addresses under your miner_id (eg. owner, worker, controller addresses and etc.) into lotus; -- Import the wallet address related to miner_id (eg.Owner, Worker, Controller, etc.) into lotus; ```bash -# Export private key from venus-wallet +# export private key from venus-wallet $ ./venus-wallet export Password: -# import to lotus +# import them to lotus $ ./lotus wallet import Enter private key: ``` -- Wait for the sector currently being sealed to be completed (ProveCommitSector message on the chain); - -- Stop venus-sealer and initialize a new repo with lotus-miner. The directory should not be the same as the repo of venus-sealer. +Make sure you have no sealing tasks running, messages properly sent on-chain and enough time before your next windowPost deadline. Then stop venus-sealer and initialize a new repo using lotus-miner. ```bash TRUST_PARAMS=1 ./lotus-miner init --no-local-storage --actor= --sector-size=32G --nosync ``` -- Create the `store path` of lotus-miner, which is the same as the store path of venus-sealer, so there is no need to move the permanent storage file. -```bash -# Do not add the `--init` flag, because venus-sealer has been created -./lotus-miner storage attach --store -``` +:::warning + +Note that lotus-miner repo must not have the same path as the repo of venus-sealer. + +::: + +Build lotus-fix utility tool, set nextid and import sectors from venus-sealer. -- Modify the key=/storage/nextid in the metadata to ensure that the new sectorID does not start from 1. ```bash -# Compile lotus-fix in the venus-sealer directory +# Skip if you already compiled ffi +$ git submodule update --init --recursive +$ make deps + +# Compile lotus-fix $ make lotus-fix -# Modify the nextid of lotus-miner -./lotus-fix -lotus-miner-repo=<~/.lotusminer> -sid= +# fix nextid and import sectors from venus-sealer +# change repo path accordingly +$ ./lotus-fix -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=2 ``` -- Import the Sector data completed by venus-sealer, this is not necessary, because these can also be found on the chain. +:::tip + +lotus-fix is a utility tool for migrating from venus to lotus. + ```bash -./lotus-fix -task=import-sector -lotus-miner-repo=/home/litao/.lotusminer -venus-sealer-repo=~/.venussealer -import sectors success. +# taskType=0; manually change nextid +# set nextid to 300 with -sid flag +$ ./lotus-fix -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=0 -sid=300 + +# taskType=1; import sectors from venus-sealer to lotus-miner +$ ./lotus-fix -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=1 + +# taskType=2; atuo change nextid and import sectors from venus-sealer to lotus-miner +$ ./lotus-fix -lotus-miner-repo=/root/.lotusminer/ -venus-sealer-repo=/root/.venussealer -taskType=2 ``` -> These two steps need to temporarily stop lotus-miner operation, so it is recommended to operate after init. In addition, if the operation is performed by the root user and lotus-miner is performed by a sub-user (eg. test), file authorization is required. + +::: + +:::warning + +Make sure lotus-miner is not running while using lotus-fix. + +::: + +:::tip + +If executing lotus-fix from root user while lotus-miner is run by a user account, you may need set the following. + ```bash +# For example, if your user account name is `test` chown test:test /home/test/ -R ``` -- Make a new sector +::: + +Attach `store path` to lotus-miner, which should be the same as the store path of venus-sealer. + +```bash +# do not add the `--init` flag +./lotus-miner storage attach --store +``` + +Pledge a new sector ```bash +# attach seal path for lotus-miner $ ./lotus-miner storage attach --init --seal $ nohup ./lotus-miner run > miner.log 2>&1 & $ ./lotus-miner sectors pledge ``` -At this point, your cluster has been switched to lotus operation. For follow-up operations, please refer to lotus related documents. The previously created venus-sealer repo can also be deleted. +At this point, your storage system has been switched to lotus. For follow-up operations, please refer to lotus related documents. From caf965049c2e8273ae6393bb9e732ac9448fd121 Mon Sep 17 00:00:00 2001 From: Yu Date: Wed, 17 Nov 2021 17:07:07 +0800 Subject: [PATCH 2/2] update miner to sp --- docs/guide/README.md | 18 +++++++++--------- docs/zh/guide/README.md | 28 ++++++++++++++-------------- 2 files changed, 23 insertions(+), 23 deletions(-) diff --git a/docs/guide/README.md b/docs/guide/README.md index 395aab518..1dd2bddf0 100644 --- a/docs/guide/README.md +++ b/docs/guide/README.md @@ -18,21 +18,21 @@ We plan to let Venus support the development of storage pool. At the begining, w After that, through several times of re-design and modification, we finally decide to build it as a distributed storage pool. Distributed storage pool will not completely in charge with any single storage provider, but managed by multiple storage providers, which is more like a storage provider group/union. -The external features of Venus distributed storage pool are similar to other pools. Storage Providers can store their resources in distributed geographic nodes. As long as there is a stable connection to the network, the storage provider can create a node accessible to Venus storage pool; The probability of earning the block reward is proportional to the amount of storage the miner contributes to the Filecoin network, and the final result of separate calculation and overall calculation should be the same: ***n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p***, which provides a theoretical basis on the algorithm. +The external features of Venus distributed storage pool are similar to other pools. Storage Providers can store their resources in distributed geographic nodes. As long as there is a stable connection to the network, the storage provider can create a node accessible to Venus storage pool; The probability of earning the block reward is proportional to the amount of storage the storage provider contributes to the Filecoin network, and the final result of separate calculation and overall calculation should be the same: ***n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p***, which provides a theoretical basis on the algorithm. For the storage and retrieval, storage providers can access the network through the venus unified entrance or by themselves. In the design and with the permission from storage providers, venus will select the appropriate node to store data according to specific requirements, so that the data is closer to the real scenario. 1. ***Data storage***: component sharing is supported, and the storage will be gradually migrated to MySQL to ensure the metadata security of Venus through some highly available solutions. -2. ***Shared Modules***: support high availability, ensure the quality of service, reduce the time cost and maintenance cost of miners, which make it easier for miners to join the storage pool. Nowadays, mining is a high-tech activity, but to achieve Filecoin's goal to get the utmost out of storage resources, it is inevitable to lower the threshold to attract more participants. +2. ***Shared Modules***: support high availability, ensure the quality of service, reduce the time cost and maintenance cost of storage providers, which make it easier for storage providers to join the storage pool. Nowadays, mining is a high-tech activity, but to achieve Filecoin's goal to get the utmost out of storage resources, it is inevitable to lower the threshold to attract more participants. -3. ***Combine the right for more block rewards***: miners can integrate resources together and help each other pack messages, so as to avoid the situation of small miners that no one can pack messages. +3. ***Combine the right for more block rewards***: storage providers can integrate resources together and help each other pack messages, so as to avoid the situation of small storage providers that no one can pack messages. 4. ***Improve the TPS of Filecoin network***: if there are multiple blocks at the same height, venus-miner can ensure that the messages in each block are different, as the avoidance of highly-repeated messages when blocks are separated. 5. ***Improve the stability of messages***: messages in storing activities can be separated from nodes and managed by venus-messager, which can track the latest state of the chain to set a relatively reasonable estimated gas parameter, and also supports users to set a message parameter themselves. -6. ***Improve the speed of data access***: the current Filecoin network is more like a pool which is merely for data storage, but as a complete data service, it also needs data retrieval to realize its real value. With sufficient miner users, Venus has more chances to promote the real data application. For example, for data distribution, Venus can distribute the data to some miners' nodes nearest to the customers, which can improve the access speed; some public data can distribute these data to more nodes as much as possible to ensure that access at any location is effective, which can greatly improve the performance of IPFS network and further realize the goal of IPFS, as one of the Web3.0 solutions. +6. ***Improve the speed of data access***: the current Filecoin network is more like a pool which is merely for data storage, but as a complete data service, it also needs data retrieval to realize its real value. With sufficient miner users, Venus has more chances to promote the real data application. For example, for data distribution, Venus can distribute the data to some storage providers' nodes nearest to the customers, which can improve the access speed; some public data can distribute these data to more nodes as much as possible to ensure that access at any location is effective, which can greatly improve the performance of IPFS network and further realize the goal of IPFS, as one of the Web3.0 solutions. ## How Venus works @@ -69,16 +69,16 @@ venus is similar to lotus-daemon, which is used to support all nodes. venus is c 1. External signature is supported in the API of creating block (request will be proposed to lotus too). 2. The API of message selection supports the selection of multiple batches of messages at the same time, which is used to select messages when multiple storage providers get the block rewards. 3. Support the centralized authorization access to venus-auth. - + Therefore, if you are interested in the mixed deployment of venus / lotus, you need to use Venus project which is compatible to Lotus or pick your own CCS. ### venus-miner -The function of venus-miner is to combine the rights to earn block rewards. The program can configure the location of multiple miners and their sealers and wallets, and generate blocks for these miners at the same time. venus-miner has the following features: +The function of venus-miner is to combine the rights to earn block rewards. The program can configure the location of multiple storage providers and their sealers and wallets, and generate blocks for these storage providers at the same time. venus-miner has the following features: -1. Separate data: because the process of generating blocks needs to access data, and storage provider's sealer may be heterogeneous, but now most miners will use their own codes, so there is a problem about how to access these data to realize joint mining. By venus-miner’s independence on the storage organization mode and completing the proofs by miners, no matter how the miner's sealer organizes the storage, as long as the Computeproof API is implemented, venus-miner can generate the proof through it. +1. Separate data: because the process of generating blocks needs to access data, and storage provider's sealer may be heterogeneous, but now most storage providers will use their own codes, so there is a problem about how to access these data to realize joint mining. By venus-miner’s independence on the storage organization mode and completing the proofs by storage providers, no matter how the miner's sealer organizes the storage, as long as the Computeproof API is implemented, venus-miner can generate the proof through it. 2. Separate private key: when calculating random numbers and signature blocks, all operations about private key are accessed through remote wallet, which can improve the security of mining activities. -3. Improve miners' wincount and TPS: when the miner who uses venus-miner rto get multiple (> 1) rights of block rewards in a period, venus-miner will try to select different messages from the message pool for packaging, which can somehow improve the speed of these messages on the chain, and make the block get more gas premium. +3. Improve storage providers' wincount and TPS: when the miner who uses venus-miner rto get multiple (> 1) rights of block rewards in a period, venus-miner will try to select different messages from the message pool for packaging, which can somehow improve the speed of these messages on the chain, and make the block get more gas premium. ### venus-messenger @@ -99,7 +99,7 @@ In terms of functions: ### venus-wallet -venus-wallet is a remote wallet, which can support both Lotus and Venus in terms of protocols. In a typical deployment environment, this module is deployed locally by miners, and the security of assets is guaranteed by certain policy configuration. venus-wallet has the following features: +venus-wallet is a remote wallet, which can support both Lotus and Venus in terms of protocols. In a typical deployment environment, this module is deployed locally by storage providers, and the security of assets is guaranteed by certain policy configuration. venus-wallet has the following features: 1. Private key management function: currently it supports the private key management of asymmetric algorithms BLS and SECP, and it can generate random private key, and uses aes128 to encrypt and store the private key symmetrically whilst supports the private key to sign the data. 2. Signature verification: each signature type has its verification policy, which ensures that the signer won't do deceits the wallet through non-credible signature type. diff --git a/docs/zh/guide/README.md b/docs/zh/guide/README.md index 6a0f2856d..b1377c5d8 100644 --- a/docs/zh/guide/README.md +++ b/docs/zh/guide/README.md @@ -2,7 +2,7 @@ 在同一条区块链上需要具有多个互操作的软件实现，每个实现都有自己的安全问题集，但是所有实现不尽相同，因此，启动具有多种实现方式的加密货币网络可降低发生灾难性错误的可能性，Venus正是Filecoin的实现之一。 -Venus代指Filecoin的通用实现之一，venus则代指Venus的组件之一。Venus致力于帮助中小矿工能够更加简单的加入到Filecoin生态网络建设中。 +Venus代指Filecoin的通用实现之一，venus则代指Venus的组件之一。Venus致力于帮助中小存储提供者能够更加简单的加入到Filecoin生态网络建设中。 目前Venus通过venus、venus-sealer、venus-miner、venus-wallet、venus-messager、venus-auth组件，已经实现了Filecoin分布式矿池的支持，未来，Venus将持续完善自身，并共同推进开源的Filecoin开发与生态的发展。 @@ -14,20 +14,20 @@ Venus代指Filecoin的通用实现之一，venus则代指Venus的组件之一。 完成以上工作后，我们着手于Venus的开发方向。 -我们的设计是让Venus向矿池的发展角度去支持，最初的设计是从“如何扩展单一矿工”思考，这个方向存在理论上的可行性，但是最大的问题在于Filecoin独特的证明机制。因为Filecoin网络的矿工必须周期性的提交‘时空证明’，而为了生成证明，矿工必须读取一整个partition的数据，如果sector极其分散的分布到不同的地方，通过公网读取，则不是一个可执行的方案。 +我们的设计是让Venus向矿池的发展角度去支持，最初的设计是从“如何扩展单一存储提供者”思考，这个方向存在理论上的可行性，但是最大的问题在于Filecoin独特的证明机制。因为Filecoin网络的存储提供者必须周期性的提交‘时空证明’，而为了生成证明，存储提供者必须读取一整个partition的数据，如果sector极其分散的分布到不同的地方，通过公网读取，则不是一个可执行的方案。 -后来我们通过数次的设计与修改，最终产生了现在的方案，就是分布式矿池。分布式矿池并非体现在单一矿工，而是将分布式的概念体现在多矿工的管理，这更像一个矿工联合体。 +后来我们通过数次的设计与修改，最终产生了现在的方案，就是分布式矿池。分布式矿池并非体现在单一存储提供者，而是将分布式的概念体现在多存储提供者的管理，这更像一个存储提供者联合体。 Venus分布式矿池在外部的体现和传统的分布式矿池是相似的。在存储资源上体现在地域分布性，只要有网络可以访问的地方，都可以使节点接入到Venus矿池；在出块的角度上，因为Filecoin按算力比例来计算出块机率，所以分散的计算和整体的计算的最终结果应该是相同：***n1/p+ n2/p+n3/p......= (n1+n2+n3+.....)/p***，这在算法的基础上提供了理论基础。 -在真实数据存储检索上，矿工可以通过venus统一入口接入网络或者自主接入。设计中，venus会在获得矿工允许的条件下，按照数据的访问需求来选择合适的节点存储数据，使得数据更贴近真实的使用场景。 +在真实数据存储检索上，存储提供者可以通过venus统一入口接入网络或者自主接入。设计中，venus会在获得存储提供者允许的条件下，按照数据的访问需求来选择合适的节点存储数据，使得数据更贴近真实的使用场景。 1. ***数据存储***：支持组件共享，存储会逐渐迁移到MySQL，通过一些高可用的方案保证Venus的元数据安全。 -2. ***共享组件***：支持高可用，保证服务的质量，减少矿工的时间成本与维护成本，这使得矿工能够更容易加入到矿池生态中。现在的挖矿活动专业性很强，而实现Filecoin利用闲散存储资源的梦想则不可避免需要降低参与门槛，才能吸引更多的参与者进来。 -3. ***聚集出块权***：矿工能够将资源整合在一起，互相帮助打包消息，这样可以避免小矿工的消息无人打包的困境。 +2. ***共享组件***：支持高可用，保证服务的质量，减少存储提供者的时间成本与维护成本，这使得存储提供者能够更容易加入到矿池生态中。现在的挖矿活动专业性很强，而实现Filecoin利用闲散存储资源的梦想则不可避免需要降低参与门槛，才能吸引更多的参与者进来。 +3. ***聚集出块权***：存储提供者能够将资源整合在一起，互相帮助打包消息，这样可以避免小存储提供者的消息无人打包的困境。 4. ***提升Filecoin网络的吞吐量***：如果同一高度存在多个区块，venus-miner能够保证每个区块中的消息都是不同的，而如果各自出块，消息则很可能大量重复。 5. ***提升消息的稳定性***：挖矿活动中的消息可以和节点分开，由venus-messager来管理，venus-messager会跟踪链的最新状态来设置一个相对合理的预估的gas参数，同时也支持用户自己设置一个消息参数。 -6. ***提升数据访问速度***：目前的Filecoin网络更多的还是存储，但是作为一个存储服务，最终需要对外输出检索服务才能实现根本价值。如果有足够多的矿工使用Venus，那么Venus在真实数据的处理上就有更多的可能，比如数据的分布，Venus可以将数据分布到距离客户最近的一些矿工节点，这样可以提高客户的访问速度；比如一些公有数据可以把这些数据尽可能的分散到更多的节点上，保障在任意位置的访问都有效，这可以大大提升IPFS网络的效能，进一步实现IPFS Web3.0的梦想。 +6. ***提升数据访问速度***：目前的Filecoin网络更多的还是存储，但是作为一个存储服务，最终需要对外输出检索服务才能实现根本价值。如果有足够多的存储提供者使用Venus，那么Venus在真实数据的处理上就有更多的可能，比如数据的分布，Venus可以将数据分布到距离客户最近的一些存储提供者节点，这样可以提高客户的访问速度；比如一些公有数据可以把这些数据尽可能的分散到更多的节点上，保障在任意位置的访问都有效，这可以大大提升IPFS网络的效能，进一步实现IPFS Web3.0的梦想。 ## venus如何工作 @@ -42,9 +42,9 @@ venus类似lotus-daemon，用于实现全节点。venus接入Filecoin区块链 venus节点自身有一些区别与lotus的地方： 1. 创建区块的接口中支持了外部签名（后续会向Lotus提PR） -2. 消息选择的接口支持同时选择多个批次的消息，用于多矿工出块时选择消息。 +2. 消息选择的接口支持同时选择多个批次的消息，用于多存储提供者出块时选择消息。 3. 支持venus-auth的的中心访问授权 - + 因此如果对Venus/Lotus混合部署感兴趣，需要使用我们维护的lotus兼容venus的项目，可自行pick代码编译。 ### venus-auth @@ -55,10 +55,10 @@ venus-auth是用于授权的组件，在典型的部署环境下venus-auth用于 venus-miner的作用是聚集出块权，可以为接入链服务的多个集群执行出块逻辑。venus-miner有以下特点： -1. 分离数据：由于生成区块的过程需要访问数据，并且矿工的sealer可能是异构的，但目前多数矿工会使用自己定制的代码，那么要实现联合挖矿就存在如何访问到这些数据的问题。通过隔断venus-miner对存储组织方式的依赖，通过让证明在矿工侧完成，无论矿工的sealer如何组织存储，只要实现了**ComputeProof**接口，venus-miner就可以通过这个接口来生成证明。 +1. 分离数据：由于生成区块的过程需要访问数据，并且存储提供者的sealer可能是异构的，但目前多数存储提供者会使用自己定制的代码，那么要实现联合挖矿就存在如何访问到这些数据的问题。通过隔断venus-miner对存储组织方式的依赖，通过让证明在存储提供者侧完成，无论存储提供者的sealer如何组织存储，只要实现了**ComputeProof**接口，venus-miner就可以通过这个接口来生成证明。 2. 分离私钥：计算随机数及签名区块的过程中，所有涉及到私钥的操作都通过远程钱包的方式来访问，这样既无泄漏集群私钥,又能保证出块逻辑正常运行。 -3. 提高网络TPS：当venus-miner负责的矿工在一个周期获得多个（>1）出块权，venus-miner会尽量从消息池中选择不同的消息进行打包，这样一定程度上可以提升消息上链的速度，同时使该出块可能获得更多的小费奖励（Premium）。 -4. 收益稳定性: 多矿工联合挖矿配套奖励池分配系统可以让小矿工每天都能获得区块奖励,也可以减少某些矿工偶发性出块错误造成的损失. +3. 提高网络TPS：当venus-miner负责的存储提供者在一个周期获得多个（>1）出块权，venus-miner会尽量从消息池中选择不同的消息进行打包，这样一定程度上可以提升消息上链的速度，同时使该出块可能获得更多的小费奖励（Premium）。 +4. 收益稳定性: 多存储提供者联合挖矿配套奖励池分配系统可以让小存储提供者每天都能获得区块奖励,也可以减少某些存储提供者偶发性出块错误造成的损失. ### venus-messager @@ -78,7 +78,7 @@ venus-messager组件的目标是更好的帮助消息上链，并能够灵活的 ### venus-wallet -venus-wallet是一个远程钱包，协议上能够同时支持lotus和venus。在典型的部署环境中，这个组件由矿工部署在本地，并通过一定的策略配置保证资产的安全。venus-wallet有以下功能特点： +venus-wallet是一个远程钱包，协议上能够同时支持lotus和venus。在典型的部署环境中，这个组件由存储提供者部署在本地，并通过一定的策略配置保证资产的安全。venus-wallet有以下功能特点： 1. 私钥管理模块：目前支持非对称算法BLS和SECP的私钥管理，能够生成随机私钥，并运用aes128对私钥进行对称加密存储，同时支持私钥对数据进行签名。 2. 签名验证：每种签名类型都有对应验证策略，保证了签名方不能在签名类型上欺骗钱包。 @@ -97,7 +97,7 @@ venus-market是Venus系统中的市场组件。其愿景是打造Filecoin网络 ### venus-gateway -venus-gateway是独立组件与链服务层的桥梁，用于简化部署并降低矿工访问的复杂性、增加矿工访问的安全性。独立组件启动时将其服务接口注册到venus-gateway，链服务组件需要时通过venus-gateway请求对应集群的服务接口。 +venus-gateway是独立组件与链服务层的桥梁，用于简化部署并降低存储提供者访问的复杂性、增加存储提供者访问的安全性。独立组件启动时将其服务接口注册到venus-gateway，链服务组件需要时通过venus-gateway请求对应集群的服务接口。 - 存储提供者不需要外部IP和曝光钱包服务； - 存储池配置SSL证书后，集群与存储池的连接是安全的；