diff --git a/source/concepts/reward-programs.rst b/source/concepts/reward-programs.rst index f37bbf211..864750fa3 100644 --- a/source/concepts/reward-programs.rst +++ b/source/concepts/reward-programs.rst @@ -10,8 +10,10 @@ Each of these programs rewards **a different aspect of the network**: - :ref:`supernode-program`: For powerful, high-availability and high-throughput nodes. - :ref:`voting-node-program`: For nodes supporting Finalization, |codename|'s fork resolution mechanism. +- :ref:`early-adoption-node-program`: For nodes that support |codename|'s network from the onset but do not qualify for the Supernode program. +- :ref:`ecosystem-node-program`: For nodes supporting **both** the NIS1 and |codename| networks. -In most cases, node owners wishing to benefit from these programs must explicitly **enroll** to them. The descriptions below contain **guides** explaining how to enroll to each program. +In most cases, node owners wishing to benefit from these programs must explicitly **enroll** in them. The descriptions below contain **guides** explaining how to enroll in each program. .. _supernode-program: @@ -36,7 +38,7 @@ Supernodes are regular nodes meeting the following additional hardware and opera **Chain Height**; Chain must be synchronized no more than **4 blocks** behind the reference height. **Chain Part**; Upload **50 random blocks hashes** of the chain accurately. These are compared to the reference chain hashes for accuracy. **Computing Power**; Hash at least **2'000 iterations per second**. Node is requested to calculate 10'000 iterations of a 32 byte seed. Speed and accuracy are measured. - **Bonded Deposit**; At least **1, 2 or 3 million** |networkcurrency| must be stacked on the node. The amount will decide the reward tier (see below). + **Bonded Deposit**; At least **1, 2 or 3 million** |networkcurrency| must be staked on the node. The amount will decide the reward tier (see below). **Version**; |codename| must be **up to date**. Nodes should be updated within **10 days** of each new |codename| release. **Ping**; **200ms response or less**. Node is requested to ping 20 other random nodes on the network and at least one ping time must pass the test (each node will be pinged 5 times and response times averaged). **Responsiveness**; **1 second**. 10 blockchain height requests will be made and at least 9 must answer in less than 1 second. @@ -78,7 +80,7 @@ See the complete `Terms & Conditions `. + :doc:`Follow this guide to enroll in the Supernode program <../guides/network/supernode-enrollment>`. .. _voting-node-program: @@ -100,10 +102,10 @@ Voting nodes are regular nodes meeting the following additional requirements: :delim: ; :widths: 30 70 - **Bonded Deposit**; At least **3 million** |networkcurrency| must be stacked on the node. + **Bonded Deposit**; At least **3 million** |networkcurrency| must be staked on the node. **Voting keys**; The node must signal its interest in becoming a voting node by registering its :ref:`Voting Key `. -Although not mandatory, it is **recommended** that voting nodes meet the same hardware requirements as :ref:`supernodes `. In fact, it is expected that participants of the Voting Node Program will also enroll to the Supernode program. +Although not mandatory, it is **recommended** that voting nodes meet the same hardware requirements as :ref:`supernodes `. In fact, it is expected that participants of the Voting Node Program will also enroll in the Supernode program. Rewards ======= @@ -122,3 +124,99 @@ Rewards symbol-cli transaction votingkeylink See the complete `Terms & Conditions `__. + +.. _early-adoption-node-program: + +*************************** +Early Adoption Node Program +*************************** + +It is critical that enough nodes are already available once |codename| launches. This program rewards nodes that agree to be online during |codename|'s **first year**. + +Requirements +============ + +.. list-table:: + :widths: 30 70 + :header-rows: 1 + + * - Parameter + - Requirement + * - **Availability** + - The node must pass the same tests that :ref:`supernodes ` do, at least during **95%** of the time the **first year**. + * - **Grace period** + - Availability tests are allowed to fail **the first 12 days**. + + However, the node must be **online within 24 hours of Symbol's launch**. + * - **Bonded Deposit** + - At least **500'000** |networkcurrency| must be staked on the node during the whole period. + * - **Maximum nodes** + - Only **1** node per person is allowed. + * - **Incompatibility** + - This program is **not available** to: + * Nodes registered to the :ref:`ecosystem-node-program`. + * Core Developers, NEM entities and NEM employees. + * Tier 3 supernodes. + +Rewards +======= + +This is a **one-time bonus**, paid in full **one year after the Symbol launch**, if requirements have been met. + +At the end of the period the node owner will receive **25'000** |networkcurrency|. + +Only **the first 75 nodes** to register in this program will be eligible. + +See the complete `Terms & Conditions `__. + +.. note:: + + :doc:`Follow this guide to enroll in the Early Adoption program <../getting-started/ready-for-symbol-launch>`. + +.. _ecosystem-node-program: + +********************** +Ecosystem Node Program +********************** + +This program is aimed at maintaining **both the NIS1 and the Symbol networks** for a year and a half. + +Successfull candidates will maintain a **NIS1 supernode** and a **Symbol node** both online for 18 months. + +Requirements +============ + +.. list-table:: + :widths: 30 70 + :header-rows: 1 + + * - Parameter + - Requirement + * - **Availability** + - Both NIS1 and Symbol nodes must pass the same tests that :ref:`supernodes ` do, at least during **95%** of the time the first **18 months**. + * - **Grace period** + - Availability tests are allowed to fail **the first 12 days**. + + However, the node must be **online within 24 hours of Symbol's launch**. + * - **Bonded Deposit** + - At least **250'000** |networkcurrency| must be staked on the |codename| node during the whole period. + + At least **3'000'000** ``xem`` must be staked on the NIS1 node during the whole period (to comply with the NIS1 supernode program). + * - **Maximum nodes** + - No more than **5** nodes per person are allowed. + * - **Incompatibility** + - This program is **not available** to: + * Nodes registered to the :ref:`early-adoption-node-program`. + +Rewards +======= + +This is a **one-time bonus**, paid in full **18 months after the Symbol launch**, if requirements have been met. + +At the end of the period, **3'125'000** |networkcurrency| will be evenly distributed among all participating nodes. + +See the complete `Terms & Conditions `__. + +.. note:: + + :doc:`Follow this guide to enroll in the Ecosystem program <../getting-started/ready-for-symbol-launch>`. diff --git a/source/getting-started/index.rst b/source/getting-started/index.rst index 8fc2be486..a465e2bd3 100644 --- a/source/getting-started/index.rst +++ b/source/getting-started/index.rst @@ -11,3 +11,4 @@ This is probably the first section you'll be interested in reading in your journ setup-workstation first-application ../guides/migration/migrating-from-nem-to-symbol + ready-for-symbol-launch diff --git a/source/getting-started/ready-for-symbol-launch.rst b/source/getting-started/ready-for-symbol-launch.rst new file mode 100644 index 000000000..4b24ee7ca --- /dev/null +++ b/source/getting-started/ready-for-symbol-launch.rst @@ -0,0 +1,354 @@ +######################################### +Getting your node ready for Symbol launch +######################################### + +This guide shows the steps required to have your node **ready for action**, during |codename|'s first days. This is important for node owners wanting to benefit from some of the :doc:`Reward Programs <../concepts/reward-programs>`. + +If you are not planning to run **your own Symbol node**, or to enroll in the :ref:`Early Adoption ` or :ref:`Ecosystem ` reward programs, you do not need to worry about this guide. + +************ +Introduction +************ + +**A beginning is a very delicate time**. The first block in the |codename| blockchain (the **Nemesis** block) is handcrafted but the following blocks are **produced by the nodes in the network**. This means that the moment the network launches there must be enough :ref:`Harvesting Nodes ` present to keep block creation flowing. + +NEM Group provides a few nodes to bootstrap the network, but it's critical that community-run nodes are added quickly afterwards to ensure **network resilience and independence**. + +This guide explains: + +- How to enroll in the different :doc:`Reward Programs <../concepts/reward-programs>`, created to **incentivize nodes** to come online as soon as possible. + +- How to configure your node so that it **starts harvesting as quickly as possible** when |codename|'s network launches. + +Snapshot and launch +=================== + +As you should be well aware by now, |codename|'s launch is happenning in two phases. + +1. **Snapshot**: When the NIS1 chain reached block height 3'105'500 a **snapshot** of the contents of all NIS1 accounts was taken. + +2. **Launch**: Afterwards, on March 15th (exact time to be determined), the new |codename| network will **launch** meaning that the nodes managed by NEM Group will be brought online and they will start adding blocks to the shinny new |codename| blockchain. + +These two concepts are used throughout this guide. + +********* +Enrolling +********* + +.. warning:: Enrollment to the :ref:`Early Adoption ` and :ref:`Ecosystem ` reward programs is now **closed**. + +If you wanted to participate in either of these programs you needed to enroll in them **before the snapshot**. This section explains how to **update your node information**, as there is a **12-day grace period** to have the node fully configured and functional. + +If you are interested only in the :ref:`supernode-program` or the :ref:`voting-node-program` (or if you are not interested in any of the reward programs) you didn't need to enroll beforehand so you can skip this section and jump to :ref:`getting-ready-launching-your-node`. + +.. _getting-ready-prerequisites: + +Prerequisites +============= + +Since you are already enrolled in one of the Reward Programs, you should already have: + +- An **opted-in** `NIS1 `__ account, that held at least **10'000 XEMs** at the snapshot block height (3'105'500). +- A Paper Wallet with the information of your new Symbol account, obtained during opt-in. +- Sent an enrollment request before the snapshot. + +.. _getting-ready-grace-period: + +Grace period +============ + +.. warning:: All nodes that enrolled in either the :ref:`Early Adoption ` or :ref:`Ecosystem ` reward programs are expected to be **online** within 24 hours of |codename|'s launch. + +However, there is a **12-day grace period** (until March 27th) during which: + +- The node **availability test** are allowed to fail (These are the same tests as for the :ref:`supernode-program`). +- Your **enrollment information** can be updated in case you made a mistake. + +The rest of this section is a reminder of how to submit the enrollment request. + +Updating the request +==================== + +You can update your enrollment information as many times as you need by: + +- **Sending another NIS1 transaction** (as described below) **from the same account** as you did initially. +- Tell `NEM's Telegram Help Desk `__ about the update. + +Enrollment request +================== + +The request is **a specially-crafted NIS1 transaction** sent from your NIS1 account to a specific address using the Nano Wallet (or any other wallet that allows sending NIS1 transactions with a message). + +Detailed instructions for the Nano Wallet follow, but this is the summary: + +- The **destination address** must be ``NAQ7RCYM4PRUAKA7AMBLN4NPBJEJMRCHHJYAVA72``. +- The **amount** to transfer must be **0**. +- The **message** must be un-encrypted and adhere to one of the following templates, depending on the program you are interested in. It is recommended that you start composing the message in a text file, as you will be editing it. + + .. list-table:: + :widths: 50 50 + :header-rows: 1 + + * - Early Adoption + - Ecosystem + * - .. code-block:: json + + { + "type":10, + "p":"earlyadoption", + "d":"SYMBOL_ACCOUNT_PUBLIC_KEY", + "sh":"SYMBOL_NODE_HOST" + } + + - .. code-block:: json + + { + "type":10, + "p":"ecosystem", + "d":"SYMBOL_ACCOUNT_PUBLIC_KEY", + "sh":"SYMBOL_NODE_HOST", + "nh":"NIS1_NODE_HOST" + } + +Replace ``SYMBOL_ACCOUNT_PUBLIC_KEY`` with the **public key** of the new |codename| account you received when you opted-in. **Read the next subsection to know how to obtain it**. + +Replace ``SYMBOL_NODE_HOST`` with the public host (hostname or IP address) of your **Symbol node**. + +Replace ``NIS1_NODE_HOST`` with the public host (hostname or IP address) of a **NIS1 node** you own (only for the Ecosystem program). + +.. note:: + + If you are not using the standard port for the monitoring agent (7880) you can add an ``"ap":PORT_NUMBER`` line to the registration message. For example: + + .. code-block:: json + + { + "type":10, + "p":"earlyadoption", + "d":"SYMBOL_ACCOUNT_PUBLIC_KEY", + "sh":"SYMBOL_NODE_HOST", + "ap":7881 + } + +.. _getting-ready-node-public-key: + +The account's keys +================== + +When you opted-in you should have received a **Paper Wallet**. This is just a PDF file meant to be **printed or stored offline** for added security. + +This file contains your new Symbol account's **mnemonic phrase**, which you will need to produce a :ref:`keypair`: a **public key** required for enrolling and a **private key** required to configure your node (See the :ref:`hdwallets-and-mnemonics` page for more information). + +This will be accomplished using the |codename| :ref:`wallet-desktop` (Not to be confused with the NIS1 Nano Wallet used to opt-in). You will be using the new |desktop-wallet| for all your operations on the |codename| blockchain, so :ref:`install it now ` to start getting acquainted to it. + +Obviously the wallet will not be **fully operative** until |codename| launches, but it can already be used to extract your account's keys from the mnemonic phrase. + +1. Fire up the wallet and click on the ``Create a new profile`` link: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-0.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-0.png + +2. Click on the ``Import mnemonic`` button: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-1.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-1.png + +3. Enter a profile name, select the ``Symbol Mainnet`` network type (**Important!**), enter and confirm a password and click ``Next``: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-2.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-2.png + +4. Enter the 24 words from the mnemonic phrase in your paper wallet and click ``Next``: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-3.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-3.png + +5. You will be presented with the list of account addresses that can be derived from that mnemonic (as explained in the :ref:`hdwallets-and-mnemonics` page). **Select the one that matches the address in your paper wallet** (typically the first one) and click ``Next``: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-4.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-4.png + + .. note:: If your opted-in address does **not appear** in the list, make sure the NIS1 account has **enough funds** as stated in the :ref:`getting-ready-prerequisites` section. Only accounts with at least **100 XEMs** can opt-in, and only accounts with at least **10'000 XEMs** can harvest. + +6. Accept the terms and conditions and click ``Finish``: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-5.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-5.png + +7. You will be taken to the wallet's **main screen** (The balance shown might not be accurate until |codename| launches). Select the ``Accounts`` tab on the left: + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-6.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-6.png + +8. This is the **accounts screen**. You only imported one account from your mnemonic, so there is only one entry in the list. Verify on the right that the **address** shown matches your paper wallet and note that below there is a **Public Key**. This is the first key we were looking for. Click the **copy** button to the right of the key (do not try to select and copy the key's text directly as it is too long and it is truncated): + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-7.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-7.png + + This hexadecimal string (64-characters long) is the |codename| account's public key that you need to use in the enrollment message in the ``d`` field (replacing ``SYMBOL_ACCOUNT_PUBLIC_KEY`` in the templates). **Paste the key you copied from the Desktop Wallet into your enrollment message**. + +9. Now click on the ``Show`` link right below the public key and enter your password. + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-8.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-8.png + +10. Your account's **Private Key** will be shown for a few seconds. This is the second key we were looking for. Click the **copy** button to the right of the key (do not try to select and copy the key's text directly as it is too long and it is truncated): + + .. image:: /resources/images/screenshots/mnemonic-to-pubkey-wallet-9.png + :align: center + :width: 50% + :class: with-shadow + :target: /_images/mnemonic-to-pubkey-wallet-9.png + + This hexadecimal string (64-characters long) is the |codename| account's **private key** that you need to configure your node in the next section. **Paste the key into a temporary file for later use**. + +Send the transaction +==================== + +Your enrollment message should now look something like this (depending on the chosen reward program): + +.. code-block:: json + + { + "type":10, + "p":"earlyadoption", + "d":"B49D19106E08C1E655FA5A02D85FD628BE9CE13FF3A09D7D25C7C9190E515DBA", + "sh":"my-symbol-node.com" + } + +Remember that **if you don't know your host name yet**, you can leave it blank (``"sh":""``) and send another transaction during the grace period to update it. + +.. note:: Paste the message into a `JSON Validator `__ to ensure it is correctly formatted. + +You will now use **NEM's Nano Wallet** to send the message and complete the enrollment (Not to be confused with the |desktop-wallet| that you used before). You should already have the wallet installed if you followed the :ref:`getting-ready-prerequisites` section. + +This is how the Nano Wallet looks like after you fire it up: + +.. image:: /resources/images/screenshots/nano-wallet-reward-enrollment-tx.png + :align: center + :class: with-shadow + :target: /_images/nano-wallet-reward-enrollment-tx.png + +Click on the **LOGIN** button at the top-right, complete the login procedure, and then follow these instructions: + +.. image:: /resources/images/screenshots/nano-wallet-reward-enrollment-tx-instructions.png + :align: center + :class: with-shadow + :target: /_images/nano-wallet-reward-enrollment-tx-instructions.png + +1. Click on the **Send** button at the top. +2. Check that you have **enough funds** to pay for the transaction fee (the required amount is shown below in the **Fee** box). +3. Check that you are using the **correct account**. To enroll in the **Ecosystem** program this transaction has to be sent from the account owning the NIS1 node. For the **Early Adoption** program it does not matter. +4. Enter the destination address ``NAQ7RCYM4PRUAKA7AMBLN4NPBJEJMRCHHJYAVA72``. +5. Enter the **enrollment message** you prepared. +6. Enter your wallet's password and click on the wide **Send** button at the bottom. + +Once the transaction is announced and accepted, **your enrollment is complete**. + +.. note:: Don't forget to tell `NEM's Telegram Help Desk `__ about the update!. + +The next section explains how to setup your node so that it is ready to harvest as soon as possible, as required by the Early Adoption and Ecosystem programs. + +.. _getting-ready-launching-your-node: + +******************* +Launching your node +******************* + +Nodes can register as :doc:`harvesters <../guides/harvesting/index>`, :ref:`supernodes ` or :ref:`voting nodes ` **at any time**. + +**However**, to participate in either the :ref:`early-adoption-node-program` or the :ref:`ecosystem-node-program` your node needs to: + +- Become online during **the first 24 hours after Symbol's launch**. +- Start passing all **availability tests** during the `grace period `_. + +This section explains how to start your node **once the Symbol network is up and running**, using the Symbol Bootstrap tool. + +1. **Install the latest version** using the method described in :doc:`../guides/network/using-symbol-bootstrap`. + +2. **Create a custom preset file**. + + You need to create a :ref:`custom preset file ` for Symbol Bootstrap so it **uses the account you opted-in** instead of creating a new one. + + **The custom preset contains your account's private key**, but Symbol Bootstrap will store it **encrypted**. You can delete the preset file afterwards. + + Create a file named, for example, ``custom.yml`` with this content: + + .. code-block:: yaml + + nodes: + - voting: true + mainPrivateKey: ●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●● + +3. **Start Symbol Bootstrap**. + + .. code-block:: bash + + symbol-bootstrap start -p mainnet -a dual -c custom.yml + + (Read the :doc:`../guides/network/running-a-symbol-node` guide to know more about this command.) + + This will ask you for a password to encrypt the configuration files: + + .. code-block:: text + + ? Enter password to use to encrypt and decrypt custom presets, addresses.yml, and preset.yml files. When providing a password, private keys will be encrypted. Keep this password in a secure place! + + **Remember this password** as Symbol Bootstrap will request it every time you work with an encrypted configuration file. + +4. **Wait for the node to boot**. + + You should see a lot of debug output on the console while all the node's services are booted. Meanwhile, on a different terminal, go to the same directory where you ran the previous command and run: + + .. code-block:: bash + + symbol-bootstrap healthCheck + + When all indicators are green your node is up and running and you can continue with this guide. + +5. **Register the rest of the keys** + + There are more keys involved in running a node than the main account's key. If you only added your main key to the custom preset file, Symbol Bootstrap will have created the rest for you (remote, VRF and voting) but they still need to be linked to the main account. This is done with the ``link`` command. + + Once your node is running, from a different terminal (but in the same folder where you ran ``symbol-bootstrap start``), run: + + .. code-block:: bash + + symbol-bootstrap link + + This will announce a few link transactions (there's a :doc:`fee <../concepts/fees>` involved) and your node will become fully configured. + +************ +Verification +************ + +Browse to `Symbol Explorer `__, locate your node, and check that all information is correct. + +You should be able to see a lot of information (including the node's name and URL, for example), and, if it is enrolled in any reward program, a special card stating the program's name and the latest availability test results. \ No newline at end of file diff --git a/source/guides/network/supernode-enrollment.rst b/source/guides/network/supernode-enrollment.rst index b361db651..3ef8c3991 100644 --- a/source/guides/network/supernode-enrollment.rst +++ b/source/guides/network/supernode-enrollment.rst @@ -1,5 +1,5 @@ ################################## -Enrolling to the Supernode program +Enrolling in the Supernode program ################################## This guide shows how to create a node and register it as a **Supernode**. Make sure you know about the :ref:`supernode-program` before continuing with this guide. @@ -143,7 +143,7 @@ The process requires **installing a monitoring agent** and **announcing a specia 5. **Send the enrolling message** - The last bit is to **notify the Controller** that your node wants to enroll the Supernode program. This is done through a conventional :ref:`Transfer Transaction ` with no mosaics and a special message: + The last bit is to **notify the Controller** that your node wants to enroll in the Supernode program. This is done through a conventional :ref:`Transfer Transaction ` with no mosaics and a special message: .. code-block:: text diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-0.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-0.png new file mode 100644 index 000000000..17f23de67 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-0.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-1.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-1.png new file mode 100644 index 000000000..bd4cba4c3 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-1.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-2.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-2.png new file mode 100644 index 000000000..0b7ae6446 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-2.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-3.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-3.png new file mode 100644 index 000000000..b6f2863cc Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-3.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-4.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-4.png new file mode 100644 index 000000000..07868d67f Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-4.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-5.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-5.png new file mode 100644 index 000000000..e586111ec Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-5.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-6.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-6.png new file mode 100644 index 000000000..1f1c0c670 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-6.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-7.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-7.png new file mode 100644 index 000000000..bba1e1610 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-7.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-8.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-8.png new file mode 100644 index 000000000..c7dcd2dec Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-8.png differ diff --git a/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-9.png b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-9.png new file mode 100644 index 000000000..9885c21f4 Binary files /dev/null and b/source/resources/images/screenshots/mnemonic-to-pubkey-wallet-9.png differ diff --git a/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx-instructions.png b/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx-instructions.png new file mode 100644 index 000000000..909aaa73c Binary files /dev/null and b/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx-instructions.png differ diff --git a/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx.png b/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx.png new file mode 100644 index 000000000..f793460d5 Binary files /dev/null and b/source/resources/images/screenshots/nano-wallet-reward-enrollment-tx.png differ diff --git a/source/wallets.rst b/source/wallets.rst index e58f339b9..f87f44cee 100644 --- a/source/wallets.rst +++ b/source/wallets.rst @@ -15,13 +15,10 @@ Desktop Wallet Cross-platform client for Symbol to manage accounts, mosaics, namespaces, and issue transactions. |desktop-wallet| is available for Mac, Windows, and as a web application. -.. note:: The desktop wallet is only available for the public test network. - Installation ============ 1. Download the |desktop-wallet| from the `releases section `_. -The executable file for your operative system is under the "Assets" tab. 2. Launch the executable file and follow the installation instructions.