update the information about how to join the node strategy.

nebulasio · Mar 23, 2020 · 6c7a462 · 6c7a462
1 parent a5f5411
commit 6c7a462
Show file tree

Hide file tree

Showing 5 changed files with 47 additions and 9 deletions.
diff --git a/docs/go-nebulas/blockchain/environment.md b/docs/go-nebulas/blockchain/environment.md
@@ -18,8 +18,29 @@ RAM: >= 16G
 Disk: >= 600G SSD
 ```
 
+
+
 ## Environment
 
+**Node Installation Tutorial** - review the [Nebulas Technical Documentation: Nebulas 101 - 01 Compile Installation](../tutorials/01-installation).
+
+
+It’s recommended to build and deploy nodes via docker:
+
+
+
+*   Install [docker](https://docs.docker.com/get-started/) and [docker-compose](https://docs.docker.com/compose/install/)
+*   Execute the following docker command via [root](https://github.com/nebulasio/go-nebulas)
+
+```
+sudo docker-compose build
+
+sudo docker-compose up -d
+
+```
+
+
+
 ```
 System: Ubuntu 18.04(recommand), other Linux is ok.
 NTP: Ensure machine time synchronization

diff --git a/docs/go-nebulas/dapp-development/rpc/rpc_admin.md b/docs/go-nebulas/dapp-development/rpc/rpc_admin.md
@@ -1,6 +1,6 @@
 # RPC Management
 
-Beside the [NEB API RPC](README) interface nebulas provides additional management APIs. Neb console supports both API and management interfaces. Management RPC uses the same gRPC and HTTP port, which also binds [NEB API RPC](README.html) interfaces.
+Beside the [NEB API RPC](README) interface nebulas provides additional management APIs. Neb console supports both API and management interfaces. Management RPC uses the same gRPC and HTTP port, which also binds [NEB API RPC](README) interfaces.
 
 Nebulas provide both [gRPC](https://grpc.io) and RESTful management APIs for users to interact with Nebulas. Our admin [proto](https://github.com/nebulasio/go-nebulas/blob/develop/rpc/pb/rpc.proto) file defines all admin APIs. **We recommend using the console access admin interfaces, or restricting the admin RPC to local access.**
 

diff --git a/docs/go-nebulas/infrastructure/permission_control_in_smart_contract.md b/docs/go-nebulas/infrastructure/permission_control_in_smart_contract.md
@@ -1,4 +1,4 @@
-# permission\_control\_in\_smart\_contract
+# Permission Control in Smart Contract
 
 ## What Is Permission Control Of Smart Contract
 

diff --git a/docs/node-strategy/README.rst b/docs/node-strategy/README.rst
@@ -28,14 +28,19 @@ Learn more about the Node Strategy and PoD mechanism:
 
 Another post: `The launch of Nebulas’ Proof of Devotion consensus protocol has begun <https://ambcrypto.com/the-launch-of-nebulas-proof-of-devotion-consensus-protocol-has-begun/>`_ on Ambcrypto.
 
-**Roadmap**
+**How to Join**
 
-In order to best complete the decentralized transition of the mainnet nodes, the Nebulas PoD Node Decentralization Strategy will gradually open the node applications to all. Initially, we invite active project parties, partners and community members within the current Nebulas ecosystem to deploy nodes and explore the governance processes in advance to the public release to provide valuable advice for testing and improvement. The roadmap is as follows:
 
-*   **Early January 2020** - Launch of test bounty program on the testnet;
-*   **January 2020** - Node application by invitation, consensus mechanism initiated;
-*   **End of February 2020** - Open application for community nodes;
-*   **End of March 2020** - First governance vote, governance mechanism initiated.
+The new version mainnet Nebulas Voyager with PoD will be launched on Mar 30, 2020. 
+
+In order to best complete the decentralized transition of the mainnet nodes, the Nebulas PoD Node Decentralization Strategy will gradually open the node applications to all. We invite active project parties, partners and community members to deploy nodes and explore the governance processes.
+
+- Apply a node on Nebulas Node Platform: `node.nebulas.io <https://node.nebulas.io/apply/ready>`_
+- `Prepare your hardware <appendix.html#appendix-a-recommended-hardware-configuration-for-node-operation>`_, `Node environment <../go-nebulas/blockchain/environment.html>`_.
+- Update your code: `How to join the Nebulas mainnet <../go-nebulas/blockchain/mainnet.html>`_
+
+Nebulas Community Collaboration Platform: `go.nebulas.io <https://go.nebulas.io>`_ 
+
 
 
 ----

diff --git a/docs/node-strategy/appendix.md b/docs/node-strategy/appendix.md
@@ -5,6 +5,7 @@
 * [Appendix B. Node Multi-User Participation](#appendix-b-node-multi-user-participation)
 * [Appendix C. Earnings Simulation](#appendix-c-earnings-simulation)
 * [Appendix D. Parameter Table](#appendix-d-parameter-table)
+* [Appendix E. Addresses](#appexdix-e-addresses)
 
 ## Appendix A. Recommended Hardware Configuration for Node Operation
 
@@ -17,7 +18,7 @@ Monthly recommended configuration server expenditure is approximately: $150 USDT
 *   Disk: 	>= 600G SSD
 *   NTP: NTP service is required on the server to ensure correct time synchronization for all operational nodes.
 
-**Node Installation Tutorial** - review the [Nebulas Technical Documentation: Nebulas 101 - 01 Compile Installation](https://wiki.nebulas.io/en/latest/go-nebulas/tutorials/01-installation.html).
+**Node Installation Tutorial** - review the [Nebulas Technical Documentation: Nebulas 101 - 01 Compile Installation](../go-nebulas/tutorials/01-installation).
 
 
 It’s recommended to build and deploy nodes via docker:
@@ -111,3 +112,14 @@ Assuming that all 51 governance nodes selected each month participate, the nodes
 *   Maximum amount of funds released per governance cycle: Cannot greater than $30,000 USDT
 
 
+## Appendix E. Addresses
+
+* **Sign-in address:** This address is the only one that you can sign in to the node platform with. Please use the Nebulas Chrome Extension to sign in and manage your node on this node platform.
+
+* **Minner address:** Only used for creating the block, signature, polling check. The keystore is on your server.
+
+* **Incentive address:** Your consensus incentive will be sent to this address. We recommend a cold storage wallet for security. The incentive address can be modified via the server configuration.
+
+* **Governance address:** If your node is selected as a governance node, your vote for proposals and projects will be via this address. In addition, your governance incentive will be sent to this address. To partake in governance and to vote, we recommend using a hot wallet such as NAS nano Pro.
+
+The default governance address is the same as the sign-in address. For security reasons, it is recommended to use a different address and allocate hot and cold wallets according to our recommendations.